Open Mederim opened 3 years ago
Hi @Mederim,
Thanks for opening an issue:
Can you show the logs?
When i use verbose i get this:
Warning: getaddrinfo ENOTFOUND tracker.internetwarriors.net (udp://t racker.internetwarriors.net:1337/announce) Warning: getaddrinfo ENOTFOUND opentracker.i2p.rocks (udp://opentrac ker.i2p.rocks:6969/announce) Warning: getaddrinfo ENOTFOUND 3rt.tace.ru (udp://3rt.tace.ru:60889/ announce) Warning: Non-200 response code 400 from http://tracker.opentrackr.or g:1337/announce Segmentation fault
Also i used strace to get logs so here the link
Does it happen with Node 14?
Not tested, i use node 16.9.1
Please test with LTS, we don't officially support current
tested with alpine linux and node 14, i have a segfault too
Still have the same issue, now with node v18.6.0
Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?
O can't even build it
From what I can see, this appears to be due to a glibc version of utp-native
being used across all libc environments, rather than a musl-specific version being used on musl environments.
I've submitted a PR here which adds musl-specific prebuilds to utp-native
.
Using the musl pre-build generated from the above PR, I no longer experience segfaults when using webtorrent-cli in musl environments.
Alternatively, depending on how you're running webtorrent-cli, you can rebuild utp-native
from source, which is mentioned in this issue from utp-native
: https://github.com/mafintosh/utp-native/issues/49
Version: 3.5.3 OS: KISS LINUX NPM: 7.20.3 NodeJS: 16.7.0
I get segmentation fault when try to streaming. Just did 'webtorrent "magnet link" --mpv'.