Debugging doesn't work

[carloquinonez]

I'm on a Mac and whenever I try to debug a JS script, no debug console appears, I can't open the "Scripts and Add-ins" panel to stop the script, and I can't quit Fusion360 unless I force-quit it. The OS firewall is turned off, and the firewall in the 3rd party malware protection software my company installs is also disabled.

This morning, I tried uninstalling Fusion360 following the instruction posted elsewhere (deleted a ton of folders manually...) and the problem still persists.

Anyone have any suggestions? This only happens at work - on my home Mac, debugging works just fine. 

[hithere8]

It does not work in Windows either.

As shown in the screenshot, at console, when I hit enter, nothing happened. 

I reinstalled Chrome, Fusion, did not help.

 

[liujac]

Hi,

I tried debugging JS with the latest Fusion 360 on OS X 10.10.5. The web inspector is displayed and the debugging can work. There is another issue, one blank dialog is displayed along with the web inspector when debugging JS, mouse hover on the title bar of the blank dialog, Fusion 360 crashes. We are investigating this issue. Is that the problem you met?

Regards,

Jack

[hithere8]

Hi Jack,
Thanks for checking this. The problem I have is actually on Windows. I encountered the same on two Windows computers. This happened only during the past two weeks. Before that, I was able to use that console window for debugging. Without that, it becomes quite annoying.
Could you please help check on Windows system?
Thanks.

[carloquinonez]

Nothing happens when I click on "Debug" - the application focus doesn't even change. Once I've clicked on Debug, I can't open the "Scripts/API" dialog box again nor can I quit fusion. I was going to take a screencast to show you what's happening, but it turns out Screencast isn't launching on my mac either...

I'm running MacOS 10.12.1 at work. I also run 10.12.1 on my mac at home, but that doesn't have any problems debugging.

[liujac]

Hi @hithere8,

I could not reproduce this problem on Windows until I updated Chrome to version 54. I doubt it's regression bug of Chrome v54. The current workaround is to install a build of Chrome v53. I will log a defect to chromium org.

Regards,

Jack

[liujac · Accepted solution]

Hi @carloquinonez,

I reproduced this issue on OSX 10.12.1. I logged a defect in our internal system. Thanks for reporting this issue.

Regards,

Jack

[hithere8]

Thanks for checking this out. Appreciated!