Crash on KML load

[edawn]

What is the bug or the crash?

The app crashes when trying to load a KML file.

Steps to reproduce the issue

Go to "Layer" -> "Add Layer ..." -> "Add Vector Layer ..." and attempt to load the following KML file.

<?xml version="1.0" encoding="UTF-8"?>
<kml xmlns="http://www.opengis.net/kml/2.2"
 xmlns:gx="http://www.google.com/kml/ext/2.2">
<Folder>
  <Placemark>
    <gx:Track>
      <gx:coord>-122.207881 37.371915 156.000000</gx:coord>
      <gx:coord>-122.205712 37.373288 152.000000</gx:coord>
      <gx:coord>-122.204678 37.373939 147.000000</gx:coord>
      <gx:coord>-122.203572 37.374630 142.199997</gx:coord>
      <gx:coord>-122.203451 37.374706 141.800003</gx:coord>
      <gx:coord>-122.203329 37.374780 141.199997</gx:coord>
      <gx:coord>-122.203207 37.374857 140.199997</gx:coord>
    </gx:Track>
  </Placemark>
</Folder>
</kml>

Result:
The App crashes.

Expected result:
The App does not crash. Ideally it also imports the data (like Google Earth does) or at least shows some helpful error message.

Note:
This is the same KML file as the one shown at https://developers.google.com/kml/documentation/kmlreference#simple-example only with the <when> tags removed.

Versions

<style type="text/css"> p, li { white-space: pre-wrap; } </style>

QGIS version	3.34.3-Prizren	QGIS code revision	4737323
Qt version	5.15.3
Python version	3.9.18
GDAL/OGR version	3.8.3
PROJ version	9.3.1
EPSG Registry database version	v10.098 (2023-11-24)
GEOS version	3.12.1-CAPI-1.18.1
SQLite version	3.41.1
PDAL version	2.6.0
PostgreSQL client version	15.2
SpatiaLite version	5.1.0
QWT version	6.1.6
QScintilla2 version	2.13.4
OS version	Windows 10 Version 2009
Active Python plugins
kmltools	3.1.31
QuickOSM	2.2.3
db_manager	0.1.20
grassprovider	2.12.99
MetaSearch	0.3.6
processing	2.12.99

QGIS version 3.34.3-Prizren QGIS code revision [4737323](https://github.com/qgis/QGIS/commit/47373234ac) Qt version 5.15.3 Python version 3.9.18 GDAL/OGR version 3.8.3 PROJ version 9.3.1 EPSG Registry database version v10.098 (2023-11-24) GEOS version 3.12.1-CAPI-1.18.1 SQLite version 3.41.1 PDAL version 2.6.0 PostgreSQL client version 15.2 SpatiaLite version 5.1.0 QWT version 6.1.6 QScintilla2 version 2.13.4 OS version Windows 10 Version 2009

Active Python plugins
kmltools
3.1.31
QuickOSM
2.2.3
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

"Report details" from the crash dialog:

Python Stack Trace
Windows fatal exception: access violation

Thread 0x0000718c (most recent call first):

Stack Trace

CPLODBCDriverInstaller::RemoveDriver :
CPLODBCDriverInstaller::RemoveDriver :
CPLODBCDriverInstaller::RemoveDriver :
CPLODBCDriverInstaller::RemoveDriver :
CPLODBCDriverInstaller::RemoveDriver :
CPLODBCDriverInstaller::RemoveDriver :
CPLODBCDriverInstaller::RemoveDriver :
QgsOgrProviderUtils::querySubLayerList :
QgsTiledSceneRenderer::flags :
QgsProviderRegistry::querySublayers :
QgsProviderSublayerTask::run :
QgsTask::start :
QThreadPoolPrivate::reset :
QThread::start :
BaseThreadInitThunk :
RtlUserThreadStart :

QGIS Info
QGIS Version: 3.34.3-Prizren
QGIS code revision: 4737323
Compiled against Qt: 5.15.3
Running against Qt: 5.15.3
Compiled against GDAL: 3.8.3
Running against GDAL: 3.8.3

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

[rouault]

The crash occurs in the OGR LIBKML driver. Investigating

[rouault]

GDAL upstream fix in OSGeo/gdal#9131