Summary: | Google maps in Konqueror [@ KJSDebugger::DebugDocument::name] | ||
---|---|---|---|
Product: | [Applications] konqueror | Reporter: | Kris <komealy> |
Component: | khtml ecma | Assignee: | Konqueror Developers <konq-bugs> |
Status: | RESOLVED UNMAINTAINED | ||
Severity: | crash | CC: | 1446744399, adrien.bellanger, aiacovitti, justin.zobel |
Priority: | NOR | ||
Version: | 4.11.2 | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
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
Kris
2010-04-27 19:57:37 UTC
Turn off the JavaScript debugger if you're not using it (it is off by default). It's what's crashing here. Well, I only turned it on for this instance to see if I could get any info on it. Funny enough, I got Google maps to work (with the debugger disabled) with a workaround. I had to change my browser identification to Safari 3.5 on Mac OSX, then back to default and now it works like a champ. I'm not really sure what the issue is then. Sorry, it was Safari 3.2. The graying out of the map area happens every time that Konqueror is started, until I change the browser ID like I did in my post above, then it will work fine until I close Konqueror again. I would just leave it on the Safari ID, but when it is set that way the mouse wheel doesn't work to zoom, and you can't click and drag to pan. *** Bug 263527 has been marked as a duplicate of this bug. *** Created attachment 72861 [details] New crash information added by DrKonqi konqueror (4.8.4 (4.8.4)) on KDE Platform 4.8.4 (4.8.4) using Qt 4.8.1 - What I was doing when the application crash: I run ECMAScript test262 (http://test262.ecmascript.org/) ,Crash when running to Chapter 11. -- Backtrace (Reduced): #7 QString (other=..., this=0xbffe8718) at /usr/include/qt4/QtCore/qstring.h:725 #8 KJSDebugger::DebugDocument::name (this=0x0) at ../../khtml/ecma/debugger/debugdocument.cpp:82 #9 0xb09d0281 in KJSDebugger::DebugWindow::enterContext (this=0xbffe8718, exec=0xbffe8aec, sourceId=271082, lineno=-1073838312, function=0xa38e2760, args=...) at ../../khtml/ecma/debugger/debugwindow.cpp:741 #10 0xb04efce3 in KJS::changeDebugContext (d=KJS::Enter, exec=0xbffe8aec, n=0xfde3260) at /build/buildd/kde4libs-4.8.4a/kjs/bytecode/machine.cpp.in:201 #11 0xb04f1124 in KJS::Machine::runBlock (exec=0xbffe8aec, codeBlock=..., parentExec=0xbffe8f4c) at codes.def:464 Created attachment 72862 [details] New crash information added by DrKonqi konqueror (4.8.4 (4.8.4)) on KDE Platform 4.8.4 (4.8.4) using Qt 4.8.1 - What I was doing when the application crash: I run ECMAScript test262 (http://test262.ecmascript.org/) ,Crash when running to Chapter 11. -- Backtrace (Reduced): #7 QString (other=..., this=0xbffe8718) at /usr/include/qt4/QtCore/qstring.h:725 #8 KJSDebugger::DebugDocument::name (this=0x0) at ../../khtml/ecma/debugger/debugdocument.cpp:82 #9 0xb09d0281 in KJSDebugger::DebugWindow::enterContext (this=0xbffe8718, exec=0xbffe8aec, sourceId=271082, lineno=-1073838312, function=0xa38e2760, args=...) at ../../khtml/ecma/debugger/debugwindow.cpp:741 #10 0xb04efce3 in KJS::changeDebugContext (d=KJS::Enter, exec=0xbffe8aec, n=0xfde3260) at /build/buildd/kde4libs-4.8.4a/kjs/bytecode/machine.cpp.in:201 #11 0xb04f1124 in KJS::Machine::runBlock (exec=0xbffe8aec, codeBlock=..., parentExec=0xbffe8f4c) at codes.def:464 Created attachment 72863 [details] New crash information added by DrKonqi konqueror (4.8.4 (4.8.4)) on KDE Platform 4.8.4 (4.8.4) using Qt 4.8.1 - What I was doing when the application crash: I run ECMAScript test262 (http://test262.ecmascript.org/) ,Crash when running to Chapter 11. -- Backtrace (Reduced): #7 QString (other=..., this=0xbffe8718) at /usr/include/qt4/QtCore/qstring.h:725 #8 KJSDebugger::DebugDocument::name (this=0x0) at ../../khtml/ecma/debugger/debugdocument.cpp:82 #9 0xb09d0281 in KJSDebugger::DebugWindow::enterContext (this=0xbffe8718, exec=0xbffe8aec, sourceId=271082, lineno=-1073838312, function=0xa38e2760, args=...) at ../../khtml/ecma/debugger/debugwindow.cpp:741 #10 0xb04efce3 in KJS::changeDebugContext (d=KJS::Enter, exec=0xbffe8aec, n=0xfde3260) at /build/buildd/kde4libs-4.8.4a/kjs/bytecode/machine.cpp.in:201 #11 0xb04f1124 in KJS::Machine::runBlock (exec=0xbffe8aec, codeBlock=..., parentExec=0xbffe8f4c) at codes.def:464 Thank you for the feedback, setting status to confirmed. *** This bug has been marked as a duplicate of bug 198621 *** Reopening this bug as it is still valid and not a duplicate of 198621 Thank you for the crash report. As it has been a while since this was reported, can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved. I have set the bug status to "needsinfo" pending your response, please change back to "reported" or "resolved/worksforme" when you respond, thank you. (In reply to Justin Zobel from comment #11) > Thank you for the crash report. > > As it has been a while since this was reported, can you please test and > confirm if this issue is still occurring or if this bug report can be marked > as resolved. > > I have set the bug status to "needsinfo" pending your response, please > change back to "reported" or "resolved/worksforme" when you respond, thank > you. Thanks for the notice ! Sorry, due to changes in the environment, I can‘t test whether the problem exists now. I believe these problems should no longer exist since Konqueror's rendering engine changed to QtWebEngine. Ohhh , Sorry , But ... Why can I change the status of a bug that is not submitted by me ? ? ? and Why does the bug I submit become a comment of this issue ? ? ? and Sorry again , I'll reopen it , It will be change by Kris . Dear user, KHTML (and KJS) was a long time more or less unmaintained and got removed in KF6. Please migrate to use a QWebEngine based HTML component. We will do no further fixes or improvements to the KF5 branches of these components beside important security fixes. For security issues, please see: https://kde.org/info/security/ Sorry that we did not fix this issue during the life-time of KHTML. Greetings Christoph Cullmann |