Bug report #15427
QGIS rendering freaks out loading qml + shp when OTF disabled
|Affected QGIS version:||master_2||Regression?:||No|
|Operating System:||Easy fix?:||No|
|Pull Request or Patch supplied:||No||Resolution:||end of life|
|Crashes QGIS or corrupts data:||No||Copied to github as #:||23353|
Tested here on Debian, 2.14, 2.16 and master_2
Downloades some OSM shapes from Geofabrik, to style it nice with the qml files from:
But as soon as I try to load the qml file (which are looking into the xml created using QGIS 2.2)... for the roads, QGIS freaks out.
cpu goes to 100%
Looks like a rendering problem/artefact. If somebody is aware what I can do to make the QML work, that would be cool...
I tried to create some lines, but even with 2 lines in a memory layer it goes awry
I attach a screendump as it goes wild.
I add the shapefile + qml in a zip to the issue
#1 Updated by Richard Duivenvoorde almost 4 years ago
Ok, some further investigating...
At first on an other computer it seemed ok: BUT!! that computer did have OTF enabled.
So: better test:
1) first create a fresh project eg epsg:3857 WITH OTF ON!
2) Load shape and qml: OK
3) now disable OTF
4) either freaking rendering artifacts or grey block
Same goes if you start with an new project without OTF
#3 Updated by Richard Duivenvoorde almost 4 years ago
Ok... it is also related to epsg:4326 !
It is actually ok if you have a project in epsg:3857, BUT it goes wrong if you go to epsg:4326 !!
Does this mean it is data related? No, because I also have it if I load a minimal memory layer and add a type-column to it (used in the styles)
#5 Updated by Richard Duivenvoorde almost 4 years ago
Yes, you are right Nyall... but as we are going to encourage sharing of styles etc, I think this could happen more often..
Is it an idea to check for this?
Because it is (at least for me) not clear that it actual a configuration/data combination problem?
Like: check if OTF is disabled, and IF it is, check if sizes in styles are maybe different from projection units?
And if so: create a good warning?
You actually kill QGIS with such an action..
#7 Updated by Giovanni Manghi over 1 year ago
- Resolution set to end of life
- Status changed from Open to Closed
End of life notice: QGIS 2.18 LTR