ok should be fixed in 857678. Cheers, Benoit
PS. Now using intel graphics (yes i got one of these sony sz2 with dual intel/nvidia), no rendering glitches. 2008/9/6 Benoit Jacob <[EMAIL PROTECTED]>: > aaah got it :) > > when changing a setting, init() was called, reallocating the QImage > that was being painted in paralled by the renderer threads... > > solution was to add a renderThreads[0]->wait() in > Mandelbrot::init()... indeed the 0-th thread is the master-thread, it > controls the others if any. > > Cheers, > Benoit > > 2008/9/6 Benoit Jacob <[EMAIL PROTECTED]>: >> Indeed, i can reproduce that. >> >> How do I get a backtrace? The kcrash dialog just disappears when i ask >> for the backtrace, and when i run plasma in gdb, after the crash it >> just says "no stack". >> >> 2008/9/6 Aaron J. Seigo <[EMAIL PROTECTED]>: >>> On Friday 05 September 2008, Benoit Jacob wrote: >>>> I updated to 177.70. With desktop effects enabled, the glitches are as >>>> bad as before. With desktop effects disabled, the situation has >>>> improved but there remain some glitches. >>> >>> not related, but i just discovered that changing the settings while the >>> fractal is still rendering on the desktop results in a crash in a thread in >>> the renderer.. >>> >>> -- >>> Aaron J. Seigo >>> humru othro a kohnu se >>> GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43 >>> >>> KDE core developer sponsored by Trolltech >>> >>> >>> _______________________________________________ >>> Plasma-devel mailing list >>> Plasma-devel@kde.org >>> https://mail.kde.org/mailman/listinfo/plasma-devel >>> >>> >> > _______________________________________________ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
