Hello Dick,
There are only three things that come to mind:
1.) Is there a reason you are not using wxPython 2.6?
2.) I've noticed that a lot of developers retain a lot of information when using a database for a backend. If every query result is stored in memory and kept there (even partially) it can really cause havoc with memory limits. Try simulating the database part of your code and see if the memory problem still occurs.
3.) PostgreSQL databases need to be vacuumed every so often. Make sure it is happening!
Steve
Dick Kniep wrote:
···
Hi list,
We have developed a big application (approximately 55 KLines) with a Postgres database on wxPython 2.4.2.4.
When a user logs on it uses approximately 60 MB, 21 MB shared memory. After a while memory use shoots up to 250 MB + Off course this is unacceptable. Has anyone on the list any experience with this size of application, and is there anyone who can advise me on the way to find out where the memory is lost?
As the application has grown over time, programming has been sloppy to start with, but the loss of memory is so big, I can hardly understand how that can happen.
Cheers,
Dick Kniep