Running the Emulator Debugger causes XDK to freeze

[Noah_S_]

Hi, I'm new to Intel XDK and have enjoyed it, except when I run my app in the emulator and try to view the debugger. If I run the debugger, the main window becomes unresponsive (it isn't "not responding" according to Windows; I just can't click or do anything). If I close the debugger, the window remains like this for a good 2 minutes before I can resume working. 

This means I can run the debugger once, see what errors were caught, and then I have to wait 2 minutes to do anything else.

Any ideas why this might be happening? I've tried different devices and I'm not sure what else to try. Thanks!

[Barry_Johnson]

FWIW, I have off and on experienced precisely the sort of behavior you describe, where the whole thing basically locks up with the emulator. Then, strangely, it will occasionally stop misbehaving and work fine. I personally have largely bailed on the emulator and am taking the on-device debugging route which has been much more reliable for me (and while firing it up on the device is slower than the emulator *can be*, it is much faster than the emulator usually *is* (as well as being a higher-fidelity match to the final runtime environments). I might invest more time in sorting out the problem in the emulator if by solving it I could do 95%+ of my testing via emulation, but mostly I feel like the emulator becomes this additional device I end up supporting more than an enabler.

[PaulF_IntelCorp]

Please use the Debug tab for the most accurate results. Note that when using the Debug tab you are debugging on a Crosswalk runtime, so you will get identical results if you build with Crosswalk. Please see this doc page for more details: https://software.intel.com/en-us/xdk/docs/intel-xdk-debug-and-test-overview