v2.2.0 segfaults on Arch Linux
See original GitHub issueAfter upgrading to v2.2.0, the following code sometimes segfaults on Arch Linux, killing the entire node process:
const { WebUSB } = require('usb');
const usb = new WebUSB({ allowAllDevices:true })
usb.getDevices().then(console.log).catch(console.error)
After reverting to 2.1.3, the same code functions properly.
Issue Analytics
- State:
- Created a year ago
- Reactions:1
- Comments:6 (2 by maintainers)
Top Results From Across the Web
[SOLVED] QuiteRSS | Segmentation fault (core dumped ...
#40 0x00007f55ebc4f869 n/a (libglib-2.0.so.0) #41 0x00007f55ebc4f8ae ... #2 0x00007f55ebc4f8ae g_main_context_iteration (libglib-2.0.so> #3 ...
Read more >Segmentation fault when running as non-root on Arch Linux
I have compiled the package using the user provided : https://aur.archlinux.org/packages/notekit-clatexmath-git clatexmath-git dependency is met by ...
Read more >How to stop segmentation fault (core dumped)? - Stack Overflow
I am trying to learn c, but everytime i run a code that needs user imput i get segfault error My os is...
Read more >Issues with game starting/launching on Linux Arch ...
Hi! Recently installed this game on Arch Linux. Unfortunately it will not run. I checked that required dependencies are in place (ldd, lib32-*...
Read more >GIMP crashes on startup (#7681) · Issues - GitLab - GNOME
GIMP 2.10.30-1 segfaults on startup on Arch Linux. ... 0x00007f0d4217c5f1 g_cond_wait (libglib-2.0.so.0 + 0xa25f1) #2 0x00007f0d4263d164 n/a ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
ah no, it bisects to the upgrade to libusb v1.0.25 (#490). it seems to be libusb/libusb#1059, which is popping up in other apps and distros as well. the bug was fixed in https://github.com/libusb/libusb/pull/1073 (https://github.com/libusb/libusb/commit/7cc06ea5c7c3b36801421a6be17b51b92c1bc05a) but is still unreleased.
I can confirm that applying this fix solves the issue. like I said it hasn’t landed in a release yet, but they’re preparing to release v1.0.26 in a few days (libusb/libusb#1047). since it’s a fix only release, I think it’s better to wait for it.
v2.3.0 has been released, please check this fixes your issue.