rekonq crashed after opening a *.ui file and pressing ctrl+w many times

Bug #1062169 reported by phobie
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
rekonq
Fix Released
High
rekonq (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Two bugs leads into a crash:
* Opening a *.ui file always results into a open loop.
* Fastly closing with ctrl+w seems to have a race condition in the open tab counter.
   (You can close the last tab which is not possible if you do it slowly)

See https://bugs.kde.org/show_bug.cgi?id=307733

Found in 0.9.1-0ubuntu2
Fixed in 1.0

Revision history for this message
In , Kdebugs-phobie (kdebugs-phobie) wrote :
Download full text (20.3 KiB)

Application: rekonq (0.9.1)
KDE Platform Version: 4.8.5 (4.8.5)
Qt Version: 4.8.1
Operating System: Linux 3.2.0-31-generic x86_64
Distribution: Ubuntu 12.04.1 LTS

-- Information about the crash:
- What I was doing when the application crashed:
I double-clicked on a *.ui file.
Because of a wrong file association rekonq has been started instead of designer-qt4.
rekonq opened the file again and again
After about 100 tabs had been opened I pressed and hold CTRL+w
The browser started to close tabs while still opening new ones.
It crashed in the moment when the last tab closed.

Same behaviour if I drag'n'drop a ui-file to a open rekonq window or if I type the path manually into the address-bar.

The content of the ui-file does not matter.
It also works with a empty file.

- Custom settings of the application:
I also did a "rm -rf ~/.kde/share/config/rekonqrc ~/.kde/share/apps/rekonq" which did not help either.

-- Backtrace:
Application: rekonq (rekonq), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f5b66a85780 (LWP 14024))]

Thread 12 (Thread 0x7f5b50c14700 (LWP 14028)):
#0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162
#1 0x00007f5b65315dec in WTF::TCMalloc_PageHeap::scavengerThread (this=0x7f5b65cdede0) at wtf/FastMalloc.cpp:2495
#2 0x00007f5b65315f19 in WTF::TCMalloc_PageHeap::runScavengerThread (context=<optimized out>) at wtf/FastMalloc.cpp:1618
#3 0x00007f5b604c8e9a in start_thread (arg=0x7f5b50c14700) at pthread_create.c:308
#4 0x00007f5b66296dbd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#5 0x0000000000000000 in ?? ()

Thread 11 (Thread 0x7f5b500ef700 (LWP 14029)):
#0 0x00007f5b6628b403 in __GI___poll (fds=<optimized out>, nfds=<optimized out>, timeout=<optimized out>) at ../sysdeps/unix/sysv/linux/poll.c:87
#1 0x00007f5b5eb6b036 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2 0x00007f5b5eb6b164 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3 0x00007f5b60e82426 in QEventDispatcherGlib::processEvents (this=0x7f5b480008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#4 0x00007f5b60e51c82 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149
#5 0x00007f5b60e51ed7 in QEventLoop::exec (this=0x7f5b500eee00, flags=...) at kernel/qeventloop.cpp:204
#6 0x00007f5b60d50fa7 in QThread::exec (this=<optimized out>) at thread/qthread.cpp:501
#7 0x00007f5b60d53fcb in QThreadPrivate::start (arg=0x1ffb4c0) at thread/qthread_unix.cpp:298
#8 0x00007f5b604c8e9a in start_thread (arg=0x7f5b500ef700) at pthread_create.c:308
#9 0x00007f5b66296dbd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#10 0x0000000000000000 in ?? ()

Thread 10 (Thread 0x7f5b4f263700 (LWP 14031)):
#0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162
#1 0x00007f5b65e87222 in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4
#2 0x00007f5b65e87259 in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4
#3 0x00007f5b604c8e9a in start_thread (arg=0x7f5b4f263700) at pth...

Revision history for this message
In , Andrea Diamantini (adjam7) wrote :

You'll find this fixed in the 1.x series

phobie (phobie)
tags: added: upstream
tags: added: fixed-upstream
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

1.1 is in Quantal already.

Changed in rekonq (Ubuntu):
status: New → Fix Released
Changed in rekonq:
importance: Unknown → High
status: Unknown → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.