These are beginning to happen with a bit more frequency now. Even calling the MS debugger isn't telling me anything, and this log just dies in the midst of being idle. There are no updates to the error log.
And no crash log? How long had it been idle (roughly)?
Long enough for me to walk away, pour some fresh coffee and answer a phone call. Call it 7-10 minutes.
So its crashing because it feels rejected, and abandoned.. think you must have installed the "EXTRA-SENSITIVE" version
Sorry to hear you are having issues, so far so good here...
Please follow the instructions at http://wiki.logos.com/ProcDump to launch Logos 4 via the procdump utility; this will wait for Logos to crash and grab a diagnostic dump when it does. (I don't remember the email address you should send it to if you do capture one, but I can find out at the office next week.)
The best e-mail to send developer-requested info to is Logos4feedback@logos.com. It's a good idea to reference the forum post the request was made in and a short description of the issue so I don't sit here looking at your e-mail and scratching my head about why you sent it. [;)]
Ok Bradley and Tonya. It's running and waiting, now we'll see if that watched pot ever boils.
Ok folks we have a winner! (almost)
While searching (CTRL+F) through Romans in the NASB95 for the word "just" I received the crash again: R6025 Pure Virtual Function Call - http://community.logos.com/forums/p/42191/314109.aspx
Procdump was running but I guess because it was running in the windows/system32 directory I got nothing, it didn't save the file, but actually wrote it as a continuing itteration of html files on my desktop, constantly overwriting the last one (weird).
I'll move procdump and try again.
While searching (CTRL+F) through Romans in the NASB95 for the word "just" I received the crash again
Wasn't able to repro by following these same steps.
Thanks; I think we'll need a crash dump from your machine to track this problem down.
I'm still trying to make this happen. I run it through ProcDump almost all the time. Today I didn't and it crashed again **sigh**
I'm sure these error logs are useless, but alas no crash dump. But I'll keep trying.
[View:http://community.logos.com/cfs-file.ashx/__key/CommunityServer.Discussions.Components.Files/78/5141.Logos4ErrorLogs.zip
I'm getting the feeling that procdump is somehow stabilizing something on my system.
Just a quick note that I have managed to email two individual procdumps for this issue to the address given above.
I hope that works.
I am still getting idle crashes. nothing in the logs at all. The last line in Logos4.log says:
2012-05-29 07:56:00.4502 1 Info LDLS4.AppModel App is now idle.
Ten minutes later the app crashed, offered to run through the debugger (Which I do not have installed) and I canceled/closed it.
I had submitted a few procdumps already. Are more needed? I had stopped running with procdump for awhile, I guess I'll get back on it.
