The plugin can cause an abort if the application uses a QCoreApplication about qtpbfimageplugin HOT 3 CLOSED

This is a bug of mythpreviewgen, not QtPBFImagePlugin as any application using stuff from the Qt GUI API (QImage is part of the GUI module) is required to use at least QGuiApplication (or QApplication).

Apart from being stated in the documentation it was also affirmed in the Qt mailing list recently.

from qtpbfimageplugin.

A quick follow up for anyone who should come across this problem in the future.

If the option is open to you the easiest and undoubtedly the proper fix is to just use QGuiApplication in your application.

If you can't do that you are stuffed the only fix is to un-install this plugin and the problem will go away.

My personal view is a 3rd party Qt plugin should not be knowingly crashing applications, even if they are not following the guide lines, sometimes programmers do bend the rules slightly :)

There is a simple 3 line patch that will allow the plugin to fail gracefully rather than throwing an abort and crashing the application which in my view is a more friendly thing to do but sadly that is not a view held by tunic0 :( .

from qtpbfimageplugin.

It is not the plugin that is "crashing" (it's not even a crash) the application but an assert in Qt that detects someone is using the GUI API without a proper GUI module initialisation (using the QGuiApplication instance). Qt has however such asserts not on all GUI API use cases so QtPBFImagePlugin may be the first or even the only code that will trigger the assert.

All this means, that when your application is broken and uses the wrong base class, ANY Qt plugin or even Qt itself may trigger such assert at ANY time. So the solution is really not to request every Qt plugin or Qt self to include code like:

if (used_from_a_broken_app_like_mythpreviewgen)
    do_nothing_and_return_NULL

in front of every GUI API call (or at least in the initialisation in case of a module). The only solution is to fix your code, since otherwise you do not know who and when will trigger such an assert the next time (It may be another plugin or even a new Qt version).

from qtpbfimageplugin.