[Kst] : Huge performance problem under Windows
Barth Netterfield
netterfield at astro.utoronto.ca
Tue Nov 17 16:29:53 CET 2009
On Tuesday 17 November 2009 05:44:49 am Peter Kümmel wrote:
> I now can reproduce the increasing memory usage while resizing the window,
> but the leak information is too noisy because kst doesn't cleanup on exit.
>
> It seems the memory handling is very wired: statics, singeltons, refcounted
> pointers, pointers shared between threads, containers with shared pointers,
> and so on.
Indeed.
> ATM you can't cleanup because the kst will crash:
>
> Application::~Application() {
> // lets not clean up before we leave....
> // if we do, we'll end up crashing on exit
> // unless we fix some stuff related to destruction
> // in a multi-threaded situation.
> //delete _mainWindow;
> //delete _dialogDefaults;
It only crashes on exit sometimes. If you un-comment these lines, you will
vastly decrease the valgrind memcheck noise, and only maybe crash on exit.
> Is it planned to redesign this stuff (e.g. using new Qt4 templates)?
Boh?
cbn
More information about the Kst
mailing list