-
Notifications
You must be signed in to change notification settings - Fork 231
Instant crash with "Aw, snap!" text #331
Comments
Same problem on Fedora Linux 36. Is there anything to be done? |
Same problem here on Ubuntu 22.04. Has anyone found a solution? |
The project hasn't been maintained since 2019, sadly. The feature set is fantastic but.. the original creator left and theres no one to maintain it. Also.. yeah.. ndb is broken in a few ways. Yeah you should use the --inspect-brk setup these days. |
The original reason I found ndb, is because I wanted to debug worker threads, and couldn't find any other solution back then. I didn't need to user worker threads since then, but wonder if there is a method for this |
I believe VS Code can do it and IntelliJ can do it. |
Oh, and Chrome Web Inspector. |
node processes worker-threads? Neat, I'll have to look into it. Don't use vscode or intellij, but I'm sure there is a standalone solution |
NDB window crashes with "Aw, snap!" text instantly when started.
Chromium r624492
_text/html,%0A <title></title>%0A <style>html{background:%23242424;}</style>%0A <script>self.paramsForReuse = {"data":"eyJjd2QiOiJmaWxlOi8vL21lZGlhL2RhdGEvUHJvamVjdHMvanMvbmRidGVzdCIsImFyZ3YiOlsiL3Vzci9iaW4vbm9kZSIsIi9tZWRpYS9kYXRhL1Byb2plY3RzL2pzL25kYnRlc3Qvbm9kZV9tb2R1bGVzLy5iaW4vbmRiIiwiaW5kZXguanMiXSwibm9kZUV4ZWNQYXRoIjoiL3Vzci9iaW4vbm9kZSJ9"};</script>
Maybe the most important part:
Core dump in journal
The started processes look like (after crash):
Steps to reproduce
add
"debug": "ndb index.js"
to package.jsonThe same happens when tried on a larger, more complex expres.js based project.
Tell us about your environment:
I tried installing google-chrome, in hope that it might install some missing packages / libraries, but nothing changed.
What is the expected result?
The NDB debugger window works, and doesn't show the 'Aw, snap!' crash text
What happens instead?
The NDB debugger window crashes with 'Aw, snap!' text
Note
90% this is not an issue with NDB, so sorry for that, but still would like to ask the community for directions
The text was updated successfully, but these errors were encountered: