Thursday, May 23, 2024
129
rated 0 times [  134] [ 5]  / answers: 1 / hits: 17695  / 11 Years ago, sun, may 26, 2013, 12:00:00

I'm writing a chrome extension which does the following:




  1. Downloads a file from a website to memory using XMLHttpRequest

  2. Adds additional data to the file and then base64 encodes the result to the variable total_encoded_data

  3. Offers the data to the user using <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?


More From » google-chrome-extension

 Answers
103

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.


[#78014] Friday, May 24, 2013, 11 Years  [reply] [flag answer]
Only authorized users can answer the question. Please sign in first, or register a free account.
koltenb

Total Points: 276
Total Questions: 92
Total Answers: 101

Location: North Korea
Member since Fri, Nov 4, 2022
2 Years ago
;