Skip to content
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

Someones crashes. #476

Closed
eliooses opened this issue Nov 3, 2015 · 11 comments
Closed

Someones crashes. #476

eliooses opened this issue Nov 3, 2015 · 11 comments

Comments

@eliooses
Copy link

@eliooses eliooses commented Nov 3, 2015

Hi there!, i´m testing the browser version of webtorrent and in a timelapse of 12 hours aprox. i have 4 crashes.

I attach someones captures if that is for help.

My upload connection is very poor, i presume what that affects the performance because the connection is refused, but in other cases is crash spontaneously.

sin titulo
sin titulo2
sin titulo3
sin titulo4

@DiegoRBaquero

This comment has been minimized.

Copy link
Member

@DiegoRBaquero DiegoRBaquero commented Nov 4, 2015

The issue is the RAM. The message clearly states it.

@eliooses

This comment has been minimized.

Copy link
Author

@eliooses eliooses commented Nov 5, 2015

The first and the second yes, but the third and fourth not. I only report that if this help. The RAM collapse is weird becausa i have 8 GB of RAM and only load Sublime Text and Instantio (an many tabs of GitHub but is not relevant).

@DiegoRBaquero

This comment has been minimized.

Copy link
Member

@DiegoRBaquero DiegoRBaquero commented Nov 5, 2015

The time out of the websocket must be and issue of the tracker server I think. Unless you whatever reason you are being blocked? (Which I doubt it).

The RAM issue, I've had it too. I suppose chrome does this to protect a tab from consuming all the RAM. The thing is, I think, that any torrent downloaded content is maintained in RAM until you download it from its blob url.

And nice series btw.

@eliooses

This comment has been minimized.

Copy link
Author

@eliooses eliooses commented Nov 5, 2015

@DiegoRBaquero ! no respondí en español para que todos puedan leer. #lol

Si, te entiendo perfectamente. Genial, entonces será un tema de Chrome. Te pregunto ya que veo que estas bien activo en el tema. Sirve que reporte este tipo de cosas?

Abrazo.

@DiegoRBaquero

This comment has been minimized.

Copy link
Member

@DiegoRBaquero DiegoRBaquero commented Nov 5, 2015

Supongo que sí. A mí me pasa lo mismo cuando intento hacer stream un torrent pesado, aún cuando no hay problemas al hacer seed inicial.

Y sí! Todo reporte ayuda! Así intentamos llegar a soluciones en conjunto, como comunidad.

@feross

This comment has been minimized.

Copy link
Member

@feross feross commented Dec 4, 2015

If you seed or download files greater than 2GB in size, you will likely crash Chrome. See #319.

@feross feross closed this Dec 4, 2015
@amilajack

This comment has been minimized.

Copy link
Contributor

@amilajack amilajack commented Jul 23, 2016

Will node crash in the same situation?

@feross

This comment has been minimized.

Copy link
Member

@feross feross commented Jul 23, 2016

@amilajack No -- in node.js, WebTorrent uses fs-chunk-store instead of memory-chunk-store, so you're not limited by the maximum JS buffer size.

@amilajack

This comment has been minimized.

Copy link
Contributor

@amilajack amilajack commented Jul 24, 2016

Is it possible to require only the node module, is it possible to import the node version of webtorrent in electron instead of the browser version?

@feross

This comment has been minimized.

Copy link
Member

@feross feross commented Jul 27, 2016

@amilajack If you do require('webtorrent') in Electron, you get the node.js version. But you'll get WebRTC support for free too, because webtorrent detects it in the Electron environment.

If you want the browser version, then you can use the minified script webtorrent.min.js via a <script> tag.

@lock

This comment has been minimized.

Copy link

@lock lock bot commented May 4, 2018

This thread has been automatically locked because it has not had recent activity. To discuss futher, please open a new issue.

@lock lock bot locked as resolved and limited conversation to collaborators May 4, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
4 participants
You can’t perform that action at this time.