"double free or corruption" and "corrupted double-linked list" debug messages

[rduivenvoorde]

What is the bug or the crash?

I hope others can see this too/reproduce?

Having a self compiled debug version I see this "double free or corruption" and "corrupted double-linked list" debug messages when I close QGIS:

src/core/browser/qgsdataitem.cpp:69 : (~QgsDataItem) [0ms] mName = User Bookmarks mPath = bookmarks:user bookmarks mChildren.size() = 0
src/core/browser/qgsdataitem.cpp:69 : (~QgsDataItem) [0ms] mName = Mapzen Global Terrain mPath = xyz:/Mapzen Global Terrain mChildren.size() = 0
src/core/browser/qgsdataitem.cpp:69 : (~QgsDataItem) [0ms] mName = OpenStreetMap mPath = xyz:/OpenStreetMap mChildren.size() = 0
src/providers/postgres/qgspostgresconnpool.cpp:42 : (~QgsPostgresConnPool) [2ms] Entering.
src/providers/postgres/qgspostgresconnpool.cpp:42 : (~QgsPostgresConnPool) [0ms] Leaving.
double free or corruption (!prev)
/home/richard/bin/qgis: line 23: 48059 Aborted                 (core dumped) /home/richard/bin/qgis_/master/debug/bin/qgis "$@

src/core/browser/qgsdataitem.cpp:69 : (~QgsDataItem) [0ms] mName = User Bookmarks mPath = bookmarks:user bookmarks mChildren.size() = 0
src/core/browser/qgsdataitem.cpp:69 : (~QgsDataItem) [0ms] mName = Mapzen Global Terrain mPath = xyz:/Mapzen Global Terrain mChildren.size() = 0
src/core/browser/qgsdataitem.cpp:69 : (~QgsDataItem) [0ms] mName = OpenStreetMap mPath = xyz:/OpenStreetMap mChildren.size() = 0
corrupted double-linked list

At first I thought it was postgres related, but even without connections and or a free/clean/new profile I get these...

Steps to reproduce the issue

Start QGIS from commandline with new profile

qgis --profile xxxx

Shut it down and see:

src/core/browser/qgsdataitem.cpp:69 : (~QgsDataItem) [0ms] mName = Mapzen Global Terrain mPath = xyz:/Mapzen Global Terrain mChildren.size() = 0
src/core/browser/qgsdataitem.cpp:69 : (~QgsDataItem) [0ms] mName = OpenStreetMap mPath = xyz:/OpenStreetMap mChildren.size() = 0
corrupted double-linked list
/home/richard/bin/qgis: line 23: 48688 Aborted                 (core dumped) /home/richard/bin/qgis_/master/debug/bin/qgis "$@"

Versions

QGIS version	3.25.0-Master	QGIS code revision	65ed3c5
Qt version	5.15.2
Python version	3.9.10
GDAL/OGR version	3.4.1
PROJ version	8.2.1
EPSG Registry database version	v10.041 (2021-12-03)
GEOS version	3.10.2-CAPI-1.16.0
SQLite version	3.37.2
PostgreSQL client version	unknown
SpatiaLite version	5.0.1
QWT version	6.1.4
QScintilla2 version	2.11.6
OS version	Debian GNU/Linux bookworm/sid
This copy of QGIS writes debugging output.
Active Python plugins
sagaprovider	2.12.99
MetaSearch	0.3.6
processing	2.12.99
grassprovider	2.12.99
db_manager	0.1.20

QGIS version 3.25.0-Master QGIS code revision [65ed3c5](https://github.com/qgis/QGIS/commit/65ed3c5ee4c) Qt version 5.15.2 Python version 3.9.10 GDAL/OGR version 3.4.1 PROJ version 8.2.1 EPSG Registry database version v10.041 (2021-12-03) GEOS version 3.10.2-CAPI-1.16.0 SQLite version 3.37.2 PostgreSQL client version unknown SpatiaLite version 5.0.1 QWT version 6.1.4 QScintilla2 version 2.11.6 OS version Debian GNU/Linux bookworm/sid

This copy of QGIS writes debugging output.

Active Python plugins
sagaprovider
2.12.99
MetaSearch
0.3.6
processing
2.12.99
grassprovider
2.12.99
db_manager
0.1.20

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

[rduivenvoorde]

Not sure if I'm the only one seeing this and/or it is helpfull, but having a QtCreator session here, it ends with

[nyalldawson]

This is a pretty generic issue usually signifying something very bad in your local build. Try:

1. Clearing out the build folder entirely
2. Clear ccache cache (if installed)
3. Rebuild from scratch

[rduivenvoorde]

Ah, Thanks Nyall, closing this one then. Sorry for the fuzz

[rduivenvoorde]

FYI: you were right: new build folder/configure, ccache clean, install clean and new build: NO problem anymore. Thanks

[strk]

I'm experiencing this too, and have reported in #48608 -- I saw this happening in CI so I doubt a clean build is the solution, unless CI is also having dirty builds ?