QGIS crashing when using elevation profile

[Lars-Gunnar]

What is the bug or the crash?

QGIS crashes when using Elevation profile

Steps to reproduce the issue

I have not been able to fine a definite way to reproduce the bug, but it happens when interacting with the Elevation Profile, i.e. adding or changing data, appearances etc. The same applies when using the Elevation Profile in Layouts.

Here is a recent crash report:

Python Stack Trace
Windows fatal exception: access violation

Thread 0x000046e4 (most recent call first):

Stack Trace

QgsVectorLayerProfileGenerator::~QgsVectorLayerProfileGenerator :
QgsVectorLayerProfileGenerator::generateProfileForLines :
QgsVectorLayerProfileGenerator::generateProfile :
QgsProfilePlotRenderer::generateProfileStatic :
QgsProfilePlotRenderer::replaceSourceInternal :
QgsProfilePlotRenderer::replaceSourceInternal :
QgsProfilePlotRenderer::startGeneration :
QtConcurrent::ThreadEngineBase::run :
QThreadPoolPrivate::reset :
QThread::start :
BaseThreadInitThunk :
RtlUserThreadStart :

QGIS Info
QGIS Version: 3.32.2-Lima
QGIS code revision: c0b8833
Compiled against Qt: 5.15.3
Running against Qt: 5.15.3
Compiled against GDAL: 3.7.1
Running against GDAL: 3.7.1

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

Versions

QGIS version
3.32.2-Lima
QGIS code revision
c0b8833
Qt version
5.15.3
Python version
3.9.5
GDAL/OGR version
3.7.1
PROJ version
9.2.1
EPSG Registry database version
v10.088 (2023-05-13)
GEOS version
3.12.0-CAPI-1.18.0
SQLite version
3.41.1
PDAL version
2.5.5
PostgreSQL client version
15.2
SpatiaLite version
5.1.0
QWT version
6.1.6
QScintilla2 version
2.13.1
OS version
Windows 10 Version 2009

Active Python plugins
generate_swmm_inp
0.31
GroupStats
2.2.7
ImportEpanetInpFiles
1.6.6
joinmultiplelines
Version 0.4.1
polystrip
3.0.1
profiletool
4.2.6
qgis2web
3.16.0
Serval
3.10.5
WaterNetAnalyzer-master
1.8
db_manager
0.1.20
grassprovider
2.12.99
MetaSearch
0.3.6
processing
2.12.99

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