[Kst] : Huge performance problem under Windows

Peter Kümmel syntheticpp at gmx.net
Thu Nov 19 15:29:29 CET 2009

Barth Netterfield wrote:
> 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

Could someone give me the big picture what ObjectStore is good for?
It's all over the place and often reason for the crashs on exit.


More information about the Kst mailing list