Bug report #18031

QGIS crashed after removing temporary scratch layer

Added by Jadwiga Trojak almost 3 years ago. Updated almost 3 years ago.

Status:Closed
Priority:Normal
Assignee:-
Category:Virtual Layers
Affected QGIS version:master Regression?:No
Operating System:Windows 7 Professional 64bit Easy fix?:No
Pull Request or Patch supplied:No Resolution:not reproducable
Crashes QGIS or corrupts data:No Copied to github as #:25927

Description

User Feedback

QGIS crashed after removing temporary scratch layer

Report Details

Crash ID: f2ad2619a4bfb68157b5e116ce7dc98d4f8cf8cf

Stack Trace

QgsLayoutViewToolAddNodeItem::qt_static_metacall :
QgsLayoutViewToolAddNodeItem::qt_static_metacall :
QItemSelectionModel::qt_static_metacall :
QItemSelectionModel::qt_static_metacall :
QItemSelection::indexes :
QItemSelectionModel::selectedIndexes :
QgsLayoutViewToolAddNodeItem::qt_static_metacall :
QgsLayoutViewToolAddNodeItem::qt_static_metacall :
QgsLayoutViewToolAddNodeItem::qt_static_metacall :
QgsLayoutViewToolAddNodeItem::qt_static_metacall :
QMetaObject::activate :
QAbstractItemModel::endRemoveRows :
QgsLayoutViewToolAddNodeItem::qt_static_metacall :
QgsLayoutViewToolAddNodeItem::qt_static_metacall :
QgsLayoutViewToolAddNodeItem::qt_static_metacall :
QgsLayoutViewToolAddNodeItem::qt_static_metacall :
QMetaObject::activate :
QAbstractItemModel::endRemoveRows :
QSortFilterProxyModel::removeRows :
QSortFilterProxyModel::sortRole :
QSortFilterProxyModel::`default constructor closure' :
QMetaObject::activate :
QAbstractItemModel::beginRemoveRows :
QgsLayoutViewToolAddNodeItem::qt_static_metacall :
QgsLayoutViewToolAddNodeItem::qt_static_metacall :
QgsLayoutViewToolAddNodeItem::qt_static_metacall :
QgsLayoutViewToolAddNodeItem::qt_static_metacall :
QgsLayoutViewToolAddNodeItem::qt_static_metacall :
QMetaObject::activate :
QgsFeatureRequest::setInvalidGeometryCallback :
QgsFeatureRequest::setInvalidGeometryCallback :
QgsFeatureRequest::setInvalidGeometryCallback :
QgsFeatureRequest::setInvalidGeometryCallback :
QgsFeatureRequest::setInvalidGeometryCallback :
QMetaObject::activate :
QObject::~QObject :
QgsFeatureRequest::setInvalidGeometryCallback :
QgsFeatureRequest::setInvalidGeometryCallback :
QgsFeatureRequest::setInvalidGeometryCallback :
QgsFeatureRequest::setInvalidGeometryCallback :
QgsFeatureRequest::setInvalidGeometryCallback :
QgsFeatureRequest::setInvalidGeometryCallback :
QgsFeatureRequest::setInvalidGeometryCallback :
QgsFeatureRequest::setInvalidGeometryCallback :
QObject::event :
QApplicationPrivate::notify_helper :
QApplication::notify :
QgsFeatureRequest::setInvalidGeometryCallback :
QCoreApplication::notifyInternal2 :
QCoreApplicationPrivate::sendPostedEvents :
qt_plugin_query_metadata :
QEventDispatcherWin32::processEvents :
TranslateMessageEx :
TranslateMessage :
QEventDispatcherWin32::processEvents :
qt_plugin_query_metadata :
QEventLoop::exec :
QCoreApplication::exec :
QgisApp::addVectorLayers :
BaseThreadInitThunk :
RtlUserThreadStart :

QGIS Info
QGIS Version: 2.99.0-Master
QGIS code revision: 72ca8d7b9c
Compiled against Qt: 5.9.2
Running against Qt: 5.9.2
Compiled against GDAL: 2.2.3
Running against GDAL: 2.2.3

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

History

#1 Updated by Richard Duivenvoorde almost 3 years ago

  • Status changed from Open to Feedback

Hi, I cannot confirm this issue, neither on Linux nor on Windows10 with current master.

Can you tell the exact steps? (with or without other layers, with or without saving when you delete it etc??)

Can you try this again in a fresh profile, so you start without any plugin?

Or try yourself if you can reproduce this issue on another computer?

If not, I would conclude that this is a local issue, either called by a plugin or the install on that machine

#2 Updated by Jadwiga Trojak almost 3 years ago

Hi, the bug did't repeat after reporting.
Thanks for feedback.
Regards,

#3 Updated by Nyall Dawson almost 3 years ago

  • Resolution set to not reproducable
  • Status changed from Feedback to Closed

Not reproducable, and the attached stack trace uses out of date debugging symbols so cannot be used to assist.

Also available in: Atom PDF