[Digikam-devel] Context menu crash ?

Andi Clemens andi.clemens at gmx.net
Wed Jul 29 14:47:11 BST 2009


Gilles,

something seems to be wrong with marble integration. digiKam crashes all the 
time now, especially when openStreetMap is used.

Andi

On Wednesday 29 July 2009 12:07:52 Marcel Wiesweg wrote:
> Am Mittwoch, 29. Juli 2009 schrieb Gilles Caulier:
> > Andi,
> >
> > Whe i press on icon view item to show popup menu, digiKam crash :
> >
> > Thread 1 (Thread 0xb453ab10 (LWP 28736)):
> > #4  0xb67a6264 in KCrash::defaultCrashHandler () from
> > /usr/lib/libkdeui.so.5 #5  <signal handler called>
> > #6  0xb544cffc in __dynamic_cast () from /usr/lib/libstdc++.so.6
> > #7  0xb6d4df39 in ?? () from /usr/lib/libmarblewidget.so.4
> > #8  0xa6342bc2 in ?? () from
> > /usr/lib/kde4/plugins/marble/MarbleGeoDataPlugin.so #9  0xa6342ded in ??
> > () from /usr/lib/kde4/plugins/marble/MarbleGeoDataPlugin.so #10
> > 0xa6341f5d in ?? () from
> > /usr/lib/kde4/plugins/marble/MarbleGeoDataPlugin.so #11 0xa63416f6 in ??
> > () from
> > /usr/lib/kde4/plugins/marble/MarbleGeoDataPlugin.so #12 0xb6d636d5 in
> > Marble::LayerManager::renderLayers () from
> > /usr/lib/libmarblewidget.so.4
> > #13 0xb6d2154e in Marble::MarbleModel::paintGlobe () from
> > /usr/lib/libmarblewidget.so.4
> > #14 0xb6d2aeea in ?? () from /usr/lib/libmarblewidget.so.4
> > #15 0xb6d19a77 in Marble::MarbleWidget::paintEvent () from
> > /usr/lib/libmarblewidget.so.4
> > #25 0xb5b29973 in QWidgetPrivate::syncBackingStore () from
> > /usr/lib/libQtGui.so.4
> > #27 0xb5b52ee8 in QApplication::x11ProcessEvent () from
> > /usr/lib/libQtGui.so.4 #28 0xb5b7d714 in ?? () from
> > /usr/lib/libQtGui.so.4 #34 0xb5601903 in QEventLoop::processEvents ()
> > from /usr/lib/libQtCore.so.4 #35 0xb5601d51 in QEventLoop::exec () from
> > /usr/lib/libQtCore.so.4 #36 0xb5f7da53 in QMenu::exec () from
> > /usr/lib/libQtGui.so.4
> > #37 0x082c3801 in Digikam::ContextMenuHelper::exec (this=0xbfe76b38,
> > pos=@0xbfe77438, at=0x0) at
> > /home/gilles/Documents/data/devel/SVN/trunk/graphics/digikam/digikam/cont
> >ex tmenuhelper.cpp:599 #38 0x082f1336 in
> > Digikam::DigikamImageView::showContextMenu
> > (this=0xa34acc0, event=0xbfe77420, info=@0xbfe76bdc)
> >     at
> > /home/gilles/Documents/data/devel/SVN/trunk/graphics/digikam/digikam/digi
> >ka mimageview.cpp:241 #39 0x0831328f in
> > Digikam::ImageCategorizedView::contextMenuEvent
> > (this=0xa34acc0, event=0xbfe77420)
> >     at
> > /home/gilles/Documents/data/devel/SVN/trunk/graphics/digikam/digikam/imag
> >ec ategorizedview.cpp:784 #40 0xb5b323f3 in QWidget::event () from
> > /usr/lib/libQtGui.so.4
> >
> > ...but i'm not sure if bactrace is not corrupted due to marble info
> > there... Can you reproduce ?
>
> Can't reproduce either.
> I would interpret the backtrace so that the context menu is shown and as
> menu.exec() is modal running its own event loop, from which marble receives
> a paint event in which it crashes.
>
> Marcel
> _______________________________________________
> Digikam-devel mailing list
> Digikam-devel at kde.org
> https://mail.kde.org/mailman/listinfo/digikam-devel




More information about the Digikam-devel mailing list