diff options
| author | Thiago Macieira <thiago.macieira@intel.com> | 2015-11-12 10:14:51 -0800 |
|---|---|---|
| committer | Thiago Macieira <thiago.macieira@intel.com> | 2016-05-03 17:54:22 +0000 |
| commit | 494376f980e96339b6f1eff7c41336ca4d853065 (patch) | |
| tree | 0d04a7d8b7351beb5e08bcbc4d52a3e0963dbacf /tests/auto/testlib/selftests/expected_crashes_1.txt | |
| parent | 69c2a606b36858454ec0b53b5d9789cf8e524806 (diff) | |
Stop unloading plugins in QPluginLoader and QFactoryLoader
QPluginLoader hasn't unloaded in its destructor since Qt 5.0, but we
missed the equivalent code in QFactoryLoader (which bypasses
QPluginLoader). Besides, QPluginLoader::unload() was still doing
unloading, which it won't anymore.
Not unloading plugins is Qt's policy, as decided during the 5.0
development process and reaffirmed now in 5.6. This is due to static
data in plugins leaking out and remaining in use past the unloading of
the plugin, causing crashes.
This does not affect QLibrary and QLibrary::unload(). Those are meant
for non-Qt loadable modules, so unloading them may be safe.
Task-number: QTBUG-49061
Discussed-on: http://lists.qt-project.org/pipermail/development/2015-November/023681.html
Change-Id: I461e9fc7199748faa187ffff1416070f138df8db
Reviewed-by: Simon Hausmann <simon.hausmann@theqtcompany.com>
Reviewed-by: Lars Knoll <lars.knoll@theqtcompany.com>
Diffstat (limited to 'tests/auto/testlib/selftests/expected_crashes_1.txt')
0 files changed, 0 insertions, 0 deletions