-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
WMTS/WCS + 3D mapcanvas crash #28800
Comments
Author Name: Roberto Uhlig (@uhliro26) User FeedbackHere a hopefully "better" stack trace from windows with current master. Report DetailsCrash ID: 00cc099c5a349c9d50a4c17af5fc127297a51255 Stack Trace
QGIS Info System Info |
Author Name: Roberto Uhlig (@uhliro26)
|
Author Name: Roberto Uhlig (@uhliro26)
|
Probably the same issue as #26706 |
Redering of WCS layers has been quite inefficient since introduction of multi-threaded rendering in QGIS 2.4: whenever map rendering was starting, copying of WCS provider involved running full initialization of WCS provider which typically does three(!) network requests in the constructor (get capabilities + 2x check to work around some incompatibilities of WCS servers). This was both slow and potentially dangerous because of embedded QEventLoop for the network requests. This is now gone and when WCS provider gets cloned (e.g. when starting map rendering), it just gets copy of data without any extra work. Avoiding embedded QEventLoop fixes a crash in 3D view when loading tiles. Fixes qgis#28800 Fixes qgis#26706
Redering of WCS layers has been quite inefficient since introduction of multi-threaded rendering in QGIS 2.4: whenever map rendering was starting, copying of WCS provider involved running full initialization of WCS provider which typically does three(!) network requests in the constructor (get capabilities + 2x check to work around some incompatibilities of WCS servers). This was both slow and potentially dangerous because of embedded QEventLoop for the network requests. This is now gone and when WCS provider gets cloned (e.g. when starting map rendering), it just gets copy of data without any extra work. Avoiding embedded QEventLoop fixes a crash in 3D view when loading tiles. Fixes #28800 Fixes #26706
Author Name: Richard Duivenvoorde (@rduivenvoorde)
Original Redmine Issue: 20981
Affected QGIS version: 3.5(master)
Redmine category:3d
In current master QGIS crashes when you open the 3D mapcanvas.
This worked earlier, as stated here:
(via Google Translation)
https://translate.google.com/translate?hl=nl&sl=auto&tl=en&u=http%3A%2F%2Fwww.qgis.nl%2F2018%2F03%2F18%2Fje-eerste-3-d-kaart-in-qgis-3-0%2F
To reproduce:
I fail to get a gdb stacktrace, trying to run QGIS via gdb (even with an fresh profile) ends with:
WINDOWS STACKTRACE is:
Crash ID: d220c048a99a358a432a786e0a8c66b7a6dbb108
Stack Trace
QgsWindow3DEngine::trUtf8 :
QgsWindow3DEngine::trUtf8 :
QgsWindow3DEngine::trUtf8 :
QgsWindow3DEngine::trUtf8 :
Qgs3DMapScene::onFrameTriggered :
QgsPhongMaterialSettings::ambient :
Qgs3DMapScene::updateCameraNearFarPlanes :
QgsCameraPose::headingAngle :
QMetaObject::activate :
Qt3DLogic::QFrameAction::triggered :
Qt3DLogic::QFrameAction::onTriggered :
Qt3DLogic::QFrameAction::onTriggered :
QApplicationPrivate::notify_helper :
QApplication::notify :
QgsLayerTreeGroup::updateChildVisibilityMutuallyExclusive :
QCoreApplication::notifyInternal2 :
QCoreApplicationPrivate::sendPostedEvents :
qt_plugin_query_metadata :
QEventDispatcherWin32::processEvents :
DispatchMessageW :
DispatchMessageW :
QEventDispatcherWin32::processEvents :
qt_plugin_query_metadata :
QEventLoop::exec :
dataItem :
dataItem :
dataItem :
dataItem :
dataItem :
dataItem :
dataItem :
QgsLayerTreeGroup::updateChildVisibilityMutuallyExclusive :
QgsLayerTreeGroup::updateChildVisibilityMutuallyExclusive :
QgsLayerTreeGroup::updateChildVisibilityMutuallyExclusive :
QgsLayerTreeGroup::updateChildVisibilityMutuallyExclusive :
QgsLayerTreeGroup::updateChildVisibilityMutuallyExclusive :
QgsLayerTreeGroup::updateChildVisibilityMutuallyExclusive :
QgsTerrainGenerator::typeToString :
QgsTerrainGenerator::typeToString :
QgsDemTerrainGenerator::updateGenerator :
QgsFlatTerrainGenerator::createChunkLoader :
QgsWindow3DEngine::trUtf8 :
QgsWindow3DEngine::trUtf8 :
QgsWindow3DEngine::trUtf8 :
QgsWindow3DEngine::trUtf8 :
QgsWindow3DEngine::trUtf8 :
QMetaObject::activate :
QgsWindow3DEngine::qt_static_metacall :
QgsTerrainGenerator::typeToString :
QgsTerrainGenerator::typeToString :
QgsTerrainGenerator::typeToString :
QgsTerrainGenerator::typeToString :
QMetaObject::activate :
Qgs3DAlgorithms::qt_static_metacall :
QgsTerrainGenerator::typeToString :
QgsTerrainGenerator::typeToString :
QgsTerrainGenerator::typeToString :
QgsTerrainGenerator::typeToString :
QMetaObject::activate :
QgsLayerTreeGroup::updateChildVisibilityMutuallyExclusive :
QgsLayerTreeGroup::updateChildVisibilityMutuallyExclusive :
QgsLayerTreeGroup::updateChildVisibilityMutuallyExclusive :
QgsLayerTreeGroup::updateChildVisibilityMutuallyExclusive :
QgsLayerTreeGroup::updateChildVisibilityMutuallyExclusive :
QMetaObject::activate :
QgsLayerTreeGroup::updateChildVisibilityMutuallyExclusive :
QgsLayerTreeGroup::updateChildVisibilityMutuallyExclusive :
QgsLayerTreeGroup::updateChildVisibilityMutuallyExclusive :
QgsLayerTreeGroup::updateChildVisibilityMutuallyExclusive :
QgsLayerTreeGroup::updateChildVisibilityMutuallyExclusive :
QMetaObject::activate :
QFutureWatcherBase::event :
QApplicationPrivate::notify_helper :
QApplication::notify :
QgsLayerTreeGroup::updateChildVisibilityMutuallyExclusive :
QCoreApplication::notifyInternal2 :
QCoreApplicationPrivate::sendPostedEvents :
qt_plugin_query_metadata :
QEventDispatcherWin32::processEvents :
DispatchMessageW :
DispatchMessageW :
QEventDispatcherWin32::processEvents :
qt_plugin_query_metadata :
QEventLoop::exec :
QCoreApplication::exec :
QgisApp::actionLayerSaveAs :
BaseThreadInitThunk :
RtlUserThreadStart :
The text was updated successfully, but these errors were encountered: