Closed
Description
What is the bug or the crash?
User Feedback
QGIS doesn't start
Report Details
Python Stack Trace
Windows fatal exception: access violation
Current thread 0x00001e44 (most recent call first):
<no Python frame>
Stack Trace
memcpy_avx_ermsb_Intel memcpy_avx_ermsb_aligned.asm:186
QString::replace_helper :
QString::replace :
QString::replace :
QgsSettingsEntryBase::completeKeyPrivate :
QgsSettingsEntryBase::origin :
providerMetadataFactory :
providerMetadataFactory :
QgsDataItem::populate :
providerMetadataFactory :
providerMetadataFactory :
QgsBrowserModel::addProviderRootItem :
QgsBrowserModel::addRootItems :
QgsBrowserModel::initialize :
QgsBrowserWidget::showEvent :
QWidget::event :
QApplicationPrivate::notify_helper :
QApplication::notify :
QgsApplication::notify :
QCoreApplication::notifyInternal2 :
QWidgetPrivate::show_helper :
QWidgetPrivate::setVisible :
QWidget::setVisible :
QWidgetPrivate::showChildren :
QWidgetPrivate::show_helper :
QWidgetPrivate::showChildren :
QWidgetPrivate::show_helper :
QWidgetPrivate::setVisible :
QWidget::setVisible :
QDockWidgetLayout::wmSupportsNativeWindowDeco :
QDockWidgetLayout::wmSupportsNativeWindowDeco :
QTabBarPrivate::isAnimated :
QTabBarPrivate::isAnimated :
QMainWindow::restoreState :
pdal::operator< :
QgisApp::showEvent :
QWidget::event :
QApplicationPrivate::notify_helper :
QApplication::notify :
QgsApplication::notify :
QCoreApplication::notifyInternal2 :
QWidgetPrivate::show_helper :
QWidgetPrivate::setVisible :
QWidget::setVisible :
QgisApp::QgisApp :
main :
BaseThreadInitThunk :
RtlUserThreadStart :
QGIS Info
QGIS Version: 3.40.7-Bratislava
QGIS code revision: 91d544f
Compiled against Qt: 5.15.13
Running against Qt: 5.15.13
Compiled against GDAL: 3.10.3
Running against GDAL: 3.10.3
System Info
CPU Type: x86_64
Kernel Type: winnt
Kernel Version: 10.0.26100
Steps to reproduce the issue
Versions
Supported QGIS version
- I'm running a supported QGIS version according to the roadmap.
New profile
- I tried with a new QGIS profile
Additional context
No response