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

Broken Pipe errors on JerryScript #120

Open
bzyo opened this issue Aug 23, 2020 · 5 comments
Open

Broken Pipe errors on JerryScript #120

bzyo opened this issue Aug 23, 2020 · 5 comments

Comments

@bzyo
Copy link

bzyo commented Aug 23, 2020

On JerryScript, the following error occurs somewhat frequently:

Script execution failed: Failed to send command to child process: Broken pipe. Retrying in 1 second...

@WilliamParks
Copy link
Contributor

I have encountered the same issue intermittently with Spidermonkey as well. My initial guess is that it's due to short reads, but I haven't investigated further.

@saelo
Copy link
Collaborator

saelo commented Aug 24, 2020

Thanks for the report. That would mean it fails here:

return reprl_error(ctx, "Failed to send command to child process: %s", strerror(errno));

My guess is that this is the result of the child process dying (e.g. due to the OOM killer or if a background thread of the js shell crashes) while waiting for the next REPRL command. Then this would be the first place where the parent notices, since the pipe has now (unexpectedly) closed. Maybe we can add some code before this line to check if the child is still alive (e.g. through waitpid) and if it died, print some more information (e.g. stderr). But probably there isn't much more we can do, and Fuzzilli will also just retry the execution, so it shouldn't be much of an issue in any case

@saelo
Copy link
Collaborator

saelo commented Sep 7, 2020

I added better logging to libreprl: bd2135d
Let me know if the you still encounter the "Script execution failed" messages or if they have now become "Child unexpectedly exited/terminated" messages now (and in that case, please also include the exit code/signal number)

@bzyo
Copy link
Author

bzyo commented Sep 14, 2020

I've seen just the new error of "Child unexpectedly terminated with signal 11 between executions" by itself and then also followed by the original error posted here.

@Limesss
Copy link

Limesss commented Oct 13, 2021

I've seen just the new error of "Child unexpectedly terminated with signal 11 between executions" by itself and then also followed by the original error posted here.

hi,did u solved it ? i hava the same question in the lastest jerry version

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants