# Remote Debugger Crashing Gateway **URL:** \ **Category:** Module Development\ **Created:** [July 24, 2024, 2:57pm UTC](https://forum.inductiveautomation.com/t/remote-debugger-crashing-gateway/93676 "2024-07-24T14:57:10Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![cody.tamaki](https://avatars.discourse-cdn.com/v4/letter/c/b487fb/32.png) [@cody.tamaki](https://forum.inductiveautomation.com/u/cody.tamaki)\ **Post date:** [July 24, 2024, 2:57pm UTC](https://forum.inductiveautomation.com/t/remote-debugger-crashing-gateway/93676/1 "2024-07-24T14:57:10Z")
Lately, my local development Ignition is crashing when I'm using the remote JVM debugger and running through breakpoints. Is there some kind of new "Pause the World" watcher that restarts the JVM or something? ---
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [July 24, 2024, 2:58pm UTC](https://forum.inductiveautomation.com/t/remote-debugger-crashing-gateway/93676/2 "2024-07-24T14:58:49Z")
If you have your debugger set to suspend all threads instead of the current thread then I suppose the service wrapper could think the JVM timed out and restart it if you were paused long enough... not sure though. Try one of these in ignition.conf: ```python wrapper.ping.timeout.action=NONE ``` ```python wrapper.ping.timeout.action=DEBUG ``` ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [July 24, 2024, 3:01pm UTC](https://forum.inductiveautomation.com/t/remote-debugger-crashing-gateway/93676/3 "2024-07-24T15:01:37Z")
Also make sure that your debugger and the gateway are using the **exact** same JVM version. You may have to install a platform JDK and set the gateway to use it instead of the bundled JRE.