Hi Nyall,
I have seen you have just backported the commits into release-2_14. Thanks
a lot !
Michaël
2016-05-14 14:57 GMT+02:00 kimaidou :
> Ok, thanks a lot !
>
> 2016-05-14 12:41 GMT+02:00 Nyall Dawson :
>
>>
>> On 14 May 2016 19:39, "kimaidou"
Ok, thanks a lot !
2016-05-14 12:41 GMT+02:00 Nyall Dawson :
>
> On 14 May 2016 19:39, "kimaidou" wrote:
> >
> > Hi Nyall,
> >
> > I have just tested it with today's master, and there is no memory leak
> any more. Thanks a lot for helping solving this
On 14 May 2016 19:39, "kimaidou" wrote:
>
> Hi Nyall,
>
> I have just tested it with today's master, and there is no memory leak
any more. Thanks a lot for helping solving this nasty one.
> Could you please backport the related "memory leak" commits to the 2.14
release branch
Thanks Nyall,
I will build last master and check it asap.
Cheers,
Michaël
2016-05-10 6:25 GMT+02:00 Nyall Dawson :
> On 10 May 2016 at 03:38, kimaidou wrote:
> > Hi
> >
> > I just tested with a freshly built QGIS release-2_14 , and the issue
> >
On 10 May 2016 at 03:38, kimaidou wrote:
> Hi
>
> I just tested with a freshly built QGIS release-2_14 , and the issue
> remains.
> The easiest way to reproduce is to zoom back and forth from big scales ( ~
> 1:25 000 ) to layer extent scale ( ~ 1:600 000 )
Should be fixed by
Hi
I just tested with a freshly built QGIS release-2_14 , and the issue
remains.
The easiest way to reproduce is to zoom back and forth from big scales ( ~
1:25 000 ) to layer extent scale ( ~ 1:600 000 )
Good evening/morning
Michaël
2016-05-09 15:02 GMT+02:00 kimaidou :
>
Hi Matthias,
Not yet, I need to build QGIS master before being able to report back
Thanks for your answer
2016-05-09 14:59 GMT+02:00 Matthias Kuhn :
> Have you tested with either the latest 2.14 nightly or master nightly?
> An issue with OGR connection pooling has been
Have you tested with either the latest 2.14 nightly or master nightly?
An issue with OGR connection pooling has been resolved recently. And I
wonder if that could be related.
-- Matthias
On 05/09/2016 02:28 PM, kimaidou wrote:
> I created an issue about it : http://hub.qgis.org/issues/14792
>
>
I created an issue about it : http://hub.qgis.org/issues/14792
2016-05-09 11:48 GMT+02:00 kimaidou :
> Hi again,
>
> I also forgot to mention that I have no memory leak when using the same
> dataset in PostGIS ( tested by importing the Shapefile in PostGIS with
> shape2pgsql
Hi again,
I also forgot to mention that I have no memory leak when using the same
dataset in PostGIS ( tested by importing the Shapefile in PostGIS with
shape2pgsql )
Michaël
2016-05-09 11:07 GMT+02:00 kimaidou :
> I forgot to mention the steps to reproduce the bug, and the
I forgot to mention the steps to reproduce the bug, and the precautions to
take :
* open the project in QGIS 2.14 ( I have not tested with older versions)
* open a terminal and use this kind of command to monitor QGIS memory
consumption : htop, or ps with
watch -n1 'ps -aux --sort -pmem | head
Hi devs,
I have just found a memory leak in QGIS Desktop (and server) with the
project available in [1] ( a 20Mo tar.bz2 )
This is a very simple project with only one buildings Shapefile ( SHP
68Mo). This layer has been exported from PostGIS from a query wich aimed to
simplify the building for
12 matches
Mail list logo