-
Notifications
You must be signed in to change notification settings - Fork 325
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
Storing files of a few megabytes to window.ipfs.files.add hangs Firefox for a minute or more #485
Comments
It takes maybe ~30 seconds of hanging to successfully add a 1.6MB file, in my hands. |
To test, you can go to https://interfect.github.io/ipfstunes with The hang occurs before the prompt to authorize access to |
Thank you for reporting this. I was able to confirm presence of described delay / high load in Firefox 60. |
I created demo page that reliably reproduces the difference between Chrome and Firefox: Chromium 67Firefox (Stable & Nightly)The difference is night and day, it really looks like a bug. Initial guess: related to postMessage handling in webextensions (Firefox bug) or some edge case in serialization done by ipfs-postmsg-proxy (bug in our code). Next step is to create a webextension demo that sends the same amount of data without ipfs-postmsg-proxy. Sidenote: UI in Firefox Nightly is a little bit more responsive, probably due to the fact Firefox 63+ moved extensions to separate process on Linux. |
Quick test of raw Next: look into serialization in ipfs-postmsg-proxy. |
Closes #485 thanks to fix from ipfs-inactive/ipfs-postmsg-proxy#35
@interfect fyi the fix for this was released in beta v2.5.0.11550, will land in stable soon. |
I'm trying to store MP3 files in IPFS for https://github.com/interfect/ipfstunes by loading them into
Buffer
s and thenipfs.files.add
-ing them. Everything works fine using in-pagejs-ipfs
, but with IPFS Companion'swindow.ipfs
, using either the embedded or external node, storing a song-sized file will hang the Firefox UI and make my window manager prompt me to kill it because it is unresponsive.I don't seem to have this problem with tiny files.
The text was updated successfully, but these errors were encountered: