[Bug 55705] New: PDF Xchange editor crashes
https://bugs.winehq.org/show_bug.cgi?id=55705 Bug ID: 55705 Summary: PDF Xchange editor crashes Product: Wine Version: 8.17 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: donescamillo(a)gmail.com Distribution: --- Wine 8.17 development branch. PdfXchange Editor free version i.e. not registered version. portable, version 10.0.1.371 Linux Mint 21.2 PdfXchange editor works OK, can highlight, add labels, images, whatever the free version allows. The problem is that after some time, when PdfXchange Editor is being closed, it hangs, and the dialog asking for forcing the application to close appears. This happens in previous versions, too. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=55705 --- Comment #1 from Austin English <austinenglish(a)gmail.com> --- Please attach the terminal output. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=55705 --- Comment #2 from donescamillo(a)gmail.com --- How do I get the terminal output? -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=55705 --- Comment #3 from donescamillo(a)gmail.com --- Created attachment 75552 --> https://bugs.winehq.org/attachment.cgi?id=75552 Log file after freeze -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=55705 --- Comment #4 from donescamillo(a)gmail.com --- Created attachment 75553 --> https://bugs.winehq.org/attachment.cgi?id=75553 Log file after crash -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=55705 donescamillo(a)gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- Version|8.17 |9.0 -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=55705 Christoph.Schmidpeter(a)gmx.de changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |Christoph.Schmidpeter(a)gmx.d | |e --- Comment #5 from Christoph.Schmidpeter(a)gmx.de --- I can confirm the sometimes occuring hang on trying to close the app after some time. I do not get a dialog to close the app though. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=55705 temp82(a)luukku.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |temp82(a)luukku.com --- Comment #6 from temp82(a)luukku.com --- the original reported version should not be changed. Please provide a working download link into URL field. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=55705 Ken Sharp <imwellcushtymelike(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|major |normal Version|9.0 |8.17 -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=55705 --- Comment #7 from mokopel352@limtu.com --- The hang has happened a little differently with different versions of PDF XChange and Wine. With the current version 10.8 of PDF XChange and recent versions of Wine I have seen the hang only with a licensed version that was behind a firewall. If the portable version is started from a terminal using `WINEDEBUG=fixme-all wine PDFXEdit.exe` then after about 40 minutes it will display: 0520:err:rpc:rpcrt4_protseq_np_wait_for_new_connection wait failed with error 87 0290:err:rpc:RpcAssoc_BindConnection receive failed with error 1726 0304:err:sync:RtlpWaitForCriticalSection section 00006FFFFE369480 "dlls/combase/rpc.c: dcom registered server interfaces" wait timed out in thread 0304, blocked by 0548, retrying (60 sec) 0624:err:sync:RtlpWaitForCriticalSection section 00006FFFFD77E3A0 "dlls/rpcrt4/rpc_server.c: server_cs" wait timed out in thread 0624, blocked by 0548, retrying (60 sec) The RtlpWaitForCriticalSection messages will repeat every 60 seconds. If in file dlls/rpcrt4/rpc_transport.c, line 752 in the rpcrt4_protseq_np_wait_for_new_connection function is changed to `if (conn->io_status.Status == STATUS_SUCCESS)` instead of `if (conn->io_status.Status == STATUS_SUCCESS || conn->io_status.Status == STATUS_PIPE_CONNECTED)` the hang doesn't happen anymore. I can't imagine that this is a proper fix since I assume the extra check must be there for a good reason. But maybe someone else with the problem can try it and see if it also works for them. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=55705 --- Comment #8 from donescamillo@gmail.com --- Wine 11.0, stable. I can confirm it, it still happens. Free license of the PdfXchange Editor, no firewall. Open a PDF document in PdfXchange in Wine and leave it. After sometime close the document or Wine, it will hang. Other than this PdfXchange works, you can scroll and highlight and do other operation, all OK until you close the document or Wine, then it hangs. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=55705 mokopel352@limtu.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mokopel352@limtu.com --- Comment #9 from mokopel352@limtu.com --- Are you able to try the fix that I found? -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=55705 --- Comment #10 from donescamillo@gmail.com --- No, I have not, I dont know how to apply this fix. Does it mean I have to rebuild Wine from source? Because this I really dont know how to do. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=55705 --- Comment #11 from mokopel352@limtu.com --- Yes. The source would need to have that one line changed and then it would need to be compiled. No problems have been experienced since doing that. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=55705 mokopel352@limtu.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC|mokopel352@limtu.com | -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=55705 KRosUser <kyle.kcsoftwares@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kyle.kcsoftwares@gmail.com --- Comment #12 from KRosUser <kyle.kcsoftwares@gmail.com> --- Related or duplicate of https://bugs.winehq.org/show_bug.cgi?id=39711 ? -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=55705 --- Comment #13 from donescamillo@gmail.com --- Just to confirm that the bug still happens in Wine 11.3 stable and PdfXchange Editor Portable 10.8.2 build 407, unlicened version (using only the free features). I have no firewalls installed. Also, I dont know how to build Wine with the fix that mokopel352@limtu.com suggested. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=55705 mokopel352@limtu.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mokopel352@limtu.com --- Comment #14 from mokopel352@limtu.com --- The fix no longer works for PDF XChange version 11. Version 11 freezes when attempting to use the program after about an hour of sitting idle. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=55705 --- Comment #15 from Ken Sharp <imwellcushtymelike@gmail.com> --- A new bug needs a new bug report. https://gitlab.winehq.org/wine/wine/-/wikis/Bugs -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=55705 --- Comment #16 from mokopel352@limtu.com --- The fix I found I'm sure wasn't a proper fix and never became an official patch. The real problem is the error message like what follows, which can be seen in the console when using WINEDEBUG=fixme-all: 0624:err:sync:RtlpWaitForCriticalSection section 00006FFFFD77E3A0 "dlls/rpcrt4/rpc_server.c: server_cs" wait timed out in thread 0624, blocked by 0548, retrying (60 sec) The fix I had for version 10 no longer affects this error in version 11. When this error happens, the program will then freeze, either in version 10 or in version 11. So if this error gets fixed properly so that version 11 runs, it's likely that version 10 will also be fixed. Version 10 is no longer publicly available from the publisher's website, so if a new bug report needs to be created, that would make this one moot. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=55705 --- Comment #17 from mokopel352@limtu.com --- Created attachment 81640 --> http://bugs.winehq.org/attachment.cgi?id=81640 patch for rpc_transport.c A patch has been attached. This patch extends on the previous workaround. So far PDF XChange version 11.0.1 has not been freezing in my testing. This patch does not resolve the cause for the rpc time out errors, so it is not a proper fix. It just keeps wine from trying to process the error and then freezing. But maybe it will help someone else who may be experiencing this freeze until a developer is able to take a look into it. To be able to see the rpc time out error, use WINEDEBUG=fixme-all to avoid the console from being overrun by all the other error messages. I use X11, so that may also be a factor in how this error gets handled and whether or not the program freezes. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=55705 --- Comment #18 from mokopel352@limtu.com --- This bug looks to be related to bug 60334. The exact same error message with the wait handle count as described in that bug report is the first message to be displayed when problems are about to be noticed in PDF XChange. The first error message that gets reported is "err:rpc:rpcrt4_protseq_np_wait_for_new_connection wait failed with error 87, wait handle count 65." -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=55705 Filip Řeháček <filip.rehacek@outlook.cz> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |filip.rehacek@outlook.cz --- Comment #19 from Filip Řeháček <filip.rehacek@outlook.cz> --- Created attachment 82326 --> http://bugs.winehq.org/attachment.cgi?id=82326 rpcrt4: wait on named-pipe listeners in chunks (64-handle limit workaround, bug 60334) -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=55705 --- Comment #20 from Filip Řeháček <filip.rehacek@outlook.cz> --- I can confirm this bug and provide a working workaround, with log evidence. Affected software: PDF-XChange Editor 11.1.0.0 under Wine 11.19, AUR package pdf-xchange. Crash sequence captured in a 216k-line debug log (log available on request): after roughly 40 minutes of use the app dies with: 0120:err:rpc:rpcrt4_protseq_np_wait_for_new_connection wait failed with error 87 0454:err:rpc:RpcAssoc_BindConnection receive failed with error 1726 0024:err:sync:RtlpWaitForCriticalSection ... rpc_server.c: server_cs ... blocked by 012c, retrying (60 sec) 0024:err:sync:RtlpWaitForCriticalSection ... combase/rpc.c: dcom registered server interfaces ... blocked by 012c ... 0024:err:seh:call_seh_handlers invalid frame ... 0024:err:seh:NtRaiseException Exception frame is not in stack limits => unable to dispatch exception. This is the same "wait handle count 65" failure described in bug 60334: WaitForMultipleObjectsEx only accepts MAXIMUM_WAIT_OBJECTS (64) handles, once more than 63 named-pipe listeners are registered on one protseq the wait fails with error 87. RPCRT4_server_thread() then shuts down, a thread holds server_cs / "dcom registered server interfaces" forever, and every COM marshaling call deadlocks until the main thread dies. Workaround attached: wait on the listeners in chunks of at most 64 handles and cycle through them, instead of letting the wait overflow and kill the RPC server thread. Confirmed stable over long sessions; no change in behavior when under 64 listeners. Some earlier workarounds in this thread touched the io_status.Status check in the same function; on current wine that check already handles STATUS_PIPE_CONNECTED, so the remaining bug is the wait-handle overflow. Please consider this as a confirmation + working workaround. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=55705 --- Comment #21 from mokopel352@limtu.com --- (In reply to Filip Řeháček from comment #20)
I can confirm this bug and provide a working workaround, with log evidence. Thank you for providing this patch. I can confirm the fix.
-- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=55705 --- Comment #22 from donescamillo@gmail.com --- I hope it will go in the next Wine release -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=55705 --- Comment #23 from donescamillo@gmail.com --- It sort of happened again, but differently: When I tried to close the program, the program hung and the "FORCE QUIT" dialog appeared. Then after a while the program closed without me killing it, which is way better than before. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=55705 --- Comment #24 from mokopel352@limtu.com --- (In reply to donescamillo from comment #23)
It sort of happened again, but differently: When I tried to close the program, the program hung and the "FORCE QUIT" dialog appeared. Then after a while the program closed without me killing it, which is way better than before.
Check that all processes started by a previous version of Wine have been terminated properly. I have been using it for a number of hours now and it's been working perfectly. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=55705 --- Comment #25 from donescamillo@gmail.com --- I completely uninstalled the official stable version to avoid messing things up. I will run it again for a long time, using it too, and see how goes. But even with a slight delay when shut down I am OK with it. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
participants (2)
-
WineHQ Bugzilla -
WineHQ Bugzilla