FARR stops working after win7 locked

[kigero]

I'm using FARR 2.93.01, and after my windows 7 machine locks, when I log back on FARR doesn't respond to the key combination (win+space), and selecting "Show Find and Run Robot" from the right click menu doesn't show the window either.  Earlier versions on my old XP machine worked fine, and this version works fine until the computer is locked.  It seems like it's only when the machine is locked for a long period of time.  Restarting FARR gets rid of the issue.  Possibly unrelated, but the settings screen pops up quite a bit as well, seemingly randomly - sometimes at startup, sometimes I'll just notice that it's open behind other windows. 

Any ideas what's going on?  Thanks!

[mouser]

Hmm.. strange.. anyone else experiencing this?

Can i ask what setting you have for the General tab of options, under "Inactive Memory Use"?

[kigero]

I've got it set to "Stay in Memory Longer".

[mouser]

Can you try changing that and seeing if that has any effect?

[kigero]

I changed it last night to "Average Memory Use", and so far so good - I'll reply back if that doesn't fix it.  Thanks!

[kigero]

Seems like that was the culprit, I haven't had it lock up on me since I changed that setting.  I'm still getting the config dialog popping up randomly though, so that is apparently not related.  I'm not too worried about that though.  Thanks!

[kigero]

Well unfortunately, it seems I was a bit hasty.  I'm still getting the lockups, just not as frequently.  Any other information I can give you to help with debugging?

Thanks

[mouser]

if the main display won't show in this case it's hard to know what else to do.

what you could do is:
1. wait a long time after trying to restore it from the tray and make sure it doesnt wake up after like 5 minutes.
2. use alt+tab to make sure the window isnt hidden -- maybe something is moving it off screen.
3. when it hangs do ctrl+alt+del and see if its actually using any cpu in this state -- if it is using a lot of cpu that might suggest one kind of problem.
4. email me ([email protected]) and ill send you a test version that creates a debug log, maybe that will give us a clue.