Bug 259064 - Dolphin crash on exit
Summary: Dolphin crash on exit
Status: RESOLVED DUPLICATE of bug 257944
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: 16.12.2
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Peter Penz
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-12-07 00:41 UTC by Valentin Rusu
Modified: 2010-12-10 00:26 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
New crash information added by DrKonqi (2.13 KB, text/plain)
2010-12-07 12:15 UTC, Alex Richardson
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Valentin Rusu 2010-12-07 00:41:17 UTC
Application: dolphin (1.5.9)
KDE Platform Version: 4.5.80 (4.6 Beta1)
Qt Version: 4.7.1
Operating System: Linux 2.6.37-rc3-git1-6-default i686
Distribution: "openSUSE 11.4 Milestone 4 of 6 (i586)"

-- Information about the crash:
- What I was doing when the application crashed:
I was just closing it by closing it's main window.
The crash handler popped up

-- Backtrace:
Application: Dolphin (kdeinit4), signal: Aborted
[KCrash Handler]
#7  0xffffe430 in __kernel_vsyscall ()
#8  0xb606291f in raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#9  0xb6064260 in abort () at abort.c:92
#10 0xb609ef27 in __libc_message (do_abort=2, fmt=0xb61670b4 "*** glibc detected *** %s: %s: 0x%s ***\n") at ../sysdeps/unix/sysv/linux/libc_fatal.c:186
#11 0xb60a4f6b in malloc_printerr (action=<value optimized out>, str=<value optimized out>, ptr=0x8609b48) at malloc.c:6267
#12 0xb60a9ab9 in __libc_free (mem=0x8609b48) at malloc.c:3700
#13 0xb62558af in operator delete(void*) () from /usr/lib/libstdc++.so.6
#14 0xb62364cb in std::basic_string<char, std::char_traits<char>, std::allocator<char> >::_Rep::_M_destroy(std::allocator<char> const&) () from /usr/lib/libstdc++.so.6
#15 0xb623657a in std::basic_string<char, std::char_traits<char>, std::allocator<char> >::~basic_string() () from /usr/lib/libstdc++.so.6
#16 0xb606591f in __run_exit_handlers (status=0, listp=0xb61a0304, run_list_atexit=true) at exit.c:78
#17 0xb606597d in exit (status=0) at exit.c:100
#18 0x0804e539 in launch (argc=5, _name=0x80c46dc "/usr/bin/dolphin", args=<value optimized out>, cwd=0x0, envc=1, envs=<value optimized out>, reset_env=false, tty=0x0, avoid_loops=false, startup_id_str=0x80c472b "zamox.rusu.info;1291673078;553841;2283_TIME1513708") at /usr/src/debug/kdelibs-4.5.80/kinit/kinit.cpp:730
#19 0x0804f067 in handle_launcher_request (sock=8, who=<value optimized out>) at /usr/src/debug/kdelibs-4.5.80/kinit/kinit.cpp:1222
#20 0x0804f70c in handle_requests (waitForPid=<value optimized out>) at /usr/src/debug/kdelibs-4.5.80/kinit/kinit.cpp:1415
#21 0x08050589 in main (argc=) at /usr/src/debug/kdelibs-4.5.80/kinit/kinit.cpp:1901

Possible duplicates by query: bug 257531, bug 255512, bug 255312, bug 254668, bug 253841.

Reported using DrKonqi
Comment 1 Alex Richardson 2010-12-07 12:15:15 UTC
Created attachment 54240 [details]
New crash information added by DrKonqi

dolphin (1.5.9) on KDE Platform 4.5.80 (4.6 Beta1) using Qt 4.7.1

- What I was doing when the application crashed:
I just closed dolphin and then the crash happened. I had the console open iside dolphin and had run a program from it before. Maybe this has something to do with the crash.

-- Backtrace (Reduced):
#8  0x00007fc604ce0c53 in __libc_message (do_abort=2, fmt=0x7fc604d95018 "*** glibc detected *** %s: %s: 0x%s ***\n") at ../sysdeps/unix/sysv/linux/libc_fatal.c:186
#9  0x00007fc604ce6226 in malloc_printerr (action=3, str=0x7fc604d921fe "free(): invalid pointer", ptr=<value optimized out>) at malloc.c:6267
[...]
#11 0x00007fc604ca84e1 in __run_exit_handlers (status=0, listp=0x7fc604fcd4a8, run_list_atexit=true) at exit.c:78
#12 0x00007fc604ca8535 in exit (status=12596) at exit.c:100
#13 0x0000000000407610 in _start ()
Comment 2 Dario Andres 2010-12-10 00:26:26 UTC
[Comment from a bug triager]
This issue is being tracked at bug 257944. Merging. Thanks

*** This bug has been marked as a duplicate of bug 257944 ***