bug: Chromium crashes on mac os #86
Comments
This flag has been removed because all the info that was logged by it is output by default now in case of an error. Looking at the chromium executable path, it looks like you're using the latest Puppeteer 8.0 (Chromium version r856583). I've tried upgrading as well and it still works for me (on macOS 11.2 here). So I'm not really sure where the problem is for you but I suggest you search for "puppeteer chromium quit unexpectedly" and maybe there's some related upstream issue. If you find something, please reference it here. I've done a quick search and couldn't find anything, and it isn't reproducible for me either, so I can't really do anything here. Also, have you checked the troubleshooting link? https://github.com/puppeteer/puppeteer/blob/main/docs/troubleshooting.md |
|
Closing this for now as there has been no reply. |
|
Sorry @simonhaenisch. I didn't feel that there is something to reply. Yes, I searched "pupeteer chromium quit unexpectedly", even before posting question here. Yes, I read the docs on link, even before posting here (that link was in errors before crash). I checked, for me, it still crashes, and I'm now on 11.3.1. I'm sorry I didn't reply. If I can provide some help regarding this, I'll gladly help. Best regards. |
|
Thanks for the update. If you have another Mac available, maybe you can try to see if it's reproducible there as well, or you could try creating a new user account on your Mac (the user's TBH I'm still considering closing this because it does not seem related to |
|
Thank you for reopening. I'll try on another Mac (Catalina) next week and also try to clean the folders you mentioned. I'll let you know of the results. As for closing the issue, you are probably right. But, we can give it another shot, maybe there is something that can be done. |
|
Hello. Tried on another Mac (Catalina), it is working ok. On my Mac: again, removed /usr/local/lib/node_modules (md-to-pdf was globally installed), without success. So, maybe something got mixed, or some faulty files were generated on my first install. Thank you very much for your time. |
Context:
md-to-pdf -v):3.3.1macOS 11.114.0.0Describe the bug:
Using simple
md-to-pdf readme.mdcommand, chromium crashes. Tried with--debug(as suggested in this comment on #54), but it seems that--debugis not supported.Tried
--launch-options '{ "args": ["--no-sandbox"] }'(from #20) and--launch-options="['--no-sandbox', '--disable-setuid-sandbox']"(from #54), but to no avail.Bellow you can find my command line history with commands and their outputs. Also, you can find screenshot of it too.
And, if I click on 'report...' button in 'Chromium quit unexpectedly', this is how my report looks like (maybe you can find some useful info here):
The text was updated successfully, but these errors were encountered: