Bug report #11453

Crash when zooming in too far with MSSQL spatial layer

Added by Darren Cope over 9 years ago. Updated almost 9 years ago.

Status:Closed
Priority:Severe/Regression
Assignee:-
Category:Data Provider/MSSQL
Affected QGIS version:master Regression?:No
Operating System:Windows Easy fix?:No
Pull Request or Patch supplied:No Resolution:fixed/implemented
Crashes QGIS or corrupts data:Yes Copied to github as #:19729

Description

I have added an MSSQL Spatial Layer (line). when I zoom in 'too far', QGIS will crash, giving a .dmp file (attached). The 'too far' seems to vary based on having other layers in the project, and/or if the layer is editable or if nodes are highlighted.

I did a search of QGIS issues, and couldn't find anything related, but may have missed it. Any thoughts?

CrashDump.zip - crash dump (4.27 MB) Darren Cope, 2014-10-20 06:12 AM

History

#1 Updated by Darren Cope over 9 years ago

#2 Updated by Giovanni Manghi over 9 years ago

  • Category set to Data Provider/MSSQL
  • Status changed from Open to Feedback

It is ok on 2.4 or older?

#3 Updated by Darren Cope over 9 years ago

I just tried on 2.4, and the problem does occur there as well. It does not seem to happen in 2.1 or 1.9.

#4 Updated by Giovanni Manghi over 9 years ago

  • Priority changed from Normal to Severe/Regression

Darren Cope wrote:

It does not seem to happen in 2.1 or 1.9.

and
2.0.1 or 2.2 (the stable releases)?

#5 Updated by Darren Cope over 9 years ago

I had to install 2.0.1 and 2.2.0 from the stand alone installers as I didn't have them on this computer. I tested in both, and it appears to work fine.

#6 Updated by Giovanni Manghi over 9 years ago

  • Status changed from Feedback to Open

#7 Updated by Jürgen Fischer over 9 years ago

  • Subject changed from QGIS 2.5.0-Master Crashing When Zooming in too far with MSSQL Spatial Layer to Crash when zooming in too far with MSSQL spatial layer
  • Operating System set to Windows

#8 Updated by Nathan Woodrow over 9 years ago

  • Status changed from Open to Feedback

Can you try a newer build. I fixed a bug that might be related to this a week or so ago.

#9 Updated by Darren Cope over 9 years ago

Nathan; the problem still seems to occur after running an OSGEO4W update this morning.

#10 Updated by Giovanni Manghi over 9 years ago

  • Status changed from Feedback to Open

#11 Updated by Martin Dobias about 9 years ago

  • Status changed from Open to Feedback

This may have been fixed with b48e7fd3 - could you please test again?

#12 Updated by Giovanni Manghi almost 9 years ago

  • Resolution set to fixed/implemented

Martin Dobias wrote:

This may have been fixed with b48e7fd3 - could you please test again?

closing for the lack of feedback, please reopen if necessary.

#13 Updated by Giovanni Manghi almost 9 years ago

  • Status changed from Feedback to Closed

Also available in: Atom PDF