|
@kovid and @CHALEY
I didn't really expect Calibre to restart from debug, I was just reporting that I was trying to cover all the bases. Also to report that Calibre itself didn't add any extra details to the debug log once the key strokes were sent.
@compurandom
I'm running Windows 10 with 16GB memory of which only 4.2GB is used when Calibre is up and running. So plenty of free memory.
Yes I know I can work around the issue by closing down and clicking the icon again or run the debug exe when I need to get a debug log for an issue. But something has changed from 4.23 to 5.2 ( I missed out all the intermediate releases) to cause this issue.
So my responses to this thread was just me adding more info to the issue that another person initially reported in a hope to help find out what has changed.
|