-
Notifications
You must be signed in to change notification settings - Fork 30.8k
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
Running node from udev causes SEGV #19036
Comments
I am trying to recreate this - how do you fire the rule? (I am new to |
@gireeshpunathil I think |
thanks, but that did not help - I have no evidence that it triggered the action. |
FWIW, I wasn't able to reproduce either but my guess would be it's system-specific, possibly Arch-specific. Perhaps there's a restrictive ulimit in effect (like a low |
@gireeshpunathil on my system it does not report that it needs root permissions when you manually retrigger the event (run
The udev rule watches display outputs - hot pluggable ports like #path to your display output could be different
#udevadm test - does not trigger the RUN command of the rule
udevadm test /sys/class/drm/card0/card0-HDMI-A-1/ @bnoordhuis that's an idea worth exploring, thank you.
I tried increasing stack size to |
I was able to recreate the crash. Earlier I was working in a container image, which does not work well with udev as I read.
while I am not certain this is the root cause, this is a major deviation from the normal run.
|
Right, so there's a W^X deny policy in effect. Upstream V8 might one day support that - some work was done on that recently - but for now you'll have to either disable the policy or not run node from udev. Thanks for clearing that up, Gireesh. I'll close this out. |
@bnoordhuis Any update on this issue? |
@sudhakar3697 Recent versions of Node.js have a |
For the benefit of anyone coming across this issue as I did, I didn’t have the luxury of using a newer version of node with the /etc/systemd/system/myservice.service
/etc/udev/rules.d/120-bluetooth.rules
Hopefully this comment will assist someone else who encountered this issue like me. |
Version: v9.6.1
Platform: Linux archlaptop 4.15.2-2-ARCH #1 SMP PREEMPT Thu Feb 8 18:54:52 UTC 2018 x86_64 GNU/Linux
I have following rule in
/etc/udev/rules.d/98-monitor-hotplug.rules
When the event is triggered the node process terminates with
SEGV
.This is very similar to #16901 which has been closed with no conclusion.
It doesn't matter if I run empty
script.js
file ornode -e "process.exit(0);"
instead of executing/bin/node
repl console on the udev event. It always terminates withSEGV
.I experience the same issue with node version
v8.9.4
LTS.Could anybody try to reproduce this issue, please?
Apart from providing the logs, I have currently no idea how to debug this issue, so please if you need more info, could you provide me with specific information about how I should proceed? Thank you.
gdb
thread apply all bt full
The text was updated successfully, but these errors were encountered: