Skip to main content
Known Participant
March 5, 2006
Question

ESTK crashing when debugging

  • March 5, 2006
  • 24 replies
  • 1936 views
Here is a sample script that creates a menu item in the context thumbnail menu in Bridge. You save this script as a jsx file and place it in your StartUpScripts folder.

When this script runs, the debugger halts at the debugger statement, the line is highlighted in yellow and the cursor is frozen at the start of the line (it does not blink). About 3 seconds later the ESTK crashes.

Could someone else please try this on their computer to see if you can duplicate this behavior. Any suggestions would be most appreciated.

Thanks.

Here is the script:

#target bridge

$.level = 0;

if ( BridgeTalk.appName == "bridge" ) { // only load into bridge

> // create menu

> var cmdMenuShell = new MenuElement('command', 'Menu shell ...', 'before Thumbnail/Cut-');

> // execute menu

> cmdMenuShell.onSelect = function() {

>> $.level=1; debugger;

>> alert("Hello Menu shell");

> }

}
This topic has been closed for replies.

24 replies

hillrgAuthor
Known Participant
March 28, 2006
One last update. The crash behavior in continuing, even though I am limiting myself to only using the primary monitor. I have checked the pref file and there are no negative coordinates.

The solution I have found is to close the ESTK window before running Bridge. Then when Bridge encounters an error or a debugger statement it opens the ESTK, and all is good.

Rory
Participating Frequently
March 26, 2006
Okay, thanks again.

tom
-----
hillrgAuthor
Known Participant
March 25, 2006
It happened again, right after I posted. Moving the ESTK window back to the primary monitor, closing and re-opening the ESTK solved the problem, without disabling the monitors.

Rory
Participating Frequently
March 25, 2006
Thakns! Please let me know if it ever happens again.
hillrgAuthor
Known Participant
March 25, 2006
Here you go Tom - http://members.shaw.ca/hillrg/RorySystemInfo.zip.

Rory
Participating Frequently
March 25, 2006
Doh! I forgot you're on Windows. In that case go here:

Start>All Programs>Accessories>System Tools>System Information and save the complete data in a .nfo file for me.

tom
-----
Participating Frequently
March 25, 2006
One more request, Rory. Can you create a system information file and post it for me to download? I'd like to compare yours to the other system that this occurs on and find any parallels...

Go to Applications:Utilities:System Profiler and save the profile as an RTF file.

Thanks!

tom
-----
Participating Frequently
March 25, 2006
No problem! Your prefs gave it away when I saw all the negative values for the window coords. Thanks for getting that to me, and the crash log. Resetting the monitors andd moving your windows to the main one must have helped clean up the prefs.

tom
-----
hillrgAuthor
Known Participant
March 25, 2006
You appear to have nailed the problem Tom. When I disabled all but one monitor the ESTK did not crash. When I re-enabled my other monitors, but kept all the CS2 windows (Bridge, Photoshop and ESTK) on the primary monitor it still worked. It also still works with the ESTK and Bridge on the second monitor now, so by disabling and re-enabling the monitors something was fixed.

I saved a crash log before disabling and re-enabling the monitors. If you are still interested it is at http://members.shaw.ca/hillrg/appcompat.zip. Hopefully this can help adobe.

Tom - thanks very much for sticking with me and solving this issue. If it occurs again I will know what to do.

Rory
Participating Frequently
March 23, 2006
I've heard of one other instance of crashing that was also related to dual high-res monitors, but that wasn't the same steps as yours and it was never reproducible on other machines. It involved just dragging the ESTK window about. I can't reproduce your crash on the systems I have available to me. Is there a chance you could try it on another system or with only one monitor active on yours and see if it still occurs?

Also, if you can get me a crash log, that might help to show what's happening.