[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 282933] closing session crash
From:       Daniel Eklöf <daniel () ekloef ! se>
Date:       2011-11-03 21:06:00
Message-ID: E1RM4U4-0000Sf-VZ () bugs ! kde ! org
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=282933





--- Comment #18 from Daniel Eklöf <daniel ekloef se>  2011-11-03 21:06:00 ---
(In reply to comment #17)
> a) differend optimization modes for KWin/Qt (anyone -o3?)

No, my cxxflags are:
-O2 -march=native -ftracer -maccumulate-outgoing-args -pipe
-fexcess-precision=fast

I do use a newer gcc version (4.6.2) than I did when I compiled KDE 4.7.2
(4.6.1) though.

> b) Daniel only encounters it on session ends, what could suggest a general
> memory corruption

Well, it crashes less frequently after the patch, so it might be that it's
possible to trigger it with kquitapp too, just that I haven't tried enough.
But, I don't think so. I've tried many more kquitapps than logouts, and it
never crashes with kquitapp so far, but a couple of times when logging out.

> However, Daniel's new trace ends up incredibly high in the stack as well, where
> the first one was near the heap (@Daniel: are the numbers for
> KWin::Deleted::create always that large now?)

You're right, the pointers do look weird. Not sure if they always do; I haven't
paid attention to that. I'll do that from now on.

> @Daniel:
> can you try swapping the release loops for CLients and Unmanaged in
> workspace.cpp ~ line 540? (It will likely still crash, but the question is
> "where")

I'll do that tomorrow.

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.=
[prev in list] [next in list] [prev in thread] [next in thread]