http://bugs.winehq.org/show_bug.cgi?id=28950
Bug #: 28950 Summary: Nitro PDF Reader remains active after exiting Product: Wine Version: 1.3.0 Platform: x86 URL: http://install.nitropdf.com/reader/en/nitro_pdf_reader .exe OS/Version: Linux Status: NEW Keywords: download, regression Severity: trivial Priority: P2 Component: ole32 AssignedTo: wine-bugs@winehq.org ReportedBy: gyebro69@gmail.com CC: huw@codeweavers.com Classification: Unclassified Regression SHA1: 6d1ef3a6a64f0fabf05ce1bba5f0ec4373684786
Created attachment 37215 --> http://bugs.winehq.org/attachment.cgi?id=37215 plain terminal output
The application doesn't exit cleanly, it is still running after quitting, consuming 100% CPU power. I have to kill the process NitroPDFReader.exe manually.
Still present as of wine-1.3.31-172-g7df0245.
Workaround: winetricks gdiplus
The application exits cleanly in Wine-1.2.3 and the problem is present since 1.3.0:
6d1ef3a6a64f0fabf05ce1bba5f0ec4373684786 is the first bad commit commit 6d1ef3a6a64f0fabf05ce1bba5f0ec4373684786 Author: Huw Davies huw@codeweavers.com Date: Thu Jul 22 13:37:19 2010 +0100
ole32: Implement cross-process drag and drop.
:040000 040000 ab88cc6bf0936bc4adc7bff0673415282613d919 065c727204a46d01708bc01f10484cad8527e1a2 M dlls
git checkout 6d1ef3a6a64f0fabf05ce1bba5f0ec4373684786 >> hangs on exit git reset --hard HEAD^ >> exits normally
Other opened bug reports with this commit: bug #23827 and bug #25749 Please let me know if you need a log with debug channels enabled.
wine-1.3.31-172-g7df0245 Fedora 15 x86 Gnome 3 (compositing) Nvidia gfx card
http://bugs.winehq.org/show_bug.cgi?id=28950
--- Comment #1 from Austin English austinenglish@gmail.com 2011-10-31 12:23:22 CDT --- What is native gdiplus needed for?
http://bugs.winehq.org/show_bug.cgi?id=28950
--- Comment #2 from GyB gyebro69@gmail.com 2011-10-31 12:28:17 CDT --- (In reply to comment #1)
What is native gdiplus needed for?
No idea, but that worked around the problem.
http://bugs.winehq.org/show_bug.cgi?id=28950
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |madewokherd@gmail.com
--- Comment #3 from Austin English austinenglish@gmail.com 2011-10-31 13:39:14 CDT --- Weird..perhaps Vincent would be interested then.
http://bugs.winehq.org/show_bug.cgi?id=28950
--- Comment #4 from Huw Davies huw@codeweavers.com 2011-11-16 07:21:56 CST --- Is that because winetricks gdiplus rolled in native msxml3 by any chance?
I've just sent a patch that fixes a bug in msxml3 that prevented this app *starting* for me. It exits cleanly too.
http://bugs.winehq.org/show_bug.cgi?id=28950
--- Comment #5 from GyB gyebro69@gmail.com 2011-11-16 10:59:02 CST --- This is really weird... on my current system (Fedora 16, newly installed a week ago) I can't reproduce the problem: the application doesn't hang on exit. It quits normally, but I often see such messages in the terminal, after the application exited: wine client error:29: write: Bad file descriptor wine client error:29: write: Bad file descriptor
I also see several wininet messages, which were missing on my previous Fedora installation. They're printed after I chose to exit the application: fixme:wininet:InternetSetOptionW Option INTERNET_OPTION_CONNECT_TIMEOUT (8000): STUB fixme:wininet:InternetSetOptionW INTERNET_OPTION_SEND/RECEIVE_TIMEOUT/DATA_SEND_TIMEOUT 8000 fixme:wininet:InternetSetOptionW INTERNET_OPTION_SEND/RECEIVE_TIMEOUT/DATA_SEND_TIMEOUT 8000
Likely some kind of network activity is taking place when the program quits, which didn't succeed on my previous system, leading the app to hang. If no one else can reproduce the problem, I reckon this is invalid.
I must add that all testing was done in a clean wineprefix, and during the regression test I received both bad and good results.
http://bugs.winehq.org/show_bug.cgi?id=28950
--- Comment #6 from Austin English austinenglish@gmail.com 2011-11-16 13:08:39 CST --- (In reply to comment #4)
Is that because winetricks gdiplus rolled in native msxml3 by any chance?
It does not.
http://bugs.winehq.org/show_bug.cgi?id=28950
GyB gyebro69@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID
--- Comment #7 from GyB gyebro69@gmail.com 2011-11-20 09:14:02 CST --- I can't reproduce the problem on my current system with Wine-1.3.33 or with any earlier versions either. The application does exits, only these messages suggest that something wasn't quite right: wine client error:25: write: Bad file descriptor
Probably INVALID.
http://bugs.winehq.org/show_bug.cgi?id=28950
GyB gyebro69@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #8 from GyB gyebro69@gmail.com 2011-11-20 09:14:37 CST --- Closing...invalid.
-
wine-bugs＠winehq.org