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
Crash using the new labelling engine at very high scales #12932
Comments
Author Name: Médéric RIBREUX (Médéric RIBREUX) I am not able to reproduce it with trunk code under Debian Squeeze. |
Author Name: Gerhard Spieles (Gerhard Spieles) Replying to [comment:2 medspx]: Hi, its not the item in the layer properities. Its the labeling feature ABC shown in the attached pic 2. Gerhard
|
Author Name: Médéric RIBREUX (Médéric RIBREUX) Hello, thanks for your explanations... This new labeling plugin is experimental (as the new symbology system). I am still not able to reproduce the bug with the 1.5.0 trunk (under GNU/Linux Debian). I can "zoom" to 1:3 (and even 1:1) without crash. Perhaps is it MS Windows specific ? What if you try to set the scale with the zoom-in tool (focus on the label and try to zoom in progressively until 1:3 or less) ? Perhaps the bug is related to free labeling placement only... (It crashes a lot with this mode) ? |
Author Name: Gerhard Spieles (Gerhard Spieles) Hello, in a new project with only the layer, i wish to label, all is ok and I can zoom 1:1, 2:1 .... Gerhard |
Author Name: Giovanni Manghi (@gioman) Replying to [comment:5 gespiel]:
can you post a sample of the data that is causing the crash? |
Author Name: Gerhard Spieles (Gerhard Spieles) Replying to [comment:6 lutra]: sample project is attached Gerhard |
Author Name: Giovanni Manghi (@gioman) Hi, no crash at any scale level with the labelling plugin active. I'm under ubuntu 10.04 with qgis 1.5. Can you test this under a different platform? |
Author Name: Gerhard Spieles (Gerhard Spieles) Hello, |
Author Name: Giovanni Manghi (@gioman) Hi, I tested your vectors with the new labelling engine under qgis 1.5/osgeo4w in Windows Seven and I cannot replicate the crash. |
Author Name: Gerhard Spieles (Gerhard Spieles) Hell0, I@ve just tested it on a new build win7 machine and qgis crashed (see attachment) |
Author Name: Giovanni Manghi (@gioman) can you please test QGIS in english (en_us)? it is the only difference I'm seeing. |
Author Name: Giovanni Manghi (@gioman) Replying to [comment:12 lutra]:
I tested myself and no crash. In the labelling plugin, what configurations are you using? |
Author Name: Giovanni Manghi (@gioman) ok got it. There are configurations in the plugin that as a fact make qgis eat memory and then crash as described in this ticket. Just use one of the attached vectors and then choose for example "using perimiter". A scales around 1:1 it starts eating memory and then crash. Maybe this happens with other configurations. It does not crash with the default one, "around centroid". |
Author Name: Gerhard Spieles (Gerhard Spieles) Hi, |
Author Name: Paolo Cavallini (@pcav) Please deactivate all plugins and check if the problem still is there. Looks a local problem.
|
Author Name: Giovanni Manghi (@gioman)
|
Author Name: Giovanni Manghi (@gioman) It is not a local problem. It is confirmed on 1.7.3 that at very high scales, when the new labelling engine is used, QGIS starts eating memory, take a lot to render features and labels and ultimately freezes/crashes. This at least happens under Windows/osgeo4w BUT on master it works ok. The attached project is good to make tests and replicate the issue. I'll close this as fixed, but probably would be better to try backport the fix for the 1.7.x versions.
|
Author Name: Gerhard Spieles (Gerhard Spieles)
Original Redmine Issue: 2872
Affected QGIS version: 1.7.3
Redmine category:labelling
Assignee: Martin Dobias
Hello,
the new core function labeling "abc" is absolutly best.
In extrem situations, it seems to have a malfunction.
When labeling with abc in a vectorlaxer is on and you set the scale less 1:3, qgis crash.
Picture is attached.
The text was updated successfully, but these errors were encountered: