-
Notifications
You must be signed in to change notification settings - Fork 226
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
(error: Unexpected end of JSON input) #16
Comments
Same error. Can provide file if needed. (345MB) |
And the same here (300MB JSON file) |
Hi all - thanks for the reports. Yes, there is an issue with processing files over 256 MB. It has been fixed in the Pro version of the visualizer, but the fix has not yet been ported over to the free heatmap tool. The crux of the issue is in-browser memory limits for a single object (and/or hitting total RAM capacity). The fix involves steaming the JSON into memory instead for files over ~256 MB. I anticipate having the fix live in the next month or so; at present I am abroad and sans computer which severely inhibits productivity. Thanks for your patience - I will drop another comment when the issue has been resolved. Best, |
any update on this? |
Got the same here. 277MB file so just over the limit. |
same issue here. |
@tbolick I am working on a fix for this, would you mind providing me with the 345 mb file so I can test? my email is suria AT seas DOT upenn DOT edu (please attach file as a downloadable link since my email can't handle files of that size) |
Same. I'll be happy to provide my file (~340MB). Let me know. |
As an alternative, what about allowing gzip uploads? Would that help with the upload limit at all, or does it happen after file transfer? |
@JustAnotherAmateur The files are actually never uploaded to a server - all processing happens locally. Pull request #18 resolves the issue, but fell off my radar due to school and has not yet been merged into master - I will look into getting it merged now. |
Thank you! |
Getting this error from my takeout json. Not much to go on in the js console.
The text was updated successfully, but these errors were encountered: