Bug 333141 - Crash while creating bookmark
Summary: Crash while creating bookmark
Status: RESOLVED WORKSFORME
Alias: None
Product: konqueror
Classification: Applications
Component: general (show other bugs)
Version: 4.11.5
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Konqueror Developers
URL:
Keywords: drkonqi, triaged
Depends on:
Blocks:
 
Reported: 2014-04-07 01:31 UTC by steve
Modified: 2018-10-27 03:56 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description steve 2014-04-07 01:31:03 UTC
Application: konqueror (4.11.5)
KDE Platform Version: 4.11.5
Qt Version: 4.8.4
Operating System: Linux 3.11.0-19-generic i686
Distribution: Ubuntu 13.10

-- Information about the crash:
- What I was doing when the application crashed:
I went to www.drudgereport.com.  It came up, but was probably still busy loading.  I went to create a bookmark for it.  Things hung, and the browser window turned dark.  I went away for a while, and found messages that the application had crashed when I returned.

- Unusual behavior I noticed:

- Custom settings of the application:
Nothin special, this is a new install and I'm just getting used to it.

-- Backtrace:
Application: Konqueror (konqueror), signal: Aborted
Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0xb4c0c740 (LWP 18455))]

Thread 4 (Thread 0xb24edb40 (LWP 18458)):
#0  0xb521a86e in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#1  0xb521abe8 in g_mutex_unlock () from /lib/i386-linux-gnu/libglib-2.0.so.0
#2  0xb51d7b53 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#3  0xb51d804b in g_main_loop_run () from /lib/i386-linux-gnu/libglib-2.0.so.0
#4  0xb33a132a in ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
#5  0xb51fdc4a in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#6  0xb52b5d78 in start_thread (arg=0xb24edb40) at pthread_create.c:311
#7  0xb755001e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:131

Thread 3 (Thread 0xb1a74b40 (LWP 18459)):
#0  0xb770a424 in __kernel_vsyscall ()
#1  0xb753e8db in read () at ../sysdeps/unix/syscall-template.S:81
#2  0xb5219d4e in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#3  0xb51d765b in g_main_context_check () from /lib/i386-linux-gnu/libglib-2.0.so.0
#4  0xb51d7afa in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#5  0xb51d7ca8 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0
#6  0xb51d7d2e in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#7  0xb51fdc4a in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#8  0xb52b5d78 in start_thread (arg=0xb1a74b40) at pthread_create.c:311
#9  0xb755001e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:131

Thread 2 (Thread 0xb10ffb40 (LWP 18496)):
#0  0xb770a424 in __kernel_vsyscall ()
#1  0xb75634d2 in clock_gettime (clock_id=1, tp=0xb10fefe8) at ../sysdeps/unix/clock_gettime.c:115
#2  0xb5b2b3ec in do_gettime (frac=0xb10fefe0, sec=0xb10fefd8) at tools/qelapsedtimer_unix.cpp:123
#3  qt_gettime () at tools/qelapsedtimer_unix.cpp:140
#4  0xb5c10fd2 in updateCurrentTime (this=0xb070d854) at kernel/qeventdispatcher_unix.cpp:354
#5  QTimerInfoList::timerWait (this=0xb070d854, tm=...) at kernel/qeventdispatcher_unix.cpp:461
#6  0xb5c0f67b in timerSourcePrepareHelper (src=<optimized out>, timeout=0xb10ff0dc) at kernel/qeventdispatcher_glib.cpp:136
#7  0xb5c0f70d in timerSourcePrepare (source=0xb070d820, timeout=0xb10ff0dc) at kernel/qeventdispatcher_glib.cpp:169
#8  0xb51d7143 in g_main_context_prepare () from /lib/i386-linux-gnu/libglib-2.0.so.0
#9  0xb51d7a5f in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#10 0xb51d7ca8 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0
#11 0xb5c0f8df in QEventDispatcherGlib::processEvents (this=0xb07019f0, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#12 0xb5bde9f3 in QEventLoop::processEvents (this=this@entry=0xb10ff248, flags=...) at kernel/qeventloop.cpp:149
#13 0xb5bded19 in QEventLoop::exec (this=this@entry=0xb10ff248, flags=...) at kernel/qeventloop.cpp:204
#14 0xb5acde3d in QThread::exec (this=this@entry=0x8c063d8) at thread/qthread.cpp:542
#15 0xb70867a6 in KIO::NameLookUpThread::run (this=0x8c063d8) at ../../kio/kio/hostinfo.cpp:226
#16 0xb5ad072f in QThreadPrivate::start (arg=0x8c063d8) at thread/qthread_unix.cpp:338
#17 0xb52b5d78 in start_thread (arg=0xb10ffb40) at pthread_create.c:311
#18 0xb755001e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:131

Thread 1 (Thread 0xb4c0c740 (LWP 18455)):
[KCrash Handler]
#7  0xb770a424 in __kernel_vsyscall ()
#8  0xb748caff in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
#9  0xb7490083 in __GI_abort () at abort.c:90
#10 0xb5950605 in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/i386-linux-gnu/libstdc++.so.6
#11 0xb594e273 in ?? () from /usr/lib/i386-linux-gnu/libstdc++.so.6
#12 0xb594e2af in std::terminate() () from /usr/lib/i386-linux-gnu/libstdc++.so.6
#13 0xb594e565 in __cxa_rethrow () from /usr/lib/i386-linux-gnu/libstdc++.so.6
#14 0xb5bdef05 in QEventLoop::exec (this=this@entry=0xbfb28288, flags=...) at kernel/qeventloop.cpp:218
#15 0xb5be489e in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1218
#16 0xb6139974 in QApplication::exec () at kernel/qapplication.cpp:3828
#17 0xb76d8a75 in kdemain (argc=3, argv=0xbfb284f4) at ../../../konqueror/src/konqmain.cpp:242
#18 0x0804855b in main (argc=3, argv=0xbfb284f4) at konqueror_dummy.cpp:3

Possible duplicates by query: bug 332942, bug 332891, bug 332890, bug 332769, bug 332381.

Reported using DrKonqi
Comment 1 Dawit Alemayehu 2014-06-14 21:30:09 UTC
Can you readily reproduce this crash?
Comment 2 steve 2014-06-15 18:04:52 UTC
On 06/14/2014 03:30 PM, Dawit Alemayehu wrote:
> https://bugs.kde.org/show_bug.cgi?id=333141
>
> Dawit Alemayehu <adawit@kde.org> changed:
>
>             What    |Removed                     |Added
> ----------------------------------------------------------------------------
>               Status|UNCONFIRMED                 |NEEDSINFO
>                   CC|                            |adawit@kde.org
>           Resolution|---                         |WAITINGFORINFO
>
> --- Comment #1 from Dawit Alemayehu <adawit@kde.org> ---
> Can you readily reproduce this crash?
>
Yes.  I just tried it again with the same result.
-- Steve
Comment 3 Dawit Alemayehu 2014-06-15 18:09:02 UTC
(In reply to comment #2)
> On 06/14/2014 03:30 PM, Dawit Alemayehu wrote:
> > https://bugs.kde.org/show_bug.cgi?id=333141
> >
> > Dawit Alemayehu <adawit@kde.org> changed:
> >
> >             What    |Removed                     |Added
> > ----------------------------------------------------------------------------
> >               Status|UNCONFIRMED                 |NEEDSINFO
> >                   CC|                            |adawit@kde.org
> >           Resolution|---                         |WAITINGFORINFO
> >
> > --- Comment #1 from Dawit Alemayehu <adawit@kde.org> ---
> > Can you readily reproduce this crash?
> >
> Yes.  I just tried it again with the same result.

Do you get the same backtrace in the crash dialog? Unfortunately the backtrace you provided has no useful information and I cannot reproduce the crash though I am testing with KDE 4.13 and not KDE 4.11.
Comment 4 Andrew Crouthamel 2018-09-25 03:37:43 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 5 Andrew Crouthamel 2018-10-27 03:56:51 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!