Debugging via WebStorm causing NodeBB not respond when logging in
Hello, I start debugging and testing NodeBB internals using WebStorm, but when the debugging procedure starts, I cannot get redirected to last view page when I click the login button when I log in. The console shows:
/usr/bin/node --debug-brk=36534 app.js debugger listening on port 36534 5/7 11:58  - info: NodeBB v1.0.3 Copyright (C) 2013-2014 NodeBB Inc. 5/7 11:58  - info: This program comes with ABSOLUTELY NO WARRANTY. 5/7 11:58  - info: This is free software, and you are welcome to redistribute it under certain conditions. 5/7 11:58  - info: 5/7 11:58  - info: Time: Tue Jul 05 2016 11:58:54 GMT+0800 (CST) 5/7 11:58  - info: Initializing NodeBB v1.0.3 5/7 11:58  - info: [database] Checking database indices. 5/7 11:58  - warn: [plugins/load] The following plugins may not be compatible with your version of NodeBB. This may cause unintended behaviour or crashing. In the event of an unresponsive NodeBB caused by this plugin, run `./nodebb reset -p PLUGINNAME` to disable it. * nodebb-theme-lavender * nodebb-plugin-mentions * nodebb-plugin-category-notifications * nodebb-plugin-sketchfab * nodebb-plugin-emailer-local 5/7 11:59  - info: NodeBB Ready 5/7 11:59  - info: Enabling 'trust proxy' 5/7 11:59  - info: NodeBB is now listening on: 0.0.0.0:1111 5/7 11:59  - info: [plugins/spam-be-gone] Settings loaded
Debugging a paasword verification is something difficult. Because the code shows that verifying password forks bcrypt process. But unfortunately it could not get the result back when debugging.
It happens to me also, same using Visual Studio Code. What i do is login in dev mode, without debugging, and once the login cookie is set, you can debug nodebb correctly and its plugins.
Honestly i don't know why it happens.
@jarey Hopelessly, we could not catch message from generated process using WebStorm, I think this is a bug, or NodeBB maintainer could use the
debugmode to force bcrypt procedure to go within the debugging process instead of creating a new one.
Edit: update with the github issue for easier tracking in the forum.