| Summary: | segfault on exiting cube effect | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | Pedro Martin <pedromartinster> |
| Component: | effects-window-management | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | charles.v.wright, evgom.sid, god |
| Priority: | NOR | Flags: | thomas.luebking:
ReviewRequest+
|
| Version: | 4.9.0 | ||
| Target Milestone: | 4.9.1 | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | http://commits.kde.org/kde-workspace/eb7a37936ea48eabb74a002001204485dbac0eff | Version Fixed In: | 4.9.1 |
| Sentry Crash Report: | |||
| Attachments: |
New crash information added by DrKonqi
kwin crash handler kwinrc kwinrc in txt format New crash information added by DrKonqi New crash information added by DrKonqi |
||
|
Description
Pedro Martin
2012-07-31 15:30:50 UTC
The backtrace says it crashes in "effects->addRepaintFull();"
-> Does it always look _exactly_ the same (despite memory offsets like "0xf7a780")
What does this mean:
> but when I pushed "intro"
clicking or pressing ctrl+F11 again, etc.. ?
I mean click enter to back to desktop. Sorry for bad english. Brgds No need to excuse for struggles with a foreign language and thanks for the info, but what is far more important is whether all (you said "can be reproduced every time") look exactly the same (for that's actually hardly possible - this crash implies a dangeling effects pointer) Yes, all looks exactly the same, if I close segmentation fault message, I see all exactly as before crash, effects work, and you can do Ctrl+F11 again, and when I push enter in the keyboard to close cube, it closes and appears again seg-fault message on desktop. Brgds I meant whether the texts in the "developer information" tab look all exactly the same (in doubt post one or two) Texts in developer information are exactly the same, every time I reproduce crash. I created a new user and from this new user there are no crashes, it works perfectly. Maybe some old KDE48 configuration is disturbing. Not necessary to create a new user, simply setting cube configuration in systemsettings/Desktop-effects as default, apply, and after this works without issues. You can configure again cube effects after that with no issues. Thanks & Brgds this seems like we have one option which crashes. You could try to change everything again in a way so that it crashes? That is restore your previous configuration. <dev-note>We should add Q_PROPERTIES to all effects and query them in support- information. /me will work on this for 4.9.1</dev-note> Created attachment 72908 [details]
New crash information added by DrKonqi
kwin (4.9.00) on KDE Platform 4.9.00 using Qt 4.8.1
- What I was doing when the application crashed:alt>F10 for the cube ....spinn cube with the mouse a few times.........hit enter to return to desktop.
crash Reporter comes up but all looks well.
if top is running you can see it ? stutter wile the cube is up .....same with alt>tab cover flow but no crash yet
-- Backtrace (Reduced):
#6 KWin::CubeEffect::postPaintScreen (this=0x1b21d00) at ../../../kwin/effects/cube/cube.cpp:1172
#7 0x00007f2b98602528 in KWin::EffectsHandlerImpl::postPaintScreen (this=0x1964400) at ../../kwin/effects.cpp:250
#8 0x00007f2b98602528 in KWin::EffectsHandlerImpl::postPaintScreen (this=0x1964400) at ../../kwin/effects.cpp:250
#9 0x00007f2b985e2e70 in KWin::Scene::paintScreen (this=0x1244a00, mask=<optimized out>, region=0x7fff8a6e94e0) at ../../kwin/scene.cpp:150
#10 0x00007f2b985f8fae in KWin::SceneOpenGL::paint (this=0x1244a00, damage=..., toplevels=...) at ../../kwin/scene_opengl_glx.cpp:481
Does this crash happen *before* the cube returned to a "normal" desktop view or *after*? reply to comment #10 after reterning to normal view ......the screen will flicker once and then the crash reporter pops up VINNY Created attachment 72925 [details]
kwin crash handler
After modifyng desktop-effects/cube to default, apply and after configuring again cube effect,
if :
actualize KDE software (yast) or restarting desktop (ctl+del) or going to terminal (ctrl+F1) and frm here init 5, after those events when I hit Ctl +f11 and after hit enter or any key crash handler popup appears.
I try to send the new text from crash.
Brgds
can you please attach your ~/.kde/share/config/kwinrc ? Created attachment 72929 [details]
kwinrc
Created attachment 72930 [details]
kwinrc in txt format
Sorry for that , i resend my kwin.rc in plain text.
thanks & best regards
Thanks alot. Bug / crash is absolutely reproducible here. Now let's see why ;-) There's either an offset in my or your sources. However the crash is due to "desktopNameFrame->free();" and it's because you don't show the desktop name (thus desktopNameFrame is NULL - makes MUCH more sense and can be fixed ;-) https://git.reviewboard.kde.org/r/105840/ conferming comment#17 if I add the desktop name back to the cube settings no more crash :) VINNY Thanks to you both, and to all KDE team, you do a fantastic work. Best regards Pedro Martín Created attachment 72957 [details]
New crash information added by DrKonqi
kwin (4.9.00) on KDE Platform 4.9.00 using Qt 4.8.2
- What I was doing when the application crashed:
I've experienced same crash as OP explained.
Distro: Gentoo amd64
-- Backtrace (Reduced):
#6 0x00007f29aba066c4 in KWin::CubeEffect::postPaintScreen() () from /usr/lib64/kde4/kwin4_effect_builtins.so
#7 0x00007f29b92238a8 in KWin::EffectsHandlerImpl::postPaintScreen() () from /usr/lib64/libkdeinit4_kwin.so
#8 0x00007f29b92238a8 in KWin::EffectsHandlerImpl::postPaintScreen() () from /usr/lib64/libkdeinit4_kwin.so
#9 0x00007f29b9201f4e in KWin::Scene::paintScreen(int*, QRegion*) () from /usr/lib64/libkdeinit4_kwin.so
#10 0x00007f29b9219d36 in KWin::SceneOpenGL::paint(QRegion, QList<KWin::Toplevel*>) () from /usr/lib64/libkdeinit4_kwin.so
Created attachment 73081 [details]
New crash information added by DrKonqi
kwin (4.9.00 "release 558") on KDE Platform 4.9.00 "release 558" using Qt 4.8.2
- What I was doing when the application crashed:
i have openSUSE 12.1 64 bits with KDE 4.9.
Always happen when desktop cube (ctrl+f11) are activated.
-- Backtrace (Reduced):
#6 KWin::CubeEffect::postPaintScreen (this=0x2582920) at /usr/src/debug/kde-workspace-4.9.0/kwin/effects/cube/cube.cpp:1172
#7 0x00007f2ce8618ed8 in KWin::EffectsHandlerImpl::postPaintScreen (this=0x2195120) at /usr/src/debug/kde-workspace-4.9.0/kwin/effects.cpp:250
#8 0x00007f2ce85f90ee in KWin::Scene::paintScreen (this=0x215c3d0, mask=<optimized out>, region=0x7ffff0501ae0) at /usr/src/debug/kde-workspace-4.9.0/kwin/scene.cpp:150
#9 0x00007f2ce860f9ce in KWin::SceneOpenGL::paint (this=0x215c3d0, damage=..., toplevels=<optimized out>) at /usr/src/debug/kde-workspace-4.9.0/kwin/scene_opengl_glx.cpp:481
#10 0x00007f2ce85f2482 in performCompositing (this=0x20ecb90) at /usr/src/debug/kde-workspace-4.9.0/kwin/composite.cpp:432
Git commit eb7a37936ea48eabb74a002001204485dbac0eff by Thomas Lübking. Committed on 08/08/2012 at 19:48. Pushed by luebking into branch 'KDE/4.9'. check desktopNameFrame pointer in cube effect REVIEW: 105840 FIXED-IN: 4.9.1 M +2 -1 kwin/effects/cube/cube.cpp http://commits.kde.org/kde-workspace/eb7a37936ea48eabb74a002001204485dbac0eff |