-
-
Notifications
You must be signed in to change notification settings - Fork 141
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
exec-port
stops responding sometimes.
#180
Comments
Can you upgrade the OTP to 27 and reproduce it there? You may need to compile a non-optimized build in order to see the stacktrace by setting |
Upgrading OTP is not easy there. I will try to run this with |
Not sure. It has been running pretty stably in many uses. |
That's the valgrind's memory detector output.
|
It looks like it's 1> exec:run("/usr/bin/echo asd", [sync, stdout, stderr, pty]).
exec got msg from port: {1,{pid,74130}}
exec added monitor <0.87.0> for OsPid 74130exec got msg from port: {0,{stdout,74130,<<"asd\r\n">>}}
exec got msg from port: {0,{exit_status,74130,0}}
Pid 74130 exited with status: {0,0}
<0.87.0> 74130 got down message ({status,0}) (ismon=true)
{ok,[{stdout,[<<"asd\r\n">>]}]} Results in valgrind report:
In my case, it's not critical to use the |
erlexec
sometimes stops to respond. Not sure if it is related to this problem, but sometimes I see segfaults in the syslog (Debian/bullseye, Erlang/OTP 22):I understand the report is not very informative. I will try to debug it further, but any hints would help.
The text was updated successfully, but these errors were encountered: