Ticket #3709 (closed bug: fixed)

Opened 2 years ago

Last modified 2 years ago

Spatialite editing not working

Reported by: ulmi Owned by: esseffe
Priority: critical: causes crash or data corruption Milestone: Version 1.7.0
Component: Digitising Version: Trunk
Keywords: Spatialite, qgis Cc:
Platform Version: Platform: Windows
Must Fix for Release: Yes Awaiting user input: no

Description

Spatialite editing not working on qgis trunk, just for lines and polygons.

Not saving new features or editing old, crashes after a second and third try.

Point features work though!!

Change History

Changed 2 years ago by ulmi

  • priority changed from major: does not work as expected to critical: causes crash or data corruption

Changed 2 years ago by pcav

  • component changed from Build/Install to Digitising

Changed 2 years ago by pcav

In Debian testing apparently it works well. Anyone confirms, on Windows or other platforms? Does this happen with just one db, or all? Can you share one of your db who is causing the crash?

Changed 2 years ago by gislab

  • status changed from new to closed
  • resolution set to worksforme

worksforme on polygonal layer in WinXP, r15700

Changed 2 years ago by ulmi

  • status changed from closed to reopened
  • resolution worksforme deleted

For me it just works on point layers.

Neither new features or editing works on polygons and line layers, causes crash and exit. WinXp? with 1.7 r15740.

Everything works on 1.6

Sample DB >  http://dl.dropbox.com/u/378544/ZIF.7z

Changed 2 years ago by dr

Confirm crash in Windows 7, r15740.

Changed 2 years ago by mhugent

  • owner changed from nobody to esseffe
  • status changed from reopened to new

Changed 2 years ago by esseffe

  • status changed from new to closed
  • resolution set to fixed

fixed on r15814

not at all specific to Windows: this bug actually affected any platform. Shortly said: there was an uncorrect size calculation for 3D Geometries causing a memory overflow condition (and consequently, a fatal crash).

BTW while investigating on this, I discovered (and resolved) a further bug related to 3D Mulipolygons editing on QgsGeometry?.moveVertex()

Note: See TracTickets for help on using tickets.