Another crash in 4.0d

Looks like it had trouble accessing something on the clipboard

7167.Logos4Crash.txt

8664.Logos4.log

These crashes come from Windows/.NET and are not caught/processed by Logos. I do wish/humbly suggest that Logos wraps their I/O and system calls in try/catch blocks so something a little more elegant can be done with these instead of bombing the user out when something fairly typical inside of Windows happens.

Find more posts tagged with

Comments

Melissa Snyder

Are you running Logos 4 on a Mac in Parallels or similar program? See this thread, http://community.logos.com/forums/t/19839.aspx.

NetworkGeek

https://community.logos.com/discussion/comment/152627#Comment_152627

Hi Melissa,

No - I am running PC version, 4.0d SR-1, on Windows Server 2008 R2 (server version of Windows 7). Not in a VM, just running natively. I was copying and pasting lemmas doing some syntax searches, then I was copying a screen shot to paste into Paint. I closed paint and went back to Logos when it crashed.

Dave Hooton

I do wish/humbly suggest that Logos wraps their I/O and system calls in try/catch blocks so something a little more elegant can be done with these instead of bombing the user out when something fairly typical inside of Windows happens.

I would agree that there are situations where a crash can and should be avoided. But it's difficult to know how to inform the users so that they may continue eg. "Another application has locked the clipboard please close open applications before retrying the operation"!