when doing a suspend-resume cycle with a downtime of e.g. 1 to 4 days then OHM
is no longer interactive but only displays a white main window with sub windows
not responding either.
to me it looks like some timer event or other logging requests got heavily
queued to the application. maybe some math for the time difference or whatever
runs havoc in such a sequence.
suggestion for a work around:
as long as the problem is not fixed (this might be hard to debug due to the
special state conditions) the default behaviour should be to turn off OHM data
capturing and display update. an option for e.g. developers or bold testers
should be added to temporarily re-enable the previous problematic behaviour.
see also:
http://stackoverflow.com/questions/9519919/notification-when-windows-enters-in-s
leep-mode
http://stackoverflow.com/questions/7253714/get-notified-about-windows-is-going-t
o-sleep-waking-up-in-c
Original issue reported on code.google.com by alexande...@hdle.com on 26 May 2015 at 7:19
Original issue reported on code.google.com by
alexande...@hdle.comon 26 May 2015 at 7:19