Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Crash on Menu.Layer.Properites command #58775

Closed
2 tasks
EmAlvin opened this issue Sep 17, 2024 · 1 comment
Closed
2 tasks

Crash on Menu.Layer.Properites command #58775

EmAlvin opened this issue Sep 17, 2024 · 1 comment
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! Crash/Data Corruption

Comments

@EmAlvin
Copy link

EmAlvin commented Sep 17, 2024

What is the bug or the crash?

User Feedback

Well, before this crash I updated the QField plugin (QGis notified me about an available upgrade of that plugin); then I opened a recent simple project (that I had previously synched with QField back and forth in the past days); then I walked around the map of the project; then I deleted 2 points on a shapefile points layer; QGist warned me I was not in edit mode; I entered edit mode and deleted those 2 points. Finally I opened the layer properties page from the menu bar. I actually tried to do so because, after a while, QGis crashed asking me to report what I am writing. Have luck!

Report Details

Python Stack Trace

Windows fatal exception: access violation

Current thread 0x00001228 (most recent call first):
  <no Python frame>

Stack Trace


QObject::parent :
QLayout::addChildWidget :
QStackedLayout::insertWidget :
QgsOptionsDialogBase::addPage :
QgsLayerPropertiesDialog::addPropertiesPageFactory :
QgisApp::showLayerProperties :
QgisApp::layerProperties :
QObject::qt_static_metacall :
QAction::activate :
QMenu::actionGeometry :
QMenu::actionGeometry :
QMenu::mouseReleaseEvent :
QWidget::event :
QMenu::event :
QApplicationPrivate::notify_helper :
QApplication::notify :
QgsApplication::notify :
QCoreApplication::notifyInternal2 :
QApplicationPrivate::sendMouseEvent :
QSizePolicy::QSizePolicy :
QSizePolicy::QSizePolicy :
QApplicationPrivate::notify_helper :
QApplication::notify :
QgsApplication::notify :
QCoreApplication::notifyInternal2 :
QGuiApplicationPrivate::processMouseEvent :
QWindowSystemInterface::sendWindowSystemEvents :
QEventDispatcherWin32::processEvents :
qt_plugin_query_metadata :
QEventLoop::exec :
QCoreApplication::exec :
main :
BaseThreadInitThunk :
RtlUserThreadStart :

QGIS Info
QGIS Version: 3.34.10-Prizren
QGIS code revision: 113de9e
Compiled against Qt: 5.15.13
Running against Qt: 5.15.13
Compiled against GDAL: 3.9.2
Running against GDAL: 3.9.2

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

Steps to reproduce the issue

menu -> Layer -> Properties

Versions

QGIS Version: 3.34.10-Prizren
QGIS code revision: 113de9e
Compiled against Qt: 5.15.13
Running against Qt: 5.15.13
Compiled against GDAL: 3.9.2
Running against GDAL: 3.9.2

Supported QGIS version

  • I'm running a supported QGIS version according to the roadmap.

New profile

Additional context

No response

@EmAlvin EmAlvin added the Bug Either a bug report, or a bug fix. Let's hope for the latter! label Sep 17, 2024
@nyalldawson
Copy link
Collaborator

If reproducible, this is a bug in the QField plugin and needs to be reported to the QField authors

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! Crash/Data Corruption
Projects
None yet
Development

No branches or pull requests

3 participants