I'm writing a chrome extension which does the following:
XMLHttpRequest
total_encoded_data
<a href=data:application/octet-stream;charset=utf-8;base64,' + total_encoded_data+' download='file.bin'>Click to Download</a>
. Where total_encoded_data
is added to href using jQuery.I have found, through a manual binary search, that if the size of total_encoded_data
is greater than 2097100 characters, then I will get an Aw, Snap message when I click the link. If the size is smaller, then I can download as expected.
In addition to testing the filesize, I also used atoi
to ensure that the base64 encoding is valid, and it operates without error.
The Aw, Snap messages don't produce any crash reports in chrome://crashes
nor any unexpected output in the chrome_debug.log
How do I avoid an Aw, Snap message when serving a data uri where the base64 encoded string length is greater than 2097100?
It's a known chromium bug. The recommended workaround is to use a blob URL. Also see Creating a Blob from a base64 string in JavaScript.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With