Summary: | Crash when using map view inside of digikam | ||
---|---|---|---|
Product: | [Applications] digikam | Reporter: | Francesco Riosa <vivo75+kde> |
Component: | Geolocation-GoogleMaps | Assignee: | Digikam Developers <digikam-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | caulier.gilles, mike, vivo75+kde |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | 6.0.0 | |
Sentry Crash Report: | |||
Attachments: |
New crash information added by DrKonqi
New crash information added by DrKonqi |
Description
Francesco Riosa
2011-06-27 19:46:25 UTC
trying to move this to konqueror/kjs Created attachment 61384 [details]
New crash information added by DrKonqi
digikam (2.0.0-rc) on KDE Platform 4.6.4 (4.6.4) using Qt 4.7.3
same as the above, different location ...
-- Backtrace (Reduced):
#6 KJS::JSValue::type (this=<value optimized out>) at /usr/src/debug/kde-base/kdelibs-4.6.4-r1/kdelibs-4.6.4/kjs/value.h:452
#7 0x00007fa04f03407e in KJS::equal (exec=0x7fffca7c5160, v1=0x80, v2=0x3) at /usr/src/debug/kde-base/kdelibs-4.6.4-r1/kdelibs-4.6.4/kjs/operations.cpp:116
#8 0x00007fa04f06a283 in KJS::Machine::runBlock (exec=0x7fffca7c5160, codeBlock=..., parentExec=0x7fffca7c5910) at codes.def:1071
#9 0x00007fa04f04ca1a in KJS::FunctionImp::callAsFunction (this=<value optimized out>, exec=0x7fffca7c5910, thisObj=<value optimized out>, args=...) at /usr/src/debug/kde-base/kdelibs-4.6.4-r1/kdelibs-4.6.4/kjs/function.cpp:172
#10 0x00007fa04f06ac67 in KJS::Machine::runBlock (exec=0x7fffca7c5910, codeBlock=..., parentExec=0x7fffca7c60c0) at codes.def:1223
Created attachment 61385 [details]
New crash information added by DrKonqi
digikam (2.0.0-rc) on KDE Platform 4.6.4 (4.6.4) using Qt 4.7.3
the problem is exclusively related to the use of google maps inside marble, other backend does not have this problem
-- Backtrace (Reduced):
#6 KJS::JSValue::type (this=<value optimized out>) at /usr/src/debug/kde-base/kdelibs-4.6.4-r1/kdelibs-4.6.4/kjs/value.h:452
#7 0x00007fcf3ebf307e in KJS::equal (exec=0x7fffd058b020, v1=0x80, v2=0x3) at /usr/src/debug/kde-base/kdelibs-4.6.4-r1/kdelibs-4.6.4/kjs/operations.cpp:116
#8 0x00007fcf3ec29283 in KJS::Machine::runBlock (exec=0x7fffd058b020, codeBlock=..., parentExec=0x7fffd058b7d0) at codes.def:1071
#9 0x00007fcf3ec0ba1a in KJS::FunctionImp::callAsFunction (this=<value optimized out>, exec=0x7fffd058b7d0, thisObj=<value optimized out>, args=...) at /usr/src/debug/kde-base/kdelibs-4.6.4-r1/kdelibs-4.6.4/kjs/function.cpp:172
#10 0x00007fcf3ec29c67 in KJS::Machine::runBlock (exec=0x7fffd058b7d0, codeBlock=..., parentExec=0x7fffd058bf80) at codes.def:1223
Actually, we do not use KHTML inside Marble. We use either Marble or KHTML, they are both displayed in a KMapWidget ;-) Still, the crash could be due to the interaction of KMapWidget with KHTML... Michael Since digiKam do not use KHTML with Map view since a while, this problem is not more reproducible. |