Odd attribute table behavior after a crash when an undocked attribute table is open

[bkepl]

What is the bug or the crash?

I recently installed 3.44.0-Solothurn and have been very happy with the new labeling features in particular, but there is a behavior that has been present for a long time is peculiar attribute table behavior after a crash when an undocked attribute table is open. This behavior is even more strange in 3.44. Broadly speaking, I like the behavior, until it causes a crash, which I’ll outline below.

This is my two-monitor setup:

Sometime shortly after installing 3.44, QGIS crashed when an attribute table was undocked from the map canvas. The behavior of tables changed and now always open away from the map canvas. Previous versions of QGIS would revert to the expected behavior when opening and immediately closing the program. This does not happen with 3.44; attribute tables now always open away from the map canvas:

I actually prefer this behavior over the standard behavior when selecting docked table in Settings, but I expect it is not intended. Also, crashes occasionally occur when moving tables.

When opening a second table, they sometimes overlap so I don’t see the one below:

I can move them apart…

…but I must take care to not move over the other table or a crash is likely to occur:

Occasionally a crash doesn’t occur, and this is what I will get:

This resulted in a hard crash (no program hang) when closing the visible table.

Occasionally I will get this:

If I’m lucky I can separate the tables without a crash:

Sometimes (usually not) I get a crash when closing one of the tables:

I can usually move a table to the map canvas area:

This is sometimes what I get when opening another table:

I can usually move one over the other to get this, which is normally how tables open:

I can usually move these tables out together:

I closed QGIS with the tables docked to the canvas. The result when re-opening the program and opening an attribute table was odd; the table was hovering over the canvas but not docked:

A second table opened directly over the first:

Trying to move the second table over the first resulted in this:

After a few seconds, this:

When I docked the table to the map canvas, this resulted:

I was able to move the tables together without a crash:

Moving one table out by clicking the button next to the close button on the upper right of the table gave me this:

Clicking the same button on the remaining table got this (sorry for leaving my IrfanView open in the background):

Mousing over the upper edge of the gray area gave the split mouse icon to allow making the gray area smaller, but then I was unable to dock the table there, but it docked to the side:

After this I was able to dock the table at the bottom of the map canvas, but if I close the second table with this gray area displaying, I will often get a hard crash.

These are my settings for tables:

I created a new profile and the behavior remains. These are the table settings:

Steps to reproduce the issue

A QGIS session must crash with an undocked attribute table open. I haven’t tested it, but ending QGIS with the task manager might work.

Versions

QGIS version | 3.44.0-Solothurn -- | -- QGIS code revision | 5d9ba03   Libraries Qt version | 5.15.13 Python version | 3.12.11 GDAL version | 3.11.0 — Eganville PROJ version | 9.6.2 EPSG Registry database version | v12.013 (2025-05-26) GEOS version | 3.13.1-CAPI-1.19.2 SQLite version | 3.46.1 PDAL version | 2.9.0 PostgreSQL client version | 17.3 SpatiaLite version | 5.1.0 QWT version | 6.3.0 QScintilla2 version | 2.14.1 OS version | Windows 11 Version 2009   Active Python plugins AutomaticBackup-master | 1.0 basemaps | 1.3 custom_titlebar | 1.0.0 GeorefExtension | 3.0.8 geo_sim_processing | 1.2.0 ImageServerConnector | 2.1.1 layout_panel-main | 0.3 MapsPrinter | 1.0 mask | 1.11.0 MemoryLayerSaver | 6.0.0 pathfinder | version 1.0.2 pickLayer | 3.9.13 processing_saga_nextgen | 1.0.0 QCopycanvas | 0.7 qdrawEVT | 2.31 qgis_resource_sharing | 1.2.0 QLocklayers | 0.1 QuickRectangleCreator-master | 0.5 StreetView | 3.3 themeselector | 3.3.6 visible_layers | 1.0.2 db_manager | 0.1.20 grassprovider | 2.12.99 processing | 2.12.99

QGIS version
3.44.0-Solothurn
QGIS code revision
5d9ba037df1

Libraries
Qt version
5.15.13
Python version
3.12.11
GDAL version
3.11.0 — Eganville
PROJ version
9.6.2
EPSG Registry database version
v12.013 (2025-05-26)
GEOS version
3.13.1-CAPI-1.19.2
SQLite version
3.46.1
PDAL version
2.9.0
PostgreSQL client version
17.3
SpatiaLite version
5.1.0
QWT version
6.3.0
QScintilla2 version
2.14.1
OS version
Windows 11 Version 2009

Active Python plugins
AutomaticBackup-master
1.0
basemaps
1.3
custom_titlebar
1.0.0
GeorefExtension
3.0.8
geo_sim_processing
1.2.0
ImageServerConnector
2.1.1
layout_panel-main
0.3
MapsPrinter
1.0
mask
1.11.0
MemoryLayerSaver
6.0.0
pathfinder
version 1.0.2
pickLayer
3.9.13
processing_saga_nextgen
1.0.0
QCopycanvas
0.7
qdrawEVT
2.31
qgis_resource_sharing
1.2.0
QLocklayers
0.1
QuickRectangleCreator-master
0.5
StreetView
3.3
themeselector
3.3.6
visible_layers
1.0.2
db_manager
0.1.20
grassprovider
2.12.99
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

[github-actions]

Thanks for reporting, however it looks like you are using an older version of QGIS (version 3.44.0) instead of latest (Version 3.44.1). Your bug could already be resolved in the latest version.
It takes a lot of human effort to triage all the bugs in a project like QGIS, could you please retry with the latest version first?

[bkepl]

The difficulty of moving around tables that I mentioned above could be minimized if the “grabbiness” of moving one table (or pallet) over another were less pronounced, or perhaps focused on the center of the table/pallet moving into.

[bkepl]

Thanks for reporting, however it looks like you are using an older version of QGIS (version 3.44.0) instead of latest (Version 3.44.1). Your bug could already be resolved in the latest version. It takes a lot of human effort to triage all the bugs in a project like QGIS, could you please retry with the latest version first?

I opened QGIS open a couple days ago (I think yesterday, too) and didn’t see a message about a new version being available. I’ll see Monday when I’m back to work.

[bkepl]

I can't find where 3.44.1 is available for download. The only thing I can find is that I can download the QT6 version of 3.44.0 here: [https://ftp.osuosl.org/pub/osgeo/download/qgis/windows/].) I downloaded it and installed it and indeed, the behavior of the attribute tables seems to no longer be an issue, in my brief test, anyway.

There IS another issue that I find bothersome. I noticed that a couple fonts showed up as missing when I opened a project into the QT6 version. I seems QGIS is grouping 5 fonts into a family but the fonts were not created as belonging to the same font family. They SHOULD have been created this way, but weren't, and I don't know what information QGIS uses to group them when I don't find any information QGIS could have used beyond having similar names. At some point I'll see what I can do in FontForge to correctly put the font into a single family (my first attempt failed), but until I successfully do that, I'll have to stick with the QT5 version. Also, a lot of the plugins I depend on haven't been updated to QT6 (not your issue, I know).

Here's a ZIP of the fonts, if you're interested: Highway Gothic fonts.zip