Scripts manager crashes with stack overflow when new/edit selected

[conrad.drake]

Ver 2.6.3.0  (still trying to get IT to install 3.0    for the last three months)

Been happily working away on a large set of PDFs until yesterday when, for the first time in a few days, I needed to edit a script.   I can happily open the manager but the moment I click on new or edit (in the scripts view) the manager seizes up.  And I have to reach for TaskManager to stop PDFShell tools.

About half the time I get a "stack overflow" message when I do this.  Occasionally there's a "discard changes" pop up that Windows is waiting for.

Trying to get into the editor via Ctrl-click on a script results in a "hidden" window - it exists but I can't select it in Windows.

Is this just a result of being so far out of date?

[RTT]

Must be some state specific to your system that is triggering the bug. Try backup rename the file %appdata%\PDF-ShellTools\MyScripts.dat, to see if it is your list of scripts. Doing so will remove all your custom scripts from being listed.
If you have access to, backup rename also the HKEY_CURRENT_USER\SOFTWARE\PDFShellTools\MyScripts registry key, to check if the problem is related to any scripts editor saved settings.
If the problem persist, better try with version 3.0 (three months!!) before we can test other possibilities.

[conrad.drake]

Thanks once again for the prompt response.   I

t's not a problem in the my scripts.dat (shame) so I'll have to hunt down my IT  people

[conrad.drake]

Now at Rev 3.0.  Problem solved.

[conrad.drake]

Strangely, a similar behaviour has returned.  I am up-to-date except for one chinese language update.

Now, when I click "edit" (or "new") the button goes blue and that's where everything stops.   Task manager says shelltools is runnin but it is unresponsive.

It is using 0% CPU, which briefly pops up to 3% if I click on the window, and 2.036K memory.

When I stop shelltools running in New mode it says "stack overflow". When I stop if from "edit" is says "save changes (yes/no)"

Windows 7 professional, SP-1 on Intel I7-6600U CPU with 8G RAM.   I have no rights on this machine under our group policy:  doing anything at all requires an Administrator to remotely log in (e.g. installing updates; adding a new printer; adjusting time and date)

[RTT]

If you don't mind sharing your PDF-ShellTools settings, send me by email, or attach to a forum PM, a backup file of your settings. Maybe we get lucky and I can get the issue to fire here too. Create the settings backup from the manager bottom left "settings" named button.

[conrad.drake]

I don't have options to attach to PM so zip file is attached.  I've PM'd the password.  Hope there's a "smoking gun" in there!

[RTT]

No issues here, configured with your settings (you only have one script in your My Scripts list?), so I'm still clueless.
Check if you can run this process explorer tool (no installation needed). If yes, run it when the manager is stuck, locate and select the manager.exe process and create a minidump file, menu Process>CreateDump>CreateMiniDump, and send me that file.

[conrad.drake]

‘Curiouser and curiouser!” Cried Alice (she was so much surprised, that for the moment she quite forgot how to speak good English).’

I can do a dump for Chrome (local install) and Paint.net (needs admin to install) but not shell tools.

Error is "can't find the file" after telling it which file to dump to.

Interesting Manager.exe is in dark purple, the only process like that (rest are white, pink or blue)

[RTT]

I get that error if I run the 64-bit process explorer (procexp64.exe). It runs fine if I run the 32-bit (procexp.exe) instead.

That color is because the manager.exe is packed (the .exe is compressed). You can check the color meanings from the menu Options>ConfigureColors

[conrad.drake]

Sent by email as it's too large to attach (3MB compressed).  Hopefully that'll shed some light on whatever stupid thing I've done.

[RTT]

Nothing suspicious from the mini dump. The main thread is just running OnIdle tasks, waiting for input, and there isn't evidence of any unhandled exception.

I suspect you have the scripts editor window placed off-screen. If that's the case, after clicking the manager script edit button, hold down the Windows key and press the up-arrow, to maximize, or the right or left-arrow a few times to bring the window to the active screen.

[conrad.drake]

Nothing suspicious from the mini dump. The main thread is just running OnIdle tasks, waiting for input, and there isn't evidence of any unhandled exception.

I suspect you have the scripts editor window placed off-screen. If that's the case, after clicking the manager script edit button, hold down the Windows key and press the up-arrow, to maximize, or the right or left-arrow a few times to bring the window to the active screen.

No joy.  I agree with your analysis, it's like it's waiting for input.  And stopping from "edit" gets a "can't, program is waiting for input" message from Task Manager.   

Still getting "stack overflow" if I click "new" and stop with TaskManager, though.

I wonder if I've got a display driver problem which is causing this behaviour? 

I'll play with a few things later this week (got some promises to keep before then) and report back.

Thanks again.

[RTT]

Try inspecting the windows with this WinSpy++ tool, to check, and eventually edit, the state and position of the window with "Scripts editor" as caption, under the Manager.exe process.

[RTT]

Instead of opening the scripts editor from the manager, try open it directly to see if anything changes. To do this, hold down the CTRL key, while clicking a script menu item from the shell context PDF-ShellTools>My Scripts sub menu. This will open the clicked script directly in the editor, from where you can edit, run or create new ones (if the editor indeed shows up this way).