Crash when opening layout page setup (Windows 10)

[dakvid]

User Feedback

Open QGIS. New empty project, new print layout, page setup => crash.
Happens every single time for me no matter what I have open. I created a new user profile and got the exact same behaviour and stack trace.
I checked that Windows Print Spooler was running, as per https://issues.qgis.org/issues/12828

Report Details

Crash ID: ba85ae5ca463ce9cf2ab15fb1cf0c9ad0647603a

Stack Trace

QPageSetupDialog::exec :
QgsLayoutDesignerDialog::pageSetup qgslayoutdesignerdialog.cpp:3702
QMetaObject::activate :
QAction::activate :
QMenu::actionGeometry :
QMenu::actionGeometry :
QMenu::mouseReleaseEvent :
QWidget::event :
QMenu::event :
QApplicationPrivate::notify_helper :
QApplication::notify :
QgsApplication::notify qgsapplication.cpp:418
QCoreApplication::notifyInternal2 :
QApplicationPrivate::sendMouseEvent :
QSizePolicy::QSizePolicy :
QSizePolicy::QSizePolicy :
QApplicationPrivate::notify_helper :
QApplication::notify :
QgsApplication::notify qgsapplication.cpp:418
QCoreApplication::notifyInternal2 :
QGuiApplicationPrivate::processMouseEvent :
QWindowSystemInterface::sendWindowSystemEvents :
QEventDispatcherWin32::processEvents :
UserCallWinProcCheckWow :
DispatchMessageWorker :
QEventDispatcherWin32::processEvents :
qt_plugin_query_metadata :
QEventLoop::exec :
QCoreApplication::exec :
main main.cpp:1598
BaseThreadInitThunk :
RtlUserThreadStart :

QGIS Info
QGIS Version: 3.10.0-A Coru�a
QGIS code revision: 6ffa89e
Compiled against Qt: 5.11.2
Running against Qt: 5.11.2
Compiled against GDAL: 3.0.2
Running against GDAL: 3.0.2

System Info
CPU Type: x86_64
Kernel Type: winnt
Kernel Version: 10.0.18362

[acwalter]

Same/similar experience after upgrading to 3.10.1

User Feedback

Test #1 - open an existing layout
Opened existing project file from a network drive. Layers are from WFS. Opened Layout Manager, Select Show an existing Layout. Layout loads but it is not possible to interact with it and eventually the crash message comes up. This layout was created using 3.10.0

Test #2 - create new blank layout
Creating a new empty layout in the same file. That seems to work fine, added a map window, saved, closed layout and reopened. Changed a few things, saved, closed, opened. Seems good. Then open the saved layout that was created using 3.10.0 and it loads but causes the crash.

Test #3 - Copy layout that was created using 3.10.0
Open layout manager, select the existing layout, copy and name. New copy loads and renders but crashes the same way that the original does.

Test #4 - same file on a linux machine with 3.10.1
Open file, open layout created with 3.10.1 change a few things, save and close, no problems. Open layout created with 3.10.0 and it crashes the same as the windows machine. Dident ger a crash ID but the Date stamp is Fri Dec 27 10:04:43 2019

Test #5 - Same file on a different windows machine
Same behavior as test #4

Report Details

Crash ID: 878842a2b15ac6bbb3476743e02ae773ae50d110

Stack Trace

QRasterPaintEngine::transformChanged :
QPainter::translate :
QGraphicsScene::drawForeground :
QGraphicsScene::dragMoveEvent :
QGraphicsItem::dragMoveEvent :
QGraphicsEffectSource::draw :
QgsLayoutEffect::draw qgslayouteffect.cpp:33
QGraphicsScene::drawItems :
QGraphicsScene::drawItems :
QGraphicsView::paintEvent :
QgsLayoutView::paintEvent qgslayoutview.cpp:1147
QWidget::event :
QFrame::event :
QGraphicsView::viewportEvent :
QCoreApplicationPrivate::sendThroughObjectEventFilters :
QApplicationPrivate::notify_helper :
QApplication::notify :
QgsApplication::notify qgsapplication.cpp:418
QCoreApplication::notifyInternal2 :
QWidgetPrivate::drawWidget :
QWidgetPrivate::paintSiblingsRecursive :
QWidgetPrivate::drawWidget :
QWidgetPrivate::paintSiblingsRecursive :
QWidgetPrivate::drawWidget :
QWidgetPrivate::paintSiblingsRecursive :
QWidgetPrivate::drawWidget :
QWidgetPrivate::paintSiblingsRecursive :
QWidgetPrivate::drawWidget :
QApplication::windowIcon :
QWidgetPrivate::syncBackingStore :
QSizePolicy::QSizePolicy :
QSizePolicy::QSizePolicy :
QApplicationPrivate::notify_helper :
QApplication::notify :
QgsApplication::notify qgsapplication.cpp:418
QCoreApplication::notifyInternal2 :
QGuiApplicationPrivate::processExposeEvent :
QWindowSystemInterface::sendWindowSystemEvents :
QWindowSystemInterface::flushWindowSystemEvents :
UserCallWinProcCheckWow :
DispatchClientMessage :
_fnDWORD :
KiUserCallbackDispatcherContinue :
NtUserDispatchMessage :
DispatchMessageWorker :
QEventDispatcherWin32::processEvents :
qt_plugin_query_metadata :
QEventLoop::exec :
QCoreApplication::exec :
main main.cpp:1598
BaseThreadInitThunk :
RtlUserThreadStart :

QGIS Info
QGIS Version: 3.10.1-A Coru�a
QGIS code revision: ef24c52
Compiled against Qt: 5.11.2
Running against Qt: 5.11.2
Compiled against GDAL: 3.0.2
Running against GDAL: 3.0.2

System Info
CPU Type: x86_64
Kernel Type: winnt
Kernel Version: 10.0.18362

[roya0045]

@acwalter your issue is related to projection, distinct issue than the one reported.

see #32913

[roya0045]

Still valid?

[acwalter]

Problem was solved by resolving projection as suggested.

…

On Wed, Apr 8, 2020, 6:33 PM Alex ***@***.***> wrote: Still valid? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#32949 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA5GQXNOD7DQIUFM56EUPXDRLT3VNANCNFSM4JPARILQ> .

[roya0045]

@acwalter Great!
@dakvid still ocuring?

[acwalter]

It has not occurred after the bad data was removed or updated. I suppose it would be ideal to have error handling for the end-user but it does seem isolated to the projection problem for me.