Bug 225492 - konqueror crashes while loading the www page after any user interation
Summary: konqueror crashes while loading the www page after any user interation
Status: RESOLVED DUPLICATE of bug 210445
Alias: None
Product: konqueror
Classification: Applications
Component: general (other bugs)
Version First Reported In: unspecified
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: Konqueror Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-02-04 12:13 UTC by Zbigniew Lisiecki
Modified: 2010-02-05 21:37 UTC (History)
1 user (show)

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

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Zbigniew Lisiecki 2010-02-04 12:13:48 UTC 
Application that crashed: konqueror
Version of the application: 4.3.1 (KDE 4.3.1) "release 6"
KDE Version: 4.3.1 (KDE 4.3.1) "release 6"
Qt Version: 4.5.3
Operating System: Linux 2.6.31.8-andra x86_64
Distribution: "openSUSE 11.2 (x86_64)"

What I was doing when the application crashed:
konqueror crashes when mbank.com.pl enters the account .(https) The problem regards timing. It depends on that how early user interation takes place while the www page is loading.

 -- Backtrace:
Application: Konqueror (kdeinit4), signal: Segmentation fault
[Current thread is 1 (Thread 0x7f2ab28bd750 (LWP 18277))]

Thread 2 (Thread 0x7f2a9b64e910 (LWP 18285)):
#0  0x00007f2ab20942cd in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
#1  0x00007f2ab23044a2 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib64/libQtCore.so.4
#2  0x00007f2ab22fa5e2 in ?? () from /usr/lib64/libQtCore.so.4
#3  0x00007f2ab2303485 in ?? () from /usr/lib64/libQtCore.so.4
#4  0x00007f2ab208f65d in start_thread () from /lib64/libpthread.so.0
#5  0x00007f2aafaa314d in clone () from /lib64/libc.so.6
#6  0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f2ab28bd750 (LWP 18277)):
[KCrash Handler]
#5  0x00007f2aa16ad1c6 in KHTMLView::eventFilter(QObject*, QEvent*) () from /usr/lib64/libkhtml.so.5
#6  0x00007f2ab23e8127 in QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) () from /usr/lib64/libQtCore.so.4
#7  0x00007f2ab01d927c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#8  0x00007f2ab01e1093 in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#9  0x00007f2ab0dd38d6 in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5
#10 0x00007f2ab23e8ddc in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/libQtCore.so.4
#11 0x00007f2ab0268c6a in ?? () from /usr/lib64/libQtGui.so.4
#12 0x00007f2ab026b1d0 in ?? () from /usr/lib64/libQtGui.so.4
#13 0x00007f2ab0244774 in QApplication::x11ProcessEvent(_XEvent*) () from /usr/lib64/libQtGui.so.4
#14 0x00007f2ab026cb6c in ?? () from /usr/lib64/libQtGui.so.4
#15 0x00007f2aaf122dde in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#16 0x00007f2aaf1267a8 in ?? () from /usr/lib64/libglib-2.0.so.0
#17 0x00007f2aaf1268d0 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#18 0x00007f2ab24113a3 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#19 0x00007f2ab026c31e in ?? () from /usr/lib64/libQtGui.so.4
#20 0x00007f2ab23e7712 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#21 0x00007f2ab23e7ae4 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#22 0x00007f2ab23e9c99 in QCoreApplication::exec() () from /usr/lib64/libQtCore.so.4
#23 0x00007f2aa7864f83 in kdemain () from /usr/lib64/libkdeinit4_konqueror.so
#24 0x0000000000406f88 in _start ()

Reported using DrKonqi
Comment 1 Dario Andres 2010-02-05 16:30:15 UTC 
- Can you repeat this crash consistenly using the steps you described ?
Regards
Comment 2 Zbigniew Lisiecki 2010-02-05 21:04:24 UTC 
Dnia piątek, 5 lutego 2010 o 16:30:19 Dario Andres napisał(a):
> https://bugs.kde.org/show_bug.cgi?id=225492
> 
> 
> Dario Andres <andresbajotierra@gmail.com> changed:
> 
>            What    |Removed                     |Added
> ---------------------------------------------------------------------------
> - CC|                            |andresbajotierra@gmail.com
> 
> 
> 
> 
> --- Comment #1 from Dario Andres <andresbajotierra gmail com>  2010-02-05
>  16:30:15 --- - Can you repeat this crash consistenly using the steps you
>  described ? Regards
> 
Yes, I can. Unfortunately I can repeat it each time only with https of my bank 
(mbank.com.pl). I just log in and press any button, which appears before the 
whole page is loaded. Then it crashes for sure.
Yet sometimes it crashes when the RAM seems to be full too.
 regards, Zbyszek
Comment 3 Zbigniew Lisiecki 2010-02-05 21:36:29 UTC 
Dnia piątek, 5 lutego 2010 o 16:30:19 Dario Andres napisał(a):
> https://bugs.kde.org/show_bug.cgi?id=225492
> 
> 
> Dario Andres <andresbajotierra@gmail.com> changed:
> 
>            What    |Removed                     |Added
> ---------------------------------------------------------------------------
> - CC|                            |andresbajotierra@gmail.com
> 
> 
> 
> 
> --- Comment #1 from Dario Andres <andresbajotierra gmail com>  2010-02-05
>  16:30:15 --- - Can you repeat this crash consistenly using the steps you
>  described ? Regards
> 
Yes, I can. Unfortunately I can repeat it each time only with https of my bank 
(mbank.com.pl). I just log in and press any button, which appears before the 
whole page is loaded. Then it crashes for sure.
Yet sometimes it crashes with user interaction when the RAM seems to be full 
too.
 regards, Zbyszek
Comment 4 Tommi Tervo 2010-02-05 21:37:15 UTC 

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