https://bugs.kde.org/show_bug.cgi?id=434802
Bug ID: 434802
Summary: Marble crashes in "Address details" dialog
Product: marble
Version: unspecified
Platform: Debian stable
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: marble-b...@kde.org
Reporter: johan...@zarl-zierl.at
Target Milestone: ---
Application: marble (2.2.20 (2.3 development version))
Qt Version: 5.15.2
Frameworks Version: 5.78.0
Operating System: Linux 5.10.0-4-amd64 x86_64
Windowing system: X11
Distribution: Debian GNU/Linux bullseye/sid
-- Information about the crash:
When using the "Address details" dialog available via the context-menu on the
map, marble crashes if the dialog stays open too long.
I.e. when one normally uses the dialog and keeps it open for some seconds,
nothing bad happens, but if one keeps the dialog open for some time (maybe
15-20 seconds) and then closes the dialog using the ok button, marble crashes
reproducibly.
The crash also happens in other applications that use marble as a map widget (I
tested with kphotoalbum).
The crash can be reproduced every time.
-- Backtrace:
Application: Marble – Virtueller Globus (marble), signal: Segmentation fault
[KCrash Handler]
#4 QSharedDataPointer<QNetworkRequestPrivate>::QSharedDataPointer (o=...,
this=0x7ffff1ce9e78) at
../../include/QtCore/../../src/corelib/tools/qshareddata.h:96
#5 QNetworkRequest::QNetworkRequest (this=0x7ffff1ce9e78, other=...) at
access/qnetworkrequest.cpp:543
#6 0x00007fd1bca8ab95 in QNetworkReply::request
(this=this@entry=0x7fd1b0007700) at access/qnetworkreply.cpp:557
#7 0x00007fd1bca76e27 in QNetworkAccessManagerPrivate::_q_replyFinished
(this=0x56208e9d26c0, reply=0x7fd1b0007700) at
access/qnetworkaccessmanager.cpp:1704
#8 0x00007fd1bb6a0546 in QtPrivate::QSlotObjectBase::call (a=0x7ffff1ce9f80,
r=0x7fd1b0007700, this=0x56208e9cba60) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#9 doActivate<false> (sender=0x7fd1b0007700, signal_index=10,
argv=0x7ffff1ce9f80, argv@entry=0x0) at kernel/qobject.cpp:3886
#10 0x00007fd1bb6998a0 in QMetaObject::activate
(sender=sender@entry=0x7fd1b0007700, m=m@entry=0x7fd1bcbb4960
<QNetworkReply::staticMetaObject>,
local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x0) at
kernel/qobject.cpp:3946
#11 0x00007fd1bcb53063 in QNetworkReply::finished
(this=this@entry=0x7fd1b0007700) at .moc/moc_qnetworkreply.cpp:404
#12 0x00007fd1bcad28b8 in QNetworkReplyHttpImplPrivate::finished
(this=0x56208e868310) at access/qnetworkreplyhttpimpl.cpp:2280
#13 0x00007fd1bb695f91 in QObject::event (this=0x7fd1b0007700,
e=0x7fd1200f1730) at kernel/qobject.cpp:1314
#14 0x00007fd1bc12b15f in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#15 0x00007fd1bb669f6a in QCoreApplication::notifyInternal2
(receiver=0x7fd1b0007700, event=0x7fd1200f1730) at
kernel/qcoreapplication.cpp:1063
#16 0x00007fd1bb66c9a1 in QCoreApplicationPrivate::sendPostedEvents
(receiver=0x0, event_type=0, data=0x56208d1e21c0) at
kernel/qcoreapplication.cpp:1817
#17 0x00007fd1bb6c1e33 in postEventSourceDispatch (s=0x56208d375540) at
kernel/qeventdispatcher_glib.cpp:277
#18 0x00007fd1b976be6b in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#19 0x00007fd1b976c118 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#20 0x00007fd1b976c1cf in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#21 0x00007fd1bb6c14bf in QEventDispatcherGlib::processEvents
(this=0x56208d376920, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#22 0x00007fd1bb66892b in QEventLoop::exec (this=this@entry=0x7ffff1cea400,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:69
#23 0x00007fd1bb670ba0 in QCoreApplication::exec () at
../../include/QtCore/../../src/corelib/global/qflags.h:121
#24 0x000056208cab311a in main (argc=<optimized out>, argv=<optimized out>) at
./src/apps/marble-kde/kdemain.cpp:447
[Inferior 1 (process 40227) detached]
Reported using DrKonqi
--
You are receiving this mail because:
You are watching all bug changes.
