| Summary: | Marble crashes sometime when using the vector map theme | ||
|---|---|---|---|
| Product: | [Applications] marble | Reporter: | Bernhard Beschow <shentey> |
| Component: | general | Assignee: | marble-bugs |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | crash | CC: | 2012gdwu+k2, alex.danila.web, bernhardu, idiot, kde, kkremitzki, m_louis30, vamp898 |
| Priority: | HI | Keywords: | drkonqi |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Arch Linux | ||
| 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 New crash information added by DrKonqi New crash information added by DrKonqi |
||
|
Description
Bernhard Beschow
2017-04-17 18:13:51 UTC
Created attachment 107255 [details]
New crash information added by DrKonqi
marble (2.2.1 (stable release)) using Qt 5.9.1
- What I was doing when the application crashed:
I was trying to get routing using the vector map.
-- Backtrace (Reduced):
#6 0x00007f4cb38357e9 in QPixmap::size (this=this@entry=0x56749e8) at image/qpixmap.cpp:532
#7 0x00007f4cb5d26ab8 in Marble::VisiblePlacemark::symbolRect (this=this@entry=0x5674950) at /workspace/build/src/lib/marble/VisiblePlacemark.cpp:171
#8 0x00007f4cb5d28a38 in Marble::PlacemarkLayout::hasPlacemarkAt (this=0x1dad1a8, pos=...) at /workspace/build/src/lib/marble/PlacemarkLayout.cpp:550
#9 0x00007f4cb5c39549 in Marble::PlacemarkLayer::hasPlacemarkAt (this=<optimized out>, pos=...) at /workspace/build/src/lib/marble/layers/PlacemarkLayer.cpp:204
#10 0x00007f4cb5c7513c in Marble::MarbleMap::hasFeatureAt (this=0x1d798a0, position=...) at /workspace/build/src/lib/marble/MarbleMap.cpp:482
Created attachment 111407 [details]
New crash information added by DrKonqi
marble (2.2.20 (2.3 development version)) using Qt 5.9.4
- What I was doing when the application crashed:
Switched to vector theme, then attempted to download region with "visible region" option. The view position is from less than 1km altitude.
-- Backtrace (Reduced):
#6 0x00007fcc04a3103b in QPixmap::size() const () at /lib64/libQt5Gui.so.5
#7 0x00007fcc0c723208 in Marble::VisiblePlacemark::symbolRect() const () at /lib64/libmarblewidget-qt5.so.28
#8 0x00007fcc0c7250fb in Marble::PlacemarkLayout::hasPlacemarkAt(QPoint const&) () at /lib64/libmarblewidget-qt5.so.28
#9 0x00007fcc0c66ec6a in Marble::MarbleMap::hasFeatureAt(QPoint const&) const () at /lib64/libmarblewidget-qt5.so.28
#10 0x00007fcc0c6bb5b1 in Marble::MarbleDefaultInputHandler::adjustCursorShape(QPoint const&, QPoint const&) () at /lib64/libmarblewidget-qt5.so.28
*** Bug 387731 has been marked as a duplicate of this bug. *** *** Bug 388107 has been marked as a duplicate of this bug. *** *** Bug 392296 has been marked as a duplicate of this bug. *** *** Bug 393442 has been marked as a duplicate of this bug. *** *** Bug 393711 has been marked as a duplicate of this bug. *** *** Bug 394045 has been marked as a duplicate of this bug. *** Created attachment 114231 [details]
New crash information added by DrKonqi
marble (2.2.20 (2.3 development version)) using Qt 5.11.1
- What I was doing when the application crashed:
Zooming while using the OSM vector theme.
-- Backtrace (Reduced):
#6 0x00007f7f9790710b in QPixmap::size() const () at /usr/lib64/libQt5Gui.so.5
#7 0x00007f7f9abc6808 in Marble::VisiblePlacemark::symbolRect() const (this=this@entry=0x561c6df6ff20) at /usr/src/debug/marble-18.04.3-1.1.x86_64/src/lib/marble/VisiblePlacemark.cpp:171
#8 0x00007f7f9abc83c3 in Marble::PlacemarkLayout::hasPlacemarkAt(QPoint const&) (this=0x561c6459bbf8, pos=...) at /usr/include/qt5/QtCore/qarraydata.h:143
#9 0x00007f7f9aadebf9 in Marble::PlacemarkLayer::hasPlacemarkAt(QPoint const&) (this=<optimized out>, pos=...) at /usr/src/debug/marble-18.04.3-1.1.x86_64/src/lib/marble/layers/PlacemarkLayer.cpp:218
#10 0x00007f7f9ab176da in Marble::MarbleMap::hasFeatureAt(QPoint const&) const (this=0x561c64573280, position=...) at /usr/src/debug/marble-18.04.3-1.1.x86_64/src/lib/marble/MarbleMap.cpp:483
Created attachment 114232 [details]
New crash information added by DrKonqi
marble (2.2.20 (2.3 development version)) using Qt 5.11.1
- What I was doing when the application crashed:
Zooming while using the OSM vector theme.
-- Backtrace (Reduced):
#6 0x00007f7f9790710b in QPixmap::size() const () at /usr/lib64/libQt5Gui.so.5
#7 0x00007f7f9abc6808 in Marble::VisiblePlacemark::symbolRect() const (this=this@entry=0x561c6df6ff20) at /usr/src/debug/marble-18.04.3-1.1.x86_64/src/lib/marble/VisiblePlacemark.cpp:171
#8 0x00007f7f9abc83c3 in Marble::PlacemarkLayout::hasPlacemarkAt(QPoint const&) (this=0x561c6459bbf8, pos=...) at /usr/include/qt5/QtCore/qarraydata.h:143
#9 0x00007f7f9aadebf9 in Marble::PlacemarkLayer::hasPlacemarkAt(QPoint const&) (this=<optimized out>, pos=...) at /usr/src/debug/marble-18.04.3-1.1.x86_64/src/lib/marble/layers/PlacemarkLayer.cpp:218
#10 0x00007f7f9ab176da in Marble::MarbleMap::hasFeatureAt(QPoint const&) const (this=0x561c64573280, position=...) at /usr/src/debug/marble-18.04.3-1.1.x86_64/src/lib/marble/MarbleMap.cpp:483
*** Bug 401503 has been marked as a duplicate of this bug. *** Hello, hit this crash at 2018-04-13 in current Debian Buster too, with: marble 4:17.08.3-3.1 libqt5gui5 5.11.3+dfsg1-1 Could not reproduce it later again. Was moving the mouse, maybe scrolling, while marble was loading Vektor-OSM data over a slow mobile connection. Thread 1 (Thread 0x7fc1489ed940 (LWP 5283)): [KCrash Handler] #6 0x00007fc15317327b in QPixmap::size() const () at /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #7 0x00007fc154698748 in () at /usr/lib/x86_64-linux-gnu/libmarblewidget-qt5.so.28 #8 0x00007fc15469a303 in () at /usr/lib/x86_64-linux-gnu/libmarblewidget-qt5.so.28 #9 0x00007fc1545e96ca in Marble::MarbleMap::hasFeatureAt(QPoint const&) const () at /usr/lib/x86_64-linux-gnu/libmarblewidget-qt5.so.28 #10 0x00007fc1546339dc in Marble::MarbleDefaultInputHandler::adjustCursorShape(QPoint const&, QPoint const&) () at /usr/lib/x86_64-linux-gnu/libmarblewidget-qt5.so.28 #11 0x00007fc154634fba in Marble::MarbleDefaultInputHandler::handleMouseEvent(QMouseEvent*) () at /usr/lib/x86_64-linux-gnu/libmarblewidget-qt5.so.28 ... Created attachment 131170 [details]
New crash information added by DrKonqi
marble (2.2.20 (2.3 development version)) using Qt 5.14.2
- What I was doing when the application crashed:
Panning/dragging the map while it was loading, this time with the regula tile map.
-- Backtrace (Reduced):
#4 0x00007f2bc41731cb in QPixmap::size() const () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#5 0x00007f2bc57a8de9 in Marble::VisiblePlacemark::symbolRect (this=this@entry=0x55e6d506ecf0) at ./src/lib/marble/VisiblePlacemark.cpp:172
#6 0x00007f2bc57aabab in Marble::PlacemarkLayout::hasPlacemarkAt (this=0x55e6cd96a258, pos=...) at ./src/lib/marble/PlacemarkLayout.cpp:555
#7 0x00007f2bc56ea4e9 in Marble::PlacemarkLayer::hasPlacemarkAt (this=<optimized out>, pos=...) at ./src/lib/marble/layers/PlacemarkLayer.cpp:218
#8 0x00007f2bc5717d0b in Marble::MarbleMap::hasFeatureAt (this=0x55e6cd9075e0, position=...) at ./src/lib/marble/MarbleMap.cpp:483
Thank you for reporting this crash in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the crash with a recent software version? If you can reproduce the issue, please change the status to "CONFIRMED" when replying. Thank you! Could not reproduce using Marble 22.08.1 from Flathub. Tried navigating, zooming in and out several times, getting directions. Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |