Bug 322796 - Java menu problems
Summary: Java menu problems
Status: RESOLVED NOT A BUG
Alias: None
Product: kwin
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: Debian stable Linux
: NOR crash
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-07-25 00:14 UTC by Alex Austin
Modified: 2013-07-25 04:28 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alex Austin 2013-07-25 00:14:50 UTC
Application: kwin (4.8.4 (4.8.4))
KDE Platform Version: 4.8.4 (4.8.4)
Qt Version: 4.8.2
Operating System: Linux 3.2.0-4-amd64 x86_64
Distribution: Debian GNU/Linux 7.0 (wheezy)

-- Information about the crash:
- What I was doing when the application crashed:

Installed Java is "IcedTea-Web Plugin (using IcedTea-Web 1.3.2 (1.3.2-1))" according to about:plugins.
Graphics driver in use is Intel on a Core i7-2600.
	$ dpkg-query -s xserver-xorg-video-intel
	Package: xserver-xorg-video-intel
	...
	Architecture: amd64
	Version: 2:2.19.0-6
	Provides: xorg-driver-video
	...
	Description: X.Org X server -- Intel i8xx, i9xx display driver
	 ...
	 This package is built from the X.org xf86-video-intel driver module.


I opened http://www.falstad.com/circuit/ in Google Chrome. When I opened the "Circuits" menu to go to Blank Circuit, the entire display (two monitors) froze except for the mouse cursor. Killing the Java process did not unfreeze the display. Killing kwin did.

-- Backtrace:
Application: KWin (kwin), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7ff8c016d780 (LWP 5422))]

Thread 3 (Thread 0x7ff89e7db700 (LWP 5457)):
#0  __lll_lock_wait_private () at ../nptl/sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:97
#1  0x00007ff8bfac36b8 in _L_lock_9627 () from /lib/x86_64-linux-gnu/libc.so.6
#2  0x00007ff8bfac1aa1 in *__GI___libc_free (mem=0x7ff8bfdcbe60) at malloc.c:3736
#3  0x00007ff8bb1e5e21 in QThreadPrivate::finish (arg=arg@entry=0x7ff8bb638500) at thread/qthread_unix.cpp:339
#4  0x00007ff8bb1e6d13 in ~__pthread_cleanup_class (this=<synthetic pointer>, __in_chrg=<optimized out>) at /usr/include/pthread.h:545
#5  QThreadPrivate::start (arg=0x7ff8bb638500) at thread/qthread_unix.cpp:309
#6  0x00007ff8b477eb50 in start_thread (arg=<optimized out>) at pthread_create.c:304
#7  0x00007ff8bfb20a7d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#8  0x0000000000000000 in ?? ()

Thread 2 (Thread 0x7ff897ab4700 (LWP 5537)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162
#1  0x00007ff8bc5d8e77 in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4
#2  0x00007ff8bc5d8ea9 in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4
#3  0x00007ff8b477eb50 in start_thread (arg=<optimized out>) at pthread_create.c:304
#4  0x00007ff8bfb20a7d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#5  0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7ff8c016d780 (LWP 5422)):
[KCrash Handler]
#6  0x00007ff8bfa78475 in *__GI_raise (sig=<optimized out>) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#7  0x00007ff8bfa7b6f0 in *__GI_abort () at abort.c:92
#8  0x00007ff8bfab352b in __libc_message (do_abort=<optimized out>, fmt=<optimized out>) at ../sysdeps/unix/sysv/linux/libc_fatal.c:189
#9  0x00007ff8bfabcd76 in malloc_printerr (action=3, str=0x7ff8bfb91bc9 "invalid fastbin entry (free)", ptr=<optimized out>) at malloc.c:6283
#10 0x00007ff8bfac1aac in *__GI___libc_free (mem=<optimized out>) at malloc.c:3738
#11 0x00007ff8bfe2fce9 in ~QByteArray (this=0x7fffa8f9fd70, __in_chrg=<optimized out>) at /usr/include/qt4/QtCore/qbytearray.h:401
#12 KWin::Application::crashHandler (signal=<optimized out>) at ../../kwin/main.cpp:383
#13 0x00007ff8bf680818 in KCrash::defaultCrashHandler (sig=11) at ../../kdeui/util/kcrash.cpp:307
#14 <signal handler called>
#15 0x0000000000000000 in ?? ()
#16 0x00007ff8bfe9632a in KWin::Deleted::copyToDeleted (this=this@entry=0x202cb80, c=c@entry=0x25e0a00) at ../../kwin/deleted.cpp:78
#17 0x00007ff8bfe9658d in KWin::Deleted::create (c=0x25e0a00) at ../../kwin/deleted.cpp:53
#18 0x00007ff8bfe7a900 in KWin::Unmanaged::release (this=0x25e0a00) at ../../kwin/unmanaged.cpp:85
#19 0x00007ff8bfe18fcd in KWin::Workspace::~Workspace (this=0x1a91960, __in_chrg=<optimized out>) at ../../kwin/workspace.cpp:533
#20 0x00007ff8bfe196a9 in KWin::Workspace::~Workspace (this=0x1a91960, __in_chrg=<optimized out>) at ../../kwin/workspace.cpp:563
#21 0x00007ff8bfe2fb75 in KWin::Application::~Application (this=0x7fffa8fa0c70, __in_chrg=<optimized out>) at ../../kwin/main.cpp:340
#22 0x00007ff8bfe3229f in kdemain (argc=3, argv=0x7fffa8fa0df8) at ../../kwin/main.cpp:541
#23 0x00007ff8bfa64ead in __libc_start_main (main=<optimized out>, argc=<optimized out>, ubp_av=<optimized out>, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fffa8fa0de8) at libc-start.c:228
#24 0x0000000000400771 in _start ()

Possible duplicates by query: bug 302768.

Reported using DrKonqi
Comment 1 Thomas Lübking 2013-07-25 03:17:03 UTC
The backtrace is from a crash-on-exit, bug #282933
This means kwin was terminated (kill [-15], not -9) what means kwin was still processing events what means:
a) the backtrace is not (directly) related
b) suspending the compositor (Shift+Alt+F12) would likely unfreeze the screen as well

To get a rough idea about the source of the problem: does this happen with xrender compositing as well? ("kcmshell4 kwincompositing", 3rd tab)
Comment 2 Alex Austin 2013-07-25 03:36:28 UTC
Can this bug be resolved NOTMYPROBLEM or something along those lines? This failure also happens while kwin isn't running, so it must be some strange interaction between the intel driver and Java. XRender compositing makes no difference and Shift+Alt+F12 does not un-freeze the display.
Comment 3 Thomas Lübking 2013-07-25 03:57:24 UTC
either a bug in the driver or java (that popup at least) grabs the server.

Since you mentioned "kwin not running" - but another WM and/or compositor instead?
Comment 4 Alex Austin 2013-07-25 04:01:09 UTC
No. Quit kwin, ran without a wm to test, started kwin again when done.
Comment 5 Thomas Lübking 2013-07-25 04:12:51 UTC
what "unfroze" the screen in that case?
Comment 6 Alex Austin 2013-07-25 04:17:34 UTC
Just waiting for a few minutes.
Comment 7 Thomas Lübking 2013-07-25 04:28:48 UTC
Did you check /var/log/Xorg.0.log for errors?
Eventually dmesg?