[Qgis-developer] Possible memory leak in rendering code
a.neumann at carto.net
Tue Apr 23 02:05:50 PDT 2013
How comes that the same feature works fine for some but is broken for
When I have it on (using a combination of Postgis, WMS and GeoTiff) I
often have redraw issues and the layer toggeling often fails. Layers are
not drawn, but appear to be on with the checkbox in the layer tree or
vice versa. I think the main problem is when also using WMS sources.
Really strange ...
Am 23.04.2013 10:49, schrieb Nathan Woodrow:
> I'm the opposite. I have it enabled all the time and don't really have any
> issues with it.
> It's not doing any harm leaving it in IMO so -1 to remove it.
> - Nathan
> On Tue, Apr 23, 2013 at 6:38 PM, Andreas Neumann <a.neumann at carto.net>wrote:
>> I am surprised that people really used the render caching. I had all sorts
>> of issues so I did not use it. To me it was really broken. I think we
>> should remove it and reintroduce it when multithreading is implemented and
>> the feature works as expected. Better not ship it than ship in a broken
>> Anita Graser <anitagraser at gmx.at> schrieb:
>>> On Tue, Apr 23, 2013 at 8:22 AM, Matthias Kuhn <matthias.kuhn at gmx.ch>wrote:
>>>> This has some limitations like you are not able to
>>>> incrementally draw features and you are not able to cancel rendering
>>> I would be very sorry to see this feature go. I use it regularly since I
>>> often work with huge datasets. E.g. loading the street network of a whole
>>> country from PostGIS, I would have to wait for ages without the possibility
>>> to cancel rendering.
>>> Best wishes,
>>> Qgis-developer mailing list
>>> Qgis-developer at lists.osgeo.org
>> Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail
>> Qgis-developer mailing list
>> Qgis-developer at lists.osgeo.org
More information about the Qgis-developer