Re: PgAdmin III 1.12 crazy memory usage - Mailing list pgadmin-support

From Thom Brown
Subject Re: PgAdmin III 1.12 crazy memory usage
Date
Msg-id AANLkTi=7qF0mW=mWvcqB+-KG1mQUcr6rOD7UCtPxk+br@mail.gmail.com
Whole thread Raw
In response to Re: PgAdmin III 1.12 crazy memory usage  (Thom Brown <thom@linux.com>)
Responses Re: PgAdmin III 1.12 crazy memory usage  (Dave Page <dpage@pgadmin.org>)
List pgadmin-support
On 1 October 2010 14:21, Thom Brown <thom@linux.com> wrote:
> On 1 October 2010 14:12, Dave Page <dpage@pgadmin.org> wrote:
>> On Fri, Oct 1, 2010 at 2:00 PM, Thom Brown <thom@linux.com> wrote:
>>> I can't recreate this, so it may not be much help, but I left PgAdmin
>>> running with no query windows open at all, and eventually I noticed my
>>> PC slowing right down as memory started to swap.  I've attached a
>>> screenshot to show its memory usage.
>>
>> VM size of a gig? Thats small for Windows isn't it? :-p
>>
>>> Actions I had performed earlier are attempting to select all rows from
>>> a massive table, and closed that result window a few seconds into it
>>> attempting to fetch results.
>>
>> That's where my suspicions lie. Can you try to reproduce it by doing that again?
>
> No, I've attempted that with several large tables, but it doesn't make
> any noticeable difference.  Where it's actually started fetching
> results and displaying them, closing the window causes pgAdmin to
> correctly returns the memory.  I've also checked what's happening
> server-side when closing the window, and the query is cancelled.  Is
> it theorically possible for pgAdmin to fail to cancel the query when
> closing the results window?
>
> Note: Whenever I say results window, I actually mean the view/edit data window.

Got this in the logs if it's relevant at all.  Note that
bookingbaskets is the massive table:

2010-10-01 13:37:09 BST    STATEMENT    SELECT * FROM public.bookingbaskets             ORDER BY bookingbasketid ASC

2010-10-01 13:37:11 BST    LOG    could not receive data from client: No
connection could be made because the target machine actively refused
it.
2010-10-01 13:37:12 BST    LOG    unexpected EOF on client connection
2010-10-01 13:37:11 BST    LOG    could not receive data from client: No
connection could be made because the target machine actively refused
it.
2010-10-01 13:37:13 BST    LOG    unexpected EOF on client connection
2010-10-01 13:37:11 BST    LOG    could not receive data from client: No
connection could be made because the target machine actively refused
it.
2010-10-01 13:37:13 BST    LOG    unexpected EOF on client connection
2010-10-01 13:37:12 BST    LOG    could not receive data from client: No
connection could be made because the target machine actively refused
it.
2010-10-01 13:37:13 BST    LOG    unexpected EOF on client connection
2010-10-01 13:37:12 BST    LOG    could not receive data from client: No
connection could be made because the target machine actively refused
it.
2010-10-01 13:37:13 BST    LOG    unexpected EOF on client connection
2010-10-01 13:37:12 BST    LOG    could not receive data from client: No
connection could be made because the target machine actively refused
it.
2010-10-01 13:37:13 BST    LOG    unexpected EOF on client connection
2010-10-01 13:37:12 BST    LOG    could not receive data from client: No
connection could be made because the target machine actively refused
it.

This was just before I noticed the massive memory usage.  I took the
screenshot at 13:42.

--
Thom Brown
Twitter: @darkixion
IRC (freenode): dark_ixion
Registered Linux user: #516935


pgadmin-support by date:

Previous
From: Thom Brown
Date:
Subject: Re: PgAdmin III 1.12 crazy memory usage
Next
From: "Diego Garcilazo"
Date:
Subject: SQL pane error