Opened 13 years ago
Closed 13 years ago
#3709 closed bug (fixed)
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: | |
| Must Fix for Release: | Yes | Platform: | Windows |
| Platform Version: | 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 (8)
comment:1 by , 13 years ago
| Priority: | major: does not work as expected → critical: causes crash or data corruption |
|---|
comment:2 by , 13 years ago
| Component: | Build/Install → Digitising |
|---|
comment:3 by , 13 years ago
comment:4 by , 13 years ago
| Resolution: | → worksforme |
|---|---|
| Status: | new → closed |
worksforme on polygonal layer in WinXP, r15700
comment:5 by , 13 years ago
| Resolution: | worksforme |
|---|---|
| Status: | closed → reopened |
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
comment:7 by , 13 years ago
| Owner: | changed from to |
|---|---|
| Status: | reopened → new |
comment:8 by , 13 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
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()
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?