Crash on Exit

calkinscalkins
in Troubleshooting
Had this issue for a while now (since 2.x perhaps?). Everything seems to work fine except when we are done and exit the program we get an AppCrash. The faulty module is phython32.dll. I have spent a good deal of time searching google and the forums and cannot find anything with a similar issue. My event viewer logs and appdata logs are attached. I have tried also running the program as an Administrator.
Share on FacebookShare on Twitter Share on Google+

Comments

  • raoulraoul
    We are aware of a crash on exit, but it's actually been extremely difficult to track down. Also, I can't open that event log thing, I presume it's a Windows thing?
    Share on FacebookShare on Twitter Share on Google+
  • milonmilon
    Yeah, a Windows Event Log file. I haven't had time to look at it yet, but I'll let you know once I can.

    @raoul, does the crash on exit only affect Windows platforms?
    Share on FacebookShare on Twitter Share on Google+
  • milonmilon
    @raoul, I was able to extract the Windows Log data to plain text:

    Level	Date and Time	Source	Event ID	Task Category
Information	9/10/2017 8:06:04 PM	Windows Error Reporting	1001	None	"Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: OpenLP.exe
P2: 0.0.0.0
P3: 00000000
P4: python34.dll
P5: 3.4.4150.1013
P6: 5676f342
P7: c000041d
P8: 00121a08
P9: 
P10: 

Attached files:
\\?\C:\Users\Sound Booth\AppData\Local\Temp\WERDC53.tmp.WERDataCollectionStatus.txt
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WEREFFD.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF01E.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_OpenLP.exe_c6dfeba5023cecbb4a985f22719dcccd89f4f1e_ecba781b_3c1a0738

Analysis symbol: 
Rechecking for solution: 0
Report Id: d0ff84d6-c4ec-4077-89db-b14da133233d
Report Status: 97
Hashed bucket: "
Error	9/10/2017 8:05:48 PM	Application Error	1000	Application Crashing Events	"Faulting application name: OpenLP.exe, version: 0.0.0.0, time stamp: 0x00000000
Faulting module name: python34.dll, version: 3.4.4150.1013, time stamp: 0x5676f342
Exception code: 0xc000041d
Fault offset: 0x00121a08
Faulting process id: 0x199c
Faulting application start time: 0x01d32a919659c799
Faulting application path: C:\Program Files (x86)\OpenLP\OpenLP.exe
Faulting module path: C:\Program Files (x86)\OpenLP\python34.dll
Report Id: d0ff84d6-c4ec-4077-89db-b14da133233d
Faulting package full name: 
Faulting package-relative application ID: "
Information	9/10/2017 8:05:48 PM	Windows Error Reporting	1001	None	"Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: OpenLP.exe
P2: 0.0.0.0
P3: 00000000
P4: python34.dll
P5: 3.4.4150.1013
P6: 5676f342
P7: c0000005
P8: 00121a08
P9: 
P10: 

Attached files:
\\?\C:\Users\Sound Booth\AppData\Local\Temp\WER9B91.tmp.WERDataCollectionStatus.txt
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERAF39.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERAF59.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_OpenLP.exe_405e9ab93a92a61ddaf2f5a60cdb3b3fb079ac_ecba781b_3ef9c686

Analysis symbol: 
Rechecking for solution: 0
Report Id: d5b67577-b277-449a-944e-fe56bb916a6c
Report Status: 97
Hashed bucket: "
Error	9/10/2017 8:05:31 PM	Application Error	1000	Application Crashing Events	"Faulting application name: OpenLP.exe, version: 0.0.0.0, time stamp: 0x00000000
Faulting module name: python34.dll, version: 3.4.4150.1013, time stamp: 0x5676f342
Exception code: 0xc0000005
Fault offset: 0x00121a08
Faulting process id: 0x199c
Faulting application start time: 0x01d32a919659c799
Faulting application path: C:\Program Files (x86)\OpenLP\OpenLP.exe
Faulting module path: C:\Program Files (x86)\OpenLP\python34.dll
Report Id: d5b67577-b277-449a-944e-fe56bb916a6c
Faulting package full name: 
Faulting package-relative application ID: "
Information	9/10/2017 8:04:23 PM	Windows Error Reporting	1001	None	"Fault bucket 107851485177, type 1
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: OpenLP.exe
P2: 0.0.0.0
P3: 00000000
P4: python34.dll
P5: 3.4.4150.1013
P6: 5676f342
P7: c000041d
P8: 00121a08
P9: 
P10: 

Attached files:
\\?\C:\Users\Sound Booth\AppData\Local\Temp\WER3CDC.tmp.WERDataCollectionStatus.txt
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5082.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER50A2.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_OpenLP.exe_c6dfeba5023cecbb4a985f22719dcccd89f4f1e_ecba781b_0d387be5

Analysis symbol: 
Rechecking for solution: 0
Report Id: ae3fdc39-1f55-483f-9be2-65dd833eab83
Report Status: 268435456
Hashed bucket: d57e66c8bfeda8b5accbe888171e0926"
Error	9/10/2017 8:04:01 PM	Application Error	1000	Application Crashing Events	"Faulting application name: OpenLP.exe, version: 0.0.0.0, time stamp: 0x00000000
Faulting module name: python34.dll, version: 3.4.4150.1013, time stamp: 0x5676f342
Exception code: 0xc000041d
Fault offset: 0x00121a08
Faulting process id: 0x1f18
Faulting application start time: 0x01d32a9163aa72b8
Faulting application path: C:\Program Files (x86)\OpenLP\OpenLP.exe
Faulting module path: C:\Program Files (x86)\OpenLP\python34.dll
Report Id: ae3fdc39-1f55-483f-9be2-65dd833eab83
Faulting package full name: 
Faulting package-relative application ID: "
Information	9/10/2017 8:04:01 PM	Windows Error Reporting	1001	None	"Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: OpenLP.exe
P2: 0.0.0.0
P3: 00000000
P4: python34.dll
P5: 3.4.4150.1013
P6: 5676f342
P7: c0000005
P8: 00121a08
P9: 
P10: 

Attached files:
\\?\C:\Users\Sound Booth\AppData\Local\Temp\WERFC49.tmp.WERDataCollectionStatus.txt
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERFED.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER100D.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_OpenLP.exe_405e9ab93a92a61ddaf2f5a60cdb3b3fb079ac_ecba781b_3cac273d

Analysis symbol: 
Rechecking for solution: 0
Report Id: f08fa92e-01e3-487e-a6ef-1dbc06c786a2
Report Status: 97
Hashed bucket: "
Error	9/10/2017 8:03:45 PM	Application Error	1000	Application Crashing Events	"Faulting application name: OpenLP.exe, version: 0.0.0.0, time stamp: 0x00000000
Faulting module name: python34.dll, version: 3.4.4150.1013, time stamp: 0x5676f342
Exception code: 0xc0000005
Fault offset: 0x00121a08
Faulting process id: 0x1f18
Faulting application start time: 0x01d32a9163aa72b8
Faulting application path: C:\Program Files (x86)\OpenLP\OpenLP.exe
Faulting module path: C:\Program Files (x86)\OpenLP\python34.dll
Report Id: f08fa92e-01e3-487e-a6ef-1dbc06c786a2
Faulting package full name: 
Faulting package-relative application ID: "

    I hope this is useful in tracking down this issue!  Note that the log file lists python34.dll rather than python32.dll in the Problem Signature.  Also, the "attached files" aren't actually present, but @calkins could likely supply them if needed.
    Share on FacebookShare on Twitter Share on Google+
  • raoulraoul
    edited September 2017
    That crash report is useless. I don't know why macOS and Windows do that.

    The "crash" on exit affects all platforms. On Linux you just don't notice it because it happens silently in the background. Again, the crash has no effect on OpenLP because it's some weird corner case between OpenLP's Python code and Qt's C++ code while OpenLP is shutting down. We have an ongoing investigation into this.

    Please refer people back to this thread if they ask about it elsewhere... I'm tired of repeating myself.
    Share on FacebookShare on Twitter Share on Google+
  • raoulraoul
    "python34.dll" because we're using Python 3.4, not Python 3.2 (or 3.3 or 3.5 or 3.6).
    Share on FacebookShare on Twitter Share on Google+
  • calkinscalkins
    Please let me know if there is anything else that I can try or do to help you track this down.
    Share on FacebookShare on Twitter Share on Google+
  • calkinscalkins
    Is there anything else that we can obtain that might help you narrow this down?
    Share on FacebookShare on Twitter Share on Google+
  • raoulraoul
    No. We have a fair idea of what's going on, but we're still working out how to actually track down the exact location of the cause. It's something that's highly technical and seems to actually be occurring outside of OpenLP's code, in one of the libraries that we are using.
    Share on FacebookShare on Twitter Share on Google+
  • AndrewKAndrewK
    I remember reporting a "crash on exit" last year, I think it was. That was fixed in a later release, and I haven't seen it since.
    Share on FacebookShare on Twitter Share on Google+
  • MorrisonFrewMorrisonFrew
    This may be totally unrelated but may offer a little clue. I was having a "crash on exit" which was due to running OpenLP with the "Library" Section open although disconnected from the main body. Once I had reconnected it as a seamless whole I had no more problems.
    Share on FacebookShare on Twitter Share on Google+
  • raoulraoul
    Thanks for that insight. Technically that shouldn't make a difference, but clearly it does. What operating system are you using?
    Share on FacebookShare on Twitter Share on Google+
  • MorrisonFrewMorrisonFrew
    Sorry, Raoul, for the delay in replying. I am using Windows 10
    Share on FacebookShare on Twitter Share on Google+
  • milonmilon
    @MorrisonFrew, I also have Windows 10 on our OpenLP PC.  What are the exact steps to trigger the crash?  I'll try to reproduce it on my end.
    Share on FacebookShare on Twitter Share on Google+
  • calkinscalkins
    We un-dock the Media window and Service window. As soon as I do we get the issue on exit. I can echo what others are saying that it does not crash when they are docked in the main window. Here is a video of the issue including our typical usage: https://www.dropbox.com/s/9aj82kaw0eboqfd/Church-PC (713 099 511)_2017-10-31 11.41_cut.mp4?dl=0

    Share on FacebookShare on Twitter Share on Google+
  • raoulraoul
    @calkins can you disable Windows' error reporting please, do this again with the "debug" version of OpenLP and then either upload a debug log file here or e-mail it to our support address.

    http://manual.openlp.org/troubleshooting.html#i-have-been-asked-to-email-a-debug-log-where-do-i-find-this

    Share on FacebookShare on Twitter Share on Google+
  • calkinscalkins
    Why is it important that I disable the Windows Error reporting? I was having issues finding the 'Action Center' like google suggested. I finally disabled it from services.msc.

    I repeated the same steps in the video with the debug (-l debug) option enabled. The instructions above did not make it clear where to find the resulting log file but a quick dir openlp.log /s found it in the %appdata% folder.

    https://www.dropbox.com/s/gm9v8i4k88kqngk/openlp.log?dl=0
    Share on FacebookShare on Twitter Share on Google+
  • raoulraoul
    Windows Error Reporting doesn't actually do anything useful. In fact, it usually gets in the way of OpenLP managing to report its own errors.

    Thanks for the log file. Unfortunately it doesn't tell us anything, which probably means that the error is occurring after OpenLP has shut down, and while the last few pieces of memory are being cleared up. Now that I have a clearer understanding of how it is caused, I'll try to reproduce it myself on Linux.
    Share on FacebookShare on Twitter Share on Google+
Sign In or Register to comment.