openlp-core team mailing list archive

[Karan <799990@xxxxxxxxxxxxxxxxxx>]

I've had another look at the call stack and I may have found the cause of the Qt problem: qgenericbearer4.dll is not part of the OpenLP build and therefore loaded from "C:\Qt\4.7.1\plugins\bearer\" (my Visual Studio 2010 build).
I don't really understand how, since it's not actually in the PATH, but the call stack shows that QtCore4.dll uses msvcr90.dll (and is therefore likely to be the one from the OpenLP folder) and only qgenericbearer4.dll calls into msvcr100.dll. Here's the full stack: http://pastebin.com/4csYfRc8

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

Title:
  Crash on startup because wrong Qt libs are loaded (Win 7)

Status in OpenLP - Worship Presentation Software:
  New

Bug description:
  When I first started OpenLP it crashed while the splash screen was shown - access violation in msvcr100.dll (-> Visual Studio 2010 runtime library) with some Qt DLLs above it in the callstack (according to the then attached debugger). OpenLP apparently loaded the Qt DLLs from the PATH instead of using the local ones - I've got Qt 4.7.1 built with Visual Studio 2010 in the PATH. Since the other DLLs in the OpenLP folder are linked against msvcr90.dll and runtimes can't usually be mixed this seems to be the source of the problem...
  Removing my Qt build from the PATH helps, but it would be better if OpenLP simply used the libraries installed with it.

  Using OpenLP 1.9.5 on Win 7 Professionell 32-bit

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