New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
setting labeling font size to less than 0.3 freezes qgis with meters units #57336
Comments
Tested in QGIS 3.37 on windows 11 with a font size of 0.1 meter at scale and no issue. Even at 0.001 there were no issues. |
@roya0045 I have tested on two separate PC with Debian OS. Could it be OS dependent? |
That's a possiblity |
@faridcher, thanks for reporting. Please provide a simple project and layer with which the issue occurs on your system. |
@agiudiceandrea You may create a new project, a new geopackage layer with a Text field for labeing and digitize a few features Software Information:
thank you |
That information was already in the issue description. There is a good reason to ask for a sample project and data because many configurations could be different and trigger the issue. Maybe it's just me but without sample data and project I won't spend a minute of my time trying to reproduce this issue. |
What is the bug or the crash?
In a new project, add a vector layer from a geopackage and label with a Text field. Then try to set the font Size to 0.3 when units is either "Map Units" (my crs is in meters) or "Meters at Scale". It should work fine if it is set to 0.4. But as soon as I enter a value equal or less than 0.3 QGIS freezes! I either have to wait for 5 min or force close QGIS. If I wait for the GUI to set it to 0.3, once I want to show the Properties page of the layer, it then freezes QGIS.
Steps to reproduce the issue
create a new project and a new geopackage with vector layer and a Text field. add the layer to the map and label the Text field and set the font Size to 0.3 and the units to Meters at Scale
Versions
3.34.6-Prizren
Supported QGIS version
New profile
Additional context
No response
The text was updated successfully, but these errors were encountered: