Summary: | Unmotivated konqueror crash in background | ||
---|---|---|---|
Product: | [Applications] konqueror | Reporter: | Steffen Möller <steffen_moeller> |
Component: | general | Assignee: | Konqueror Developers <konq-bugs> |
Status: | CLOSED INTENTIONAL | ||
Severity: | crash | CC: | adawit |
Priority: | NOR | ||
Version First Reported In: | 4.6.5 | ||
Target Milestone: | --- | ||
Platform: | Debian unstable | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Steffen Möller
2011-12-04 22:12:38 UTC
(In reply to comment #0) > Application: konqueror (4.6.5 (4.6.5)) > KDE Platform Version: 4.6.5 (4.6.5) > Qt Version: 4.7.3 > Operating System: Linux 3.1.0-1-amd64 x86_64 > Distribution: Debian GNU/Linux unstable (sid) > > -- Information about the crash: > - What I was doing when the application crashed: > > I was reading mail. Konqueror ran in the background. > > - Unusual behavior I noticed: > > Icedove used the full screen. I just swapped and found another Window of > Konqeuror still open. Weird. Icedove takes quite some memory but konqueror is > till running and takes quite some CPU time (Intel Centrino Duo laptop). From > top: > 3006 moeller 20 0 648m 63m 7732 R 99.3 6.4 1:40.33 konqueror > > -- Backtrace: > Application: Konqueror (kdeinit4), signal: Segmentation fault > [Current thread is 1 (Thread 0x7f95ddb34760 (LWP 3013))] > > Thread 3 (Thread 0x7f95a7a70700 (LWP 3649)): > #0 __lll_lock_wait_private () at > ../nptl/sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:97 > #1 0x00007f95db319f48 in _L_lock_9627 () from /lib/x86_64-linux-gnu/libc.so.6 > #2 0x00007f95db318331 in *__GI___libc_free (mem=0x7f95b8000020) at > malloc.c:3736 > #3 0x00007f95d83912dd in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 > #4 0x00007f95dc7a5a07 in QEventDispatcherGlib::~QEventDispatcherGlib > (this=0x4168100, __in_chrg=<optimized out>) at > kernel/qeventdispatcher_glib.cpp:373 > #5 0x00007f95dc7a5c19 in QEventDispatcherGlib::~QEventDispatcherGlib > (this=0x4168100, __in_chrg=<optimized out>) at > kernel/qeventdispatcher_glib.cpp:401 > #6 0x00007f95dc693d84 in QThreadPrivate::finish (arg=0x20fa6b0) at > thread/qthread_unix.cpp:356 > #7 0x00007f95dc694c2d in ~__pthread_cleanup_class (this=<synthetic pointer>, > __in_chrg=<optimized out>) at /usr/include/pthread.h:545 > #8 ~__pthread_cleanup_class (this=<synthetic pointer>, __in_chrg=<optimized > out>) at thread/qthread_unix.cpp:801 > #9 QThreadPrivate::start (arg=0x20fa6b0) at thread/qthread_unix.cpp:279 > #10 0x00007f95d8e64b40 in start_thread (arg=<optimized out>) at > pthread_create.c:304 > #11 0x00007f95db37636d in clone () at > ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 > #12 0x0000000000000000 in ?? () > > Thread 2 (Thread 0x7f95a92b6700 (LWP 3664)): > #0 __lll_lock_wait_private () at > ../nptl/sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:97 > #1 0x00007f95db319f48 in _L_lock_9627 () from /lib/x86_64-linux-gnu/libc.so.6 > #2 0x00007f95db318331 in *__GI___libc_free (mem=0x7f95b8000020) at > malloc.c:3736 > #3 0x00007f95d83afc8f in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 > #4 0x00007f95d83afe7d in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 > #5 0x00007f95d8e64129 in __nptl_deallocate_tsd () at pthread_create.c:155 > #6 0x00007f95d8e64b4e in start_thread (arg=<optimized out>) at > pthread_create.c:311 > #7 0x00007f95db37636d in clone () at > ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 > #8 0x0000000000000000 in ?? () > > Thread 1 (Thread 0x7f95ddb34760 (LWP 3013)): > [KCrash Handler] > #6 malloc_consolidate (av=0x7f95b8000020) at malloc.c:5155 This indicates a crash in the system memory allocation rountines. Based on your comments above, "Icedove takes quite some memory...", this likely caused exhaustion of your system memory ??? Anyhow, can you reliably reproduce this crash in KDE v4.7.4 or higher ? I am on 4.7.4 for a while now and have not experienced this particular crash again. I admit to have mostly been avoiding konqueror since then, though, because of this and its neglect by all those java script savvy pages. That laptop only has 1G of memory, an exhaustion is well possible. If there are no others experiencing the same beast and if there is no immediate idea what to fix - then just ignore it, it is fine. |