openlp-core team mailing list archive

[Azaziah <suutari.olli@xxxxxxxxx>]

Before starting the actual debugging this is given as the reason:

An unhandled win32 expection occured in OpenLP.exe[3660].

Here's some Visual Studio 2015 Debugging data:

Unhandled exception at 0x6BF11A08 (python34.dll) in OpenLP.exe:
0xC000041D: An unhandled exception was encountered during a user
callback.

Exception thrown at 0x6BF11A08 (python34.dll) in OpenLP.exe: 0xC0000005: Access violation reading location 0x00000004.
If there is a handler for this exception, the program may be safely continued.

Unhandled exception at 0x6BF11A08 (python34.dll) in OpenLP.exe:
0xC000041D: An unhandled exception was encountered during a user
callback.

OpenLP.exe has triggered a breakpoint.

Call Stack:
 	[External Code]	
 	python34.dll!6bf238d2()	Unknown
 	python34.dll!6bf23a4b()	Unknown
 	python34.dll!6bf23a6d()	Unknown
 	python34.dll!6bf240c7()	Unknown
 	python34.dll!6bf2487a()	Unknown
 	python34.dll!6bf248ee()	Unknown
 	OpenLP.exe!0040253b()	Unknown

-- 
You received this bug notification because you are a member of OpenLP
Core, which is subscribed to OpenLP.
https://bugs.launchpad.net/bugs/1647099

Title:
  Closing OpenLP triggers crash in Windows builds on 2.4 >

Status in OpenLP:
  New

Bug description:
  When OpenLP is closed, Windows pops up the program crash dialogue
  twice.

  “OpenLP.exe has stopped working
  A problem caused the program to stop working correctly.
  Please close the program.”

  This happens in 2.4 builds but not in 2.2 series.

To manage notifications about this bug go to:
https://bugs.launchpad.net/openlp/+bug/1647099/+subscriptions