From: | Andreas Pflug <Andreas(dot)Pflug(at)web(dot)de> |
---|---|
To: | efesar <efesar(at)nmia(dot)com>, pgadmin-hackers(at)postgresql(dot)org |
Subject: | Re: PGA3 Memory Leaks |
Date: | 2003-04-16 21:07:06 |
Message-ID: | 3E9DC5FA.8030506@web.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
efesar wrote:
>Andreas,
>
>The wxWindows documentation specifically states those objects must be
>deleted.
>
>The one line I didn't uncomment was "delete statistics." Since statistics is
>a wxListCtrl, it probably doesn't need to be deleted. That's why I left it
>commented. Please test and document. It's possible your crash was caused by
>that.
>
>In the meantime, I think the change should stay. IMHO, memory leaks are not
>wastes of time.
>
>Dave -- Opinion? I'll leave this one up to you, it that's okay.
>
>
>
Keith,
I had the crash on delete statistics. If you like to trace that on-exit
leaks, I don't mind as long as they don't cause double deletion as in
the case of statistics.
Don't get me wrong, I appreciate that we have somebody who's eager to
locate memory leaks, these things happen when producing code and should
be eliminated. It's just a difference whether that orphaned memory is a
db connection created all over and over again, or some bytes that get
dumped by the os anyway.
Regards,
Andreas
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Page | 2003-04-17 07:11:05 | Re: PGA3 Memory Leaks |
Previous Message | efesar | 2003-04-16 19:42:20 | Re: PGA3 Memory Leaks |