| Summary: | Konqueror crashed while accessing internetbanking site | ||
|---|---|---|---|
| Product: | [Applications] konqueror | Reporter: | kavol <kavol> |
| Component: | general | Assignee: | Konqueror Developers <konq-bugs> |
| Status: | RESOLVED UPSTREAM | ||
| Severity: | crash | CC: | adawit, kavol |
| Priority: | NOR | ||
| Version: | 4.8.5 | ||
| Target Milestone: | --- | ||
| Platform: | Fedora RPMs | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
New crash information added by DrKonqi
New crash information added by DrKonqi New crash information added by DrKonqi |
||
|
Description
kavol
2012-09-06 11:34:17 UTC
Created attachment 73702 [details]
New crash information added by DrKonqi
konqueror (4.8.5 (4.8.5)) on KDE Platform 4.8.5 (4.8.5) using Qt 4.8.2
- What I was doing when the application crashed:
It crashes reproducibly, although the backtrace looks a bit different this time ...
-- Backtrace (Reduced):
#6 0x0000003846835925 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#7 0x00000038468370d8 in __GI_abort () at abort.c:91
[...]
#9 0x000000384687bfee in malloc_printerr (ptr=0x87d790, str=0x3846978960 "free(): invalid next size (normal)", action=3) at malloc.c:5027
#10 _int_free (av=0x3846bb0720, p=0x87d780, have_lock=0) at malloc.c:3948
#11 0x000000384984d37f in g_free (mem=0x87d790) at gmem.c:252
The problem is upstream at Gstreamer, please report this there. (In reply to comment #2) > The problem is upstream at Gstreamer, please report this there. I'm not that sure, have you examined also the trace from the second crash? - to me, it looks more like that konqueror does something bad to the plugins which results in crash which is blamed on the plugin then ... /me is going to try again Created attachment 73717 [details]
New crash information added by DrKonqi
konqueror (4.8.5 (4.8.5)) on KDE Platform 4.8.5 (4.8.5) using Qt 4.8.2
- What I was doing when the application crashed:
another crash under the same circumstances
gstreamer involved again, but this time the code path differs - DrKonqi did not suggest this as duplicate (I got suggestion for kded crash ... guess the DKonqi AI needs some work too :-))
-- Backtrace (Reduced):
#6 magazine_cache_pop_magazine (countp=0x17b9fb8, ix=0) at gslice.c:726
#7 thread_memory_magazine1_reload (ix=0, tmem=<optimized out>) at gslice.c:794
#8 g_slice_alloc (mem_size=mem_size@entry=16) at gslice.c:992
#9 0x000000384986245e in g_slist_prepend (list=list@entry=0x7f6980001f90 = {...}, data=0x384b4140d0) at gslist.c:265
#10 0x000000384b42d7ee in type_class_init_Wm (pclass=0x2c419b0, node=0x3585310) at gtype.c:2147
Created attachment 73718 [details]
New crash information added by DrKonqi
konqueror (4.8.5 (4.8.5)) on KDE Platform 4.8.5 (4.8.5) using Qt 4.8.2
- What I was doing when the application crashed:
... and again with IcedTea to be blamed this time (DrKonqi has found the duplicate now)
-- Backtrace (Reduced):
#6 0x0000003846835925 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#7 0x00000038468370d8 in __GI_abort () at abort.c:91
[...]
#9 0x000000384687bfee in malloc_printerr (ptr=0xbbba90, str=0x38469789c8 "double free or corruption (!prev)", action=3) at malloc.c:5027
#10 _int_free (av=0x3846bb0720, p=0xbbba80, have_lock=0) at malloc.c:3948
#11 0x000000384984d37f in g_free (mem=0xbbba90) at gmem.c:252
please re-evaluate this bug (sorry for the noise if I am mistaken ... but at least then I will know that I need to file new bugs both for GStreamer and for IcedTea) also note that I've tried to run konqueror under Valgrind, and it crashed even before displaying the login page; the last error reported by valgrind is: ==24978== Invalid read of size 4 ==24978== at 0x34759D0778: WebCore::findAtomicString(JSC::Identifier const&) (JSDOMBinding.cpp:133) ==24978== by 0x34759FC34B: WebCore::JSHTMLDocument::canGetItemsForName(JSC::ExecState*, WebCore::HTMLDocument*, JSC::Identifier const&) (JSHTMLDocumentCustom.cpp:55) ==24978== by 0x34756459D4: WebCore::JSHTMLDocument::getOwnPropertySlot(JSC::ExecState*, JSC::Identifier const&, JSC::PropertySlot&) (JSHTMLDocument.cpp:175) ==24978== by 0x34762544C5: JSC::JSValue::get(JSC::ExecState*, JSC::Identifier const&, JSC::PropertySlot&) const (JSObject.h:512) ==24978== by 0x34762492A1: cti_op_get_by_id_method_check (JITStubs.cpp:1520) ==24978== by 0x39447CB3: ??? ==24978== by 0x3476240E60: JSC::Interpreter::execute(JSC::ProgramExecutable*, JSC::ExecState*, JSC::ScopeChainNode*, JSC::JSObject*) (JITCode.h:77) ==24978== by 0x347625CAD0: JSC::evaluate(JSC::ExecState*, JSC::ScopeChainNode*, JSC::SourceCode const&, JSC::JSValue) (Completion.cpp:64) ==24978== by 0x3475A2D3D5: WebCore::ScriptController::evaluateInWorld(WebCore::ScriptSourceCode const&, WebCore::DOMWrapperWorld*) (JSMainThreadExecState.h:54) ==24978== by 0x3475A2DE71: WebCore::ScriptController::evaluate(WebCore::ScriptSourceCode const&) (ScriptController.cpp:166) ==24978== by 0x34759BB709: WebCore::ScriptController::executeScript(WebCore::ScriptSourceCode const&) (ScriptControllerBase.cpp:64) ==24978== by 0x34759652B1: QWebFrame::evaluateJavaScript(QString const&) (qwebframe.cpp:1539) ==24978== Address 0x1d00000120 is not stack'd, malloc'd or (recently) free'd (In reply to comment #6) > please re-evaluate this bug (sorry for the noise if I am mistaken ... but at > least then I will know that I need to file new bugs both for GStreamer and > for IcedTea) You are mistaken. How can Konqueror cause crash in upstream packages ? Even if you fell like this is not a bug in the plugins, the issue would still be upstream in QtWebKit. But that is not even the case at least as far as the icedtea java applet plugin is concerned. But do not take my words for it, go read the last few comments in bug# 242415. > also note that I've tried to run konqueror under Valgrind, and it crashed > even before displaying the login page; the last error reported by valgrind Does not matter. I cannot run Konqueror + webkit engine through valgrind either. It never worked for me and I doubt it ever will, but that simply means QtWebKit (or webkit in general) does something that breaks how valgrind attempts to emulate a machine. I won't be going out on a limb to say that it is probably the JIT based javascript engine that gives it fits. Regardless, this has no impact on this bug report. This issue is an upstream problem. |