https://bugs.winehq.org/show_bug.cgi?id=38880
Bug ID: 38880 Summary: Evernote fails to start from time to time Product: Wine Version: 1.7.46 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: robert.munteanu@gmail.com Distribution: ---
Evernote fails to start from time to start and requires a
wineserver -k
to clear the problem and restart. When the problem occurs the Evernote.exe process starts but appears to hang with 300% CPU usage. A second or third attempt usually work.
In the failure scenario the auxiliary EvernoteTray.exe and EvernoteClipper.exe processes do not appear.
https://bugs.winehq.org/show_bug.cgi?id=38880
Guillaume R guillaumeraffin@free.fr changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |guillaumeraffin@free.fr
--- Comment #1 from Guillaume R guillaumeraffin@free.fr --- I may have found a quick "fix" for this problem: run EvernoteCleanup.exe (it's in the same directory) before starting Evernote, and everything should be fine.
https://bugs.winehq.org/show_bug.cgi?id=38880
winetest@luukku.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |winetest@luukku.com
--- Comment #2 from winetest@luukku.com --- What version? It needs to be exactly the same version what was tested so this bug can be marked fixed. Also does this happen still? Pointing into a download would help too.
https://bugs.winehq.org/show_bug.cgi?id=38880
--- Comment #3 from Guillaume R guillaumeraffin@free.fr --- This still happens in wine 2.0-rc4 with Evernote 6.4.2.3788.
I was able to make it happen several times by starting a synchronization, waiting for the sync icon to stop moving, and then closing the evernote window and the tray icon (which wouldn't close with the window). At that point, trying to launch Evernote.exe won't work (it will close immediately). But if I wait several minutes, I'll be able to launch Evernote again!
Unfortunately this method doesn't always reproduce the bug.
The problem here is that even if the window is closed and the tray icon has disappeared, Evernote.exe is still running! And this prevent Evernote from being launched.
The invisible Evernote.exe will close on its own after some time (I had to wait around 5 minutes), allowing the user to start Evernote correctly again.
Running EvernoteCleanup.exe doesn't work anymore. What works is killing the Evernote's process, by any way you can/want (wineserver -k, kill <pid>, the system's monitor, etc).
https://bugs.winehq.org/show_bug.cgi?id=38880
--- Comment #4 from Guillaume R guillaumeraffin@free.fr --- Created attachment 56891 --> https://bugs.winehq.org/attachment.cgi?id=56891 log when you try to launch evernote while it's still invisibly running
https://bugs.winehq.org/show_bug.cgi?id=38880
--- Comment #5 from Guillaume R guillaumeraffin@free.fr --- Created attachment 56892 --> https://bugs.winehq.org/attachment.cgi?id=56892 log when evernote closes automatically after some time
https://bugs.winehq.org/show_bug.cgi?id=38880
--- Comment #6 from Guillaume R guillaumeraffin@free.fr --- Created attachment 56895 --> https://bugs.winehq.org/attachment.cgi?id=56895 log when closing evernote with the tray icon
The window and the tray icon disappears but the evernote process doesn't end.
https://bugs.winehq.org/show_bug.cgi?id=38880
--- Comment #7 from Guillaume R guillaumeraffin@free.fr --- And one last thing: I didn't notice any massive CPU usage when I tried to launch Evernote while an invisible Evernote.exe was still running. So there's been some improvements :)
https://bugs.winehq.org/show_bug.cgi?id=38880
winetaste@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |winetaste@gmx.net
--- Comment #8 from winetaste@gmx.net --- (In reply to Guillaume R from comment #7)
And one last thing: I didn't notice any massive CPU usage when I tried to launch Evernote while an invisible Evernote.exe was still running. So there's been some improvements :)
I know this start issue from sometimes. So I tried a little bit, and now I habe a failing start with 75% CPU usage, but I did a wineserver -k before.
-
wine-bugs＠winehq.org