QGIS crashes during map re-rendering after CRS switch

[qgib]

Author Name: Andrii Zaiev (Andrii Zaiev)
Original Redmine Issue: 21857
Affected QGIS version: 3.6.1
Redmine category:projection_support

---

User Feedback

I'm using clean installment of QGIS (version 3.6.1) and base QGIS project from Natural Earth pack (http://naciscdn.org/naturalearth/packages/Natural_Earth_quick_start.zip), one with v3 suffix.
Crash has happened when I have switched map to SWEREF99 TM (for both EPSG:3006 and EPSG:3584) CRS from WGS84. I have checked few other CRS's, for them crash doesn't occur.

Issue is reproducible only when any layer group starting with z5 is visible.

Report Details

Crash ID: cb7d3eaf1ce486bd294612c0284f7b43a1b3286b

Stack Trace

pal::GeomFunction::reorderPolygon :
pal::FeaturePart::extractCoords :
pal::FeaturePart::FeaturePart :
pal::Layer::registerFeature :
QgsLabelingEngine::processProvider :
QgsLabelingEngine::processProvider :
QgsLabelingEngine::run :
QgsMapRendererJob::drawLabeling :
QgsMapRendererParallelJob::renderLabelsStatic :
QgsMapRendererJob::renderingTime :
QThreadPoolPrivate::reset :
QThread::start :
BaseThreadInitThunk :
RtlUserThreadStart :

QGIS Info
QGIS Version: 3.6.1-Noosa
QGIS code revision: 2468226
Compiled against Qt: 5.11.2
Running against Qt: 5.11.2
Compiled against GDAL: 2.4.1
Running against GDAL: 2.4.1

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

[qgib]

Author Name: Giovanni Manghi (@gioman)

---

Also confirmed on Linux.

---

• operating_system was changed from Windows 10, version 1803 to
• priority_id was changed from Normal to High

[AlisterH]

when I have switched map to SWEREF99 TM (for both EPSG:3006 and EPSG:3584)

Did you by any chance mean EPSG:103584 rather than EPSG:3584?
In any case, I just wanted to add that trying to reproduce it in 3.10.1, I zoomed into an area that was valid for the CRS before switching, and it didn't crash when I switched. But it did crash after I zoomed out, so I wonder if the crash occurs when trying to zoom out past the valid extents of a CRS.

[rouault]

I cannot reproduce with latest 3.10 nor master. In the log I see an number of GEOS exceptions about invalid geometries probably due to reprojection. The pal compoment where the crash occured has received a number of fixes, so I presume something has fixed the issue