[pgrouting-dev] SSL SYSCALL error: EOF detected

[Stephen Woodbridge]

Hi Luis,

I looked at the valgrind log and it is basically the same as a single 
query and I do not see any leaks coming from pgrouting.

I think you should start looking at how you are using python.
https://www.google.com/?gws_rd=ssl#newwindow=1&q=psycopg2+memory+leak

Also, looking at your code, you are computing random start and end 
node_ids for the query:

1) are you sure you have all nodes from 1 to max+1?
2) it is possible that if a query errors out that we might leak memory 
and if this is the case you should attach a simple test case and 
valgrind log to a bug report.

Also, in your python you are using fetchall() but you are never freeing 
the results.

Anyway, at this point I do not see a problem with pgrouting and I'm not 
seeing this issue on any of my 12.04 systems.

Thanks,
   -Steve

On 2/26/2015 4:14 AM, Luís de Sousa wrote:
> Hi again Steve, a few more points:
>
> 1. I am using pgRouting 2.0.0 on Ubuntu 12.04 server, with all the
> software installed from the repositories. I am attaching a log file
> with details.
>
> 2. Valgrind produces exactly the same output for pgr_trsp(). I am
> attaching a log from five successive calls to this function.
>
> 3. Also attached is a small python script that replicates the issue.
> Rough numbers, RAM usage in the Postgres server swells by about 160 Mb
> per 10 000 queries. Just give it a go and let it run for a while.
>
> Thank you and regards,
>
> Luís
>
> On 25 February 2015 at 17:01, Stephen Woodbridge
> <woodbri at swoodbridge.com> wrote:
>> On 2/25/2015 10:18 AM, Luís de Sousa wrote:
>>>
>>> Hi Steve,
>>>
>>> I am sorry if I did not make this clear before: PyWPS is running on a
>>> different server. Postgres and pgRouting run on a dedicated server; it
>>> is always a postgres process taking up the RAM.
>>
>>
>> You may have and I may have forgotten :)
>>
>> Anyway, try using pgr_trsp() and see if it happen with that.
>>
>> Tell me about the postgresql server:
>>
>> What OS/Distribution?
>> Are you using pgrouting installed from a package or compiled from source?
>>
>> select * from pgr_version();
>> "2.0.0";"pgrouting-2.0.0";"78";"abde224";"develop";"1.46.1"
>>
>> My version is built from source and the "develop" branch using Boost v1.46.1
>> with 78 commits ahead of master.
>>
>> Since pgr_trsp uses different code from pgr_dijkstra I would not expect to
>> see the same behavior.
>>
>> -Steve
>>
>>
>>
>>
>> _______________________________________________
>> pgrouting-dev mailing list
>> pgrouting-dev at lists.osgeo.org
>> http://lists.osgeo.org/mailman/listinfo/pgrouting-dev