Node App works without debugger but now fails silently when using debugger?
EDIT: Screenshots added (below). I tried cloning the app from the repo again, `npm i`, didn't work. I downloaded WebStorm again and cleared the caches from `~/Library/caches`. Still remains the same problem (there must be other caches, as the new WebStorm opened my project with all my existing plugins). I'm at a complete loss.
First, I realize that the very premise of this post is a bit vague, but I find myself in a situation that I can't solve. But basically I want to know what could possibly be the difference(s) between running an app 'normally' and running under the debugger. Apart from the issue noted below, I've noted that my app fails in different ways while using debugger when not -- something is different.
I'm working on a complicated Node app and have a debugger configuration set up for it. All was working fine but I made a few changes and suddenly, although the app continues to boot without debug mode, it fails silently partway through the boot when I run it under the debug configuration. There is nothing in the debug config other than to set the javascript file and the working directory, like always.
I've done these things
- Gone back to the 'develop' branch to see if it was something I'd changed in my code, but the same thing happens
- Restarted WebStorm after invalidating caches
- Made a new debug configuration
- Tried tracing from the last known log before silent failure
- Tried restarting the machine
- Tried disabling WebStorm plugins
but nothing works. I know that it's almost certainly something in my app or setup, but what I don't understand is why it would run differently under a debug config than without. And why, after weeks using the debugger with the app, it should suddenly not work.
What should I look for that might be making the difference?
The only other thing of note is that I installed an update to Material Theme UI to 4.11.0 and since then the UI has been acting weird -- buttons (like those to run the app and debug it, in the top bar) are disappearing, as are breakpoint symbols in the gutter. I've restarted the app several times, and also disabled all the plugins I've installed, but it doesn't change things.
- WebStorm 2019.3
- MacOS 10.14.5
- Node 12.13.0
请先登录再写评论。
UI problems are likely caused by Material UI plugin, but are hardly related to debugging.
Can you elaborate on your issue? What do you mean saying that the app fails? What does your run configuration look like?
Some screenshots/screencast that illustrate the issue would be helpful
Of course. I have a screencast but I can't seem to upload it here.
Here's the output when I run without debug:
And here is running under debug:
One can see that it skips the majority of boot steps. I know you can't debug my app, but this has been working fine for weeks with debug, and I'm trying to understand what might have changed. I tried removing node_modules and cache, made no difference.
My debug config is
Thanks for any help - this is very frustrating
Are you sure that the steps are really skipped? The Node.js process output (i.e. everything that is written to the
process.stdoutandprocess.stderrdirectly) plusconsole.log()logging, etc. are normally written to Console tab when debugging. From your screenshot it seems that the Console tab of the Debug tool window is hidden, only the interactive debugger console (Debugger Console) is shown. Please make sure that this tab is visible - can you see the output?Thank you! How amazingly simple an answer. I'd hidden console some time ago, to focus on the other debug windows. Many thanks!