QGIS crashes if border style differ from Solid Line and scale is very high

[dr]

1. Open any polygonal shapefile (see attachment);
   
2. New Symbology: Fill Style -> No Brush, Border Style -> Solid Line;
   
3. Set Scale 1:1;
   
4. New Symbology: Fill Style -> No Brush, Border Style -> any border style differ from Solid Line, e.g. Dash Line
   
5. Apply and QGIS crashes.

[dr]

More simple approach to get crash:

1. Open any polygonal layer;
   
2. New Symbology: Fill Style -> No Brush, Border Style -> any border style differ from Solid Line, e.g. Dash Line;
   
3. Set Scale 1:1;
   
4. Apply and QGIS crashes.
   

[dr]

Make lines appear less jagged at the expense of some drawing performance must be enabled!

[wonder]

I'm unable to reproduce on ubuntu 10.04 64-bit, Qt 4.6.2.

Does it crash when 'Fix problems with incorrectly filled polygons' option is on/off?

[dr]

If 'Fix problems with incorrectly filled polygons' option is on then 'Make lines appear less jagged at the expense of some drawing performance' automatically becomes turned off and error is not reproduced.
r1389M, WinXP, Qt 4.5.2

[wonder]

Yes, sorry I've realized that after posting.

It seems that this is a Qt bug. It would be good to try with newer Qt release.

[gislab]

I confirm that on r13890

[wonder]

Is it possible for you to produce a backtrace?

[dr]

Replying to wonder:

Is it possible for you to produce a backtrace?

Of course: ​http://pastebin.ca/1895889

[wonder]

Replying to dr:

Replying to wonder:

Is it possible for you to produce a backtrace?

Of course: ​http://pastebin.ca/1895889

Well, this is a debug log, here it doesn't have much use.

A backtrace can be obtained by running the application in debugger (e.g. gdb) or by examining core dump file produced by the system, see ​http://bugs.php.net/bugs-generating-backtrace.php

It seems you're on windows, the situation is more complicated (AFAIK you would need to compile qgis by yourself with debugging mode enabled to get some useful data). Can you replicate the problem also on a different platform?

[jef]

Replying to wonder:

A backtrace can be obtained by running the application in debugger (e.g. gdb) or by examining core dump file produced by the system, see ​http://bugs.php.net/bugs-generating-backtrace.php

BTW we have our own description: UsingTracWithQuantumGis#Creatingabacktrace

It seems you're on windows, the situation is more complicated (AFAIK you would need to compile qgis by yourself with debugging mode enabled to get some useful data). Can you replicate the problem also on a different platform?

And another note: the qgis-dev package in OSGeo4W is compiled in RelWithDebInfo mode with QGISDEBUG enabled. Still that isn't much use without a proper development environment.

[alexbruy]

I've try to generate backtrace on windows using qgis-dev package and gdb. Results attached (yes, I know that isn't much). Also in this archieve there is a report generated by Microsoft DebugDiag tool.

Unfortunatelly on my linux most libs are without debug info, so backtrace has only one line.

[alexbruy]

Backtrace from Windows+Osgeo4W

[pcav]

Still true with current version? Please check.

[lutra]

Cannot reproduce on trunk (r14892) under Linux. Is still true under windows?

[dr]

Still exists (r14892), WinXP

[lutra]

This is confirmed under trunk/Seven 32 bit.