Crash: 4.0c: Unexplained out-of-memory exception while Logos sitting idle

I was off doing something in another app with Logos just sitting there in the background minding its own business, not in the middle of running anything I'd initiated (as far as I recall), when I decided to switch back to Logos, whereupon it crashed before even being able to show its face again. Log files attached. It's an out of memory exception, but I was not low on memory. I've got 8 GB of RAM and had very little else running at the time.

5025.UnexplainedCrash.zip

Find more posts tagged with

Comments

JimTowler

Hi Rosie,

I'm just going to guess, based on something a few lines into the crash log:

Out of memory error, then a few lines in: " ... Libronix.SearchEngine.QueryProcessor ... "

I'm thinking that maybe Logos4 re-ran a search, just as it does when you reopen the application, and it runs a query again. So, its not so much that is was doing nothing. By making it the foreground application, maybe you had in fact "initiated" something - a rerun of some or all of the open searches.

Just guessing ...

Rosie Perera

https://community.logos.com/discussion/comment/130315#Comment_130315

I'm thinking that maybe Logos4 re-ran a search, just as it does when you reopen the application, and it runs a query again. So, its not so much that is was doing nothing. By making it the foreground application, maybe you had in fact "initiated" something - a rerun of some or all of the open searches.

Yup, you're probably right, but that is no excuse for it to crash on me. I'm pretty sure I had run a search earlier in my Logos session, but it didn't barf on me then, and the results should have been cached anyway. Normally switching back to the application doesn't rerun whatever search was open when you were last looking at the Logos window. Even if Logos could be excused for running the search over again, and even if I'd somehow done something in the other app(s) I was running to reduce the amount of available memory to something that was too little for Logos to run a search in (very hard to believe given my system specs), I still don't like they way it throws an exception and crashes whenever it think it doesn't have enough memory to complete some operation. It should reserve an emergency block of memory at startup which it can use to fail gracefully (put up a message about what is going on and close if necessary) if/when it runs into a low memory situation.

JimTowler

https://community.logos.com/discussion/comment/130592#Comment_130592

I hardly believe that it crashes the way it does ...

Better would be if it failed ONLY the Search, or Sync, or Database write, or whatever ...

THEN, ask if its OK to complete a report back to Logos, ask us to write what we just did (but it should already know), and send the log(s) to Logos - but only if we approve it.

It should only crash if the lowest levels of the plumbing fall to bits. An error during the search or highlighting etc should not crash the whole world.

But maybe its external libraries or the .NET system itself with the issues?

MJ. Smith

https://community.logos.com/discussion/comment/130592#Comment_130592

Yup, you're probably right, but that is no excuse for it to crash on me.

Actually, I'd be happier if it didn't take so long to create the MS error report. 6-8 minutes down time for me. [:(]

JimTowler

https://community.logos.com/discussion/comment/130649#Comment_130649

Actually, I'd be happier if it didn't take so long to create the MS error report. 6-8 minutes down time for me.

WOW - thats way too long!!!

I have not seen a Logos4 crash for a week or so now, but I don't remember it ever being more than a few seconds to log/generate any reports.

Rosie Perera

https://community.logos.com/discussion/comment/130661#Comment_130661

Actually, I'd be happier if it didn't take so long to create the MS error report. 6-8 minutes down time for me.

WOW - thats way too long!!!

I have not seen a Logos4 crash for a week or so now, but I don't remember it ever being more than a few seconds to log/generate any reports.

Ditto. Well, I don't remember being given the option to generate the MS report in a long time now (just the Logos logs which get generated automatically and don't take long at all). I've rarely chosen to go ahead with the MS report because it wasn't until recently that I learned they didn't go just to Microsoft, but Logos gets them too and they can help. However even when I've tried it once or twice in the past, I don't recall it taking anywhere near as long as it is for you.

MJ. Smith

https://community.logos.com/discussion/comment/130663#Comment_130663

but I don't remember it ever being more than a few seconds to log/generate any reports.

I originally complained about length when it was just shy of 5 minutes in the initial release of 4.0 - each release since has added to the time. I would have complained more loudly if I'd known that the length was not everyone's experience. I'm running XP on a DSL connection.

Rosie Perera

https://community.logos.com/discussion/comment/130665#Comment_130665

That quote was actually from Jim Towler.

MJ. Smith

https://community.logos.com/discussion/comment/130676#Comment_130676

That quote was actually from Jim Towler.

Yes, I keep forgetting to double check if the forum software has messed up.

JimTowler

https://community.logos.com/discussion/comment/130676#Comment_130676

That quote was actually from Jim Towler.

I wasn't anywhere near it when it broke, and no-one saw me hide it afterwards, so don't blame me!!! [;)]

Dave Hooton

I was off doing something in another app with Logos just sitting there in the background

You also had a solo crash at http://community.logos.com/forums/t/14993.aspx - with no resolution.

Rosie Perera

https://community.logos.com/discussion/comment/130688#Comment_130688

You also had a solo crash ...

Goodness! I though I'd made it through my flight training with no such mishaps! [:)]

Melissa Snyder

https://community.logos.com/discussion/comment/130689#Comment_130689

Rosie,

I'll submit your log to development. I'm curious about the amount of .tmp files created and recorded in the log (TemporaryFileSearchResultReader). Could you check the Temp folder at C:\Users\Rosie Perera\AppData\Local\, and if there are a lot of files there starting and ending with 'tmp', as in the log, would you delete those?

Thanks,
Melissa

Update: Devs are asking for a full log if you have one from the crash (which I understand may be unlikely considering the nature of the crash).

Rosie Perera

https://community.logos.com/discussion/comment/130777#Comment_130777

Rosie,

I'll submit your log to development. I'm curious about the amount of .tmp files created and recorded in the log (TemporaryFileSearchResultReader). Could you check the Temp folder at C:\Users\Rosie Perera\AppData\Local\, and if there are a lot of files there starting and ending with 'tmp', as in the log, would you delete those?

Thanks,
Melissa

Update: Devs are asking for a full log if you have one from the crash (which I understand may be unlikely considering the nature of the crash).

Melissa, yes, there were a ton of .tmp files. I've deleted them. They were dated 5/19/2010, 4/5/2010, and 4/1/2010. The most recent two of those dates are dates when I had reported these mysterious crashes. I might have had another one on 4/1/2010 which I didn't report.

Unfortunately I wasn't running with full logging turned on, and as this bug is so intermittent it would slow me down quite a lot to run with it enabled just in the hopes of catching this crash again within the next month or two. But I'm willing to try if it's really that important. But I know it makes the logs harder to wade through for when I'm reporting run-of-the-mill bugs and crashes, and I've been told to turn off the full logging before because of that. I wish there were a mode where you could get two different log files generated side-by-side, the standard one, and the more detailed one, and then depending on the difficulty of tracking down the bug, one or the other log file would be most useful.

JimTowler

https://community.logos.com/discussion/comment/131042#Comment_131042

I expect, if the Logos developers wanted to, they could add a debug-level tag to the output logs. Then it would be easy for them to filter a level-3 debug log to only show level 0 and 1.

Its up to them wanting it, and then coding it. Not hard if they wish it ...