Opened 15 years ago

Closed 15 years ago

Last modified 15 years ago

#1402 closed bug (worksforme)

Open attribute table hangs when a ShapeFile layer has usaved changes

Reported by: zachariahyoder Owned by: nobody
Priority: critical: causes crash or data corruption Milestone:
Component: Vectors Version: 1.0.0
Keywords: memory leak attribute table Cc:
Must Fix for Release: No Platform: Windows
Platform Version: Windows XP Home Awaiting user input: yes

Description

To reproduce:

Won't produce error:

a) Simply open the attributes table window on a ShapeFile layer

Will produce error:

a) Change the layer to editable b) Add a new point c) Open the attributes table

The memory usage will then increase about about 1G (in my test example). Of course this then causes the system to run slowly if you don't have that much memory!

This seems very similar to #1198, however there is no PostGIS involved. Are they related?

I notice there are two memory leak fixes that involved PostGIS NULL values, but again, this doesn't involve PostGIS. [8217], [6391]

Attachments (1)

MemoryUsagewAttributeTable.png (104.0 KB ) - added by zachariahyoder 15 years ago.
Screenshot of CPU and memory usage increase when opening the attributes table

Download all attachments as: .zip

Change History (6)

by zachariahyoder, 15 years ago

Screenshot of CPU and memory usage increase when opening the attributes table

comment:1 by zachariahyoder, 15 years ago

There was also no copying involved in producing this error.

comment:2 by christop, 15 years ago

This bug also appears with:

  • 0.11.0-Metis built against code revision 9842
  • on Debian lenny 64 bits.

comment:3 by msieczka, 15 years ago

Awaiting user input: set

Please test with 1.0 preview release from QGIS download page and report back here.

comment:4 by zachariahyoder, 15 years ago

Resolution: worksforme
Status: newclosed
Version: 0.11.01.0.0

Thanks! It works in 1.0.0-Kore-preview1.

comment:5 by (none), 15 years ago

Milestone: Version 1.0.1

Milestone Version 1.0.1 deleted

Note: See TracTickets for help on using tickets.