[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-frameworks-devel
Subject:    Re: QString -> QStringLiteral conversions might make applications crash on exit
From:       Frank Reininghaus <frank78ac () googlemail ! com>
Date:       2016-02-28 22:14:37
Message-ID: CAFoZWWh-GpjLfMFvyGGiPC=3zAP0SJMe-Dho=dM86d4e1FUvQg () mail ! gmail ! com
[Download RAW message or body]

Hi,

2016-02-26 13:25 GMT+01:00 Jan Kundrát:
> On Friday, 26 February 2016 01:37:57 CET, Frank Reininghaus wrote:
>>
>> This becomes a problem if the read-only data that the QString refers
>> to are not there any more, which can happen if the QString was stored
>> in a global static object from one library, and the QStringLiteral is
>> from another library, which might have been unloaded before the global
>> static object was destroyed.
>
>
> Are you 100% sure that this is not "just" due to icon loaders which are
> implemented as plugins [1]?

No, I'm not sure.

> Upstream says [2] that they do not want to support unloading of plugins
> which "leak" Qt data. There's a patch [3] which implements this for all
> plugins (including the icon loaders). Apparently, it's been so ever since Qt
> 5.0.

Thanks for sharing these links!

> For an example on how an application can workaround this thing, see my patch
> to Trojitá [4].

This is indeed an interesing approach to work around the problem,
thanks! Maybe a similar thing could be done in KIconLoader.

Cheers,
Frank
_______________________________________________
Kde-frameworks-devel mailing list
Kde-frameworks-devel@kde.org
https://mail.kde.org/mailman/listinfo/kde-frameworks-devel

[prev in list] [next in list] [prev in thread] [next in thread]