Bug 277374 - cross-fuzz crashed konqueror
Summary: cross-fuzz crashed konqueror
Status: RESOLVED WORKSFORME
Alias: None
Product: konqueror
Classification: Applications
Component: khtml (show other bugs)
Version: 4.6.4
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Konqueror Developers
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2011-07-08 17:23 UTC by maninred
Modified: 2018-10-27 02:39 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description maninred 2011-07-08 17:23:35 UTC
Application: konqueror (4.6.4 (4.6.4))
KDE Platform Version: 4.6.4 (4.6.4)
Qt Version: 4.7.3
Operating System: Linux 2.6.39-2-desktop x86_64
Distribution: "openSUSE 12.1 Milestone 2 (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:

Ive used cross_fuzz. The result semms to be the same like in the associated report.

-- Backtrace:
Application: Konqueror (kdeinit4), signal: Aborted
82	T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS)
[KCrash Handler]
#6  0x00007f8fc1bfccc5 in raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#7  0x00007f8fc1bfe1db in abort () at abort.c:92
#8  0x00007f8fc200be4d in __gnu_cxx::__verbose_terminate_handler () at ../../../../libstdc++-v3/libsupc++/vterminate.cc:95
#9  0x00007f8fc2009ff6 in __cxxabiv1::__terminate (handler=<optimized out>) at ../../../../libstdc++-v3/libsupc++/eh_terminate.cc:40
#10 0x00007f8fc200a023 in std::terminate () at ../../../../libstdc++-v3/libsupc++/eh_terminate.cc:50
#11 0x00007f8fc200a166 in __cxxabiv1::__cxa_rethrow () at ../../../../libstdc++-v3/libsupc++/eh_throw.cc:116
#12 0x00007f8fc32671f6 in QEventLoop::exec (this=<optimized out>, flags=<optimized out>) at kernel/qeventloop.cpp:214
#13 0x00007f8fc326b2b7 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1008
#14 0x00007f8fb39269f2 in kdemain (argc=<optimized out>, argv=<optimized out>) at /usr/src/debug/kdebase-4.6.4/konqueror/src/konqmain.cpp:219
#15 0x0000000000408b17 in launch (argc=1, _name=0x681018 "konqueror", args=<optimized out>, cwd=0x0, envc=<optimized out>, envs=<optimized out>, reset_env=false, tty=0x0, avoid_loops=false, startup_id_str=0x40af57 "0") at /usr/src/debug/kdelibs-4.6.4/kinit/kinit.cpp:734
#16 0x0000000000409b46 in handle_launcher_request (sock=8, who=<optimized out>) at /usr/src/debug/kdelibs-4.6.4/kinit/kinit.cpp:1226
#17 0x000000000040a087 in handle_requests (waitForPid=0) at /usr/src/debug/kdelibs-4.6.4/kinit/kinit.cpp:1419
#18 0x000000000040575f in main (argc=4, argv=0x7fff00000001, envp=0x7fff579f95e0) at /usr/src/debug/kdelibs-4.6.4/kinit/kinit.cpp:1907

This bug may be a duplicate of or related to bug 277373.

Possible duplicates by query: bug 277373, bug 273425, bug 265216, bug 261118, bug 258646.

Reported using DrKonqi
Comment 1 Tommi Tervo 2011-07-08 18:38:35 UTC
konqueror: /home/teve/kde/kde-baseapps/konqueror/src/konqview.cpp:308: bool KonqView::changePart(const QString&, const QString&, bool): Assertion `!m_bLoading' failed.
Comment 2 Jekyll Wu 2013-11-10 08:42:15 UTC
Unfortunately, the backtrace doesn't contain much helpful information due to uncaught exception (not your fault). 

If you can reproduce the crash every time,  please follow the guide[1] and try to run it under gdb to get a better backtrace.  

[1] http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_when_an_uncaught_exception_is_causing_a_crash
Comment 3 Andrew Crouthamel 2018-09-25 03:50:47 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 4 Andrew Crouthamel 2018-10-27 02:39:54 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!