Bug report #2865: QGIS crashes if border style differ from Solid Line and scale is very high - QGIS Application - QGIS Issue Tracking

Bug report #2865

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

Added by dr - over 14 years ago. Updated almost 13 years ago.

Status:	Closed
Priority:	Low
Assignee:	-
Category:	Symbology
Affected QGIS version:	master	Regression?:	No
Operating System:	Windows	Easy fix?:	No
Pull Request or Patch supplied:	No	Resolution:	fixed
Crashes QGIS or corrupts data:	No	Copied to github as #:	12925

Description

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.

err.7z (487 Bytes) dr -, 2010-07-06 12:43 AM

bt.tar.bz2 - Backtrace from Windows+Osgeo4W (4.79 KB) Alexander Bruy, 2010-07-07 11:39 AM

History

#1 Updated by dr - over 14 years ago

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.

#2 Updated by dr - over 14 years ago

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

#3 Updated by Martin Dobias over 14 years ago

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?

#4 Updated by dr - over 14 years ago

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

#5 Updated by Martin Dobias over 14 years ago

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.

#6 Updated by Maxim Dubinin over 14 years ago

I confirm that on 37a815ed (SVN r13891)

#7 Updated by Martin Dobias over 14 years ago

Is it possible for you to produce a backtrace?

#8 Updated by dr - over 14 years ago

Replying to [comment:7 wonder]:

Is it possible for you to produce a backtrace?

Of course: [http://pastebin.ca/1895889]

#9 Updated by Martin Dobias over 14 years ago

Replying to [comment:8 dr]:

Replying to [comment:7 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?

#10 Updated by Jürgen Fischer over 14 years ago

Replying to [comment:9 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.

#11 Updated by Alexander Bruy over 14 years ago

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.