salamander 3 beta stuck in an endless startup crash loop

[lukast]

From time to time the S3 beta will cease to start, and instead states an 'error has occured' (with no further details), followed by the option to submit a bug report. following that, salamander tries to restart itself, but, alas, the error occurs once again, until the system (w7 x64) is restarted or logged off and on.

any ideas on how to avoid this?

do you think rolling back a version would prevent this happening?

thank you very much!

[Jan Rysavy]

Did you enter your email address to the bug report?

[lukast]

i have not, will do next time it happens, thank you.

[Jan Rysavy]

Thank you. Please send me your email (after submited bug report) to jan.rysavy@altap.cz and I will look at this problem and let you know.

[lukast]

sent.

[lukast]

sent about 5 of those since yesterday for each crash.

[lukast]

alas, some more have been sent since. :/

[lukast]

bump

[lukast]

a couple more sent

[Jan Rysavy]

I walked through all crash reports you submitted. This problem is related to clipboard content - there is some COM Data Object on clipboard (IDataObject) that crashes as soon as we call IDataObject::GetData method. We know this problem from another bug reports but unfortunately we are not able to reproduce it.

Could you please focus on latest application you used to copy some content to clipboard (Ctrl+C) before Salamander crashed?

You can try to copy some plain text (from notepad.exe) to clear clipboard content instead of restarting your computer.

There are clipboard viewer utilities we can probably use to find out more:
http://code.google.com/p/clipboardviewer/
http://www.peterbuettner.de/develop/tools/clipview/
http://freeclipboardviewer.com/

[lukast]

thank you for the reply; will try to keep that in mind for next time it happens. i have a few theories now that you mentioned clipboard but i am not jumping to conclusions yet...

[lukast]

i started clipboard viewer at system startup, and just experienced one of these salamander startup crashes. the clipboard viewer, however, was reporting no data to display right after the crash (please see attached pic). the data type seems to be reading 'deviceindependentbitmap'. though that may just be the screen grab that i took _after_ the crash happened. prior to that i was working with an audio sw (that uses xml data i believe to store data in the clipboard). either way, i saw nothing in clipboard viewer.

just checked-- when working with said software, usually, the clipboard holds data along the lines of (e.g.):
"<?xml version="1.0"?>
<vst-xml version="1.1">
<region id="874462800">
<filename>D:\!!!finished_work_pending_projects\201401_Land_Rover\!!!!\toppy_174.wav</filename>
<start>55</start>
<end>7797</end>
<projectTime domain="quarterNotes">129.99985489526367</projectTime>
</region>
<region id="874462800">"

[Jan Rysavy]

Interesting, thank you. Did it help to clear clipboard with some plain text?

[lukast]

Interesting, thank you. Did it help to clear clipboard with some plain text?

that i forgot to try, will try next time (if) it happens, and report back.

thank you.

[lukast]

Interesting, thank you. Did it help to clear clipboard with some plain text?

that i forgot to try, will try next time (if) it happens, and report back.

thank you.

ok, so upon another salamander crash (and a subsequent string of crashes on startup), the clipboard viewer was again showing nothing. opening wordpad, typing in a random string, going ctlr+c and restarting salamander has then indeed fixed the startup crash loop.

edit-- i seem to have narrowed it down. the crash occurs when a certain type of object had been added to the clipboard in a certain application prior to launching salamander. for this object, i indeed see nothing in clipboardviewer, or in wordpad if i try to flush it by ctrl+v. other types of objects from that same application, when added to the clipboard, do not cause salamander to crash on startup. these 'harmless' objects in clipboard do show xml data in cliboardviewer.