| Summary: | Crash when closing 2.0.0 beta 1 | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | Julien Narboux <Julien> |
| Component: | Geolocation-Marble | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | caulier.gilles, Julien, kde, mike |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | 2.0.0 | |
| Sentry Crash Report: | |||
| Attachments: |
New crash information added by DrKonqi
Check whether backends are ready New crash information added by DrKonqi |
||
|
Description
Julien Narboux
2011-01-04 13:17:04 UTC
It's probably marble stuff... Michael ? Gilles Caulier Created attachment 55550 [details]
New crash information added by DrKonqi
digikam (2.0.0-beta1) on KDE Platform 4.5.1 (KDE 4.5.1) using Qt 4.7.0
- What I was doing when the application crashed:
closing digikam again. Here is another trace.
-- Backtrace (Reduced):
#7 Marble::MarbleWidget::centerLongitude (this=0x0) at ../../../../marble/src/lib/MarbleWidget.cpp:768
#8 0x00464183 in KMap::BackendMarble::getCenter (this=0x9d6c4f0) at /home/jnarboux/digikam-2.0.0-beta1/extra/libkmap/libkmap/backend-marble.cpp:276
#9 0x004436c1 in KMap::KMapWidget::getCenter (this=0x9d63c78) at /home/jnarboux/digikam-2.0.0-beta1/extra/libkmap/libkmap/kmap_widget.cpp:560
#10 0x00443acc in KMap::KMapWidget::saveSettingsToGroup (this=0x9d63c78, group=0xbfe1ce58) at /home/jnarboux/digikam-2.0.0-beta1/extra/libkmap/libkmap/kmap_widget.cpp:620
#11 0x081a9b6e in Digikam::GPSSearchView::doSaveState (this=0x9d63680) at /home/jnarboux/digikam-2.0.0-beta1/core/utilities/gpssearch/gpssearchview.cpp:311
Julien can you test with this patch ?
Index: extra/libkmap/libkmap/kmap_widget.cpp
===================================================================
--- extra/libkmap/libkmap/kmap_widget.cpp (révision 1211669)
+++ extra/libkmap/libkmap/kmap_widget.cpp (copie de travail)
@@ -613,6 +613,9 @@
if (!group)
return;
+ if (!d->marbleWidget)
+ return;
+
if (!d->currentBackendName.isEmpty())
{
group->writeEntry("Backend", d->currentBackendName);
hum forget this one :/ i can't reproduce but what about this patch ?
(it compiles this time :) )
Index: extra/libkmap/libkmap/kmap_widget.cpp
===================================================================
--- extra/libkmap/libkmap/kmap_widget.cpp (révision 1211669)
+++ extra/libkmap/libkmap/kmap_widget.cpp (copie de travail)
@@ -613,6 +613,10 @@
if (!group)
return;
+
+ if (!d->currentBackendReady)
+ return;
+
if (!d->currentBackendName.isEmpty())
{
group->writeEntry("Backend", d->currentBackendName);
SVN commit 1211735 by mghansen: Better checks for ready backends. CCBUG: 262067 M +4 -3 backend-googlemaps.cpp M +8 -3 backend-marble.cpp M +44 -25 kmap_widget.cpp M +3 -2 kmap_widget.h M +2 -2 map-backend.h WebSVN link: http://websvn.kde.org/?view=rev&revision=1211735 Created attachment 55579 [details]
Check whether backends are ready
Hi Julien,
could you please test again with this patch? I also applied it to SVN, in case you use that.
Michael
Created attachment 55599 [details]
New crash information added by DrKonqi
digikam (2.0.0-beta1 (rev.: 1211962)) on KDE Platform 4.5.1 (KDE 4.5.1) using Qt 4.7.0
Here is another trace using current svn. The crash occured while drawing a selection in the map view.
Julien
-- Backtrace (Reduced):
#10 0x0147f305 in __libc_message (do_abort=2, fmt=0x1557280 "*** glibc detected *** %s: %s: 0x%s ***\n") at ../sysdeps/unix/sysv/linux/libc_fatal.c:189
#11 0x01489501 in malloc_printerr (action=<value optimized out>, str=0x6 <Address 0x6 out of bounds>, ptr=0xd351348) at malloc.c:6283
#12 0x0148c679 in _int_malloc (av=<value optimized out>, bytes=<value optimized out>) at malloc.c:4308
#13 0x0148df33 in __libc_malloc (bytes=104) at malloc.c:3660
[...]
#15 0x031e571e in QBrush::init (this=0xd37a288, color=..., style=Qt::SolidPattern) at painting/qbrush.cpp:407
Hi Julien, your new report looks like a different issue, could you please re-file it as a new bug? Did the patch fix the other problem about the crash at shutdown that you reported? Thanks, Michael I can not reproduce the crash at shutdown. I hope it is fixed. Let's close the bug and we will see. Thanks for the quick fix. Julien On 01/05/2011 01:06 PM, Julien Narboux wrote:
> Thanks for the quick fix.
Thanks for extensive testing ;-)
Michael
|