#845 closed bug (fixed)
Problem with large attribute tables
Reported by: | dassau | Owned by: | mhugent |
---|---|---|---|
Priority: | major: does not work as expected | Milestone: | |
Component: | OGR Layer support | Version: | Trunk |
Keywords: | large data ogr | Cc: | |
Must Fix for Release: | No | Platform: | Debian |
Platform Version: | lenny | Awaiting user input: | no |
Description
Hi,
I tried to open the database table of a very large shape file.
dbf -> 770 MB shp -> 384 MB shx -> 7 MB
Loading and visualizing the file works fine, although it takes some minutes, but opening the attribute table fails.
The error message is:
QIconvCodec::convertToUnicode: using ASCII for conversion, iconv_open failed terminate called after throwing an instance of 'std::bad_alloc' what(): std::bad_alloc Abgebrochen (core dumped)
When I generate a stacktrace, all it says is:
#0 0xffffe410 in ?? () Cannot access memory at address 0xbf8e8520
# Comment by Marco Hugentober:
The problem is that you run out of virtual memory (RAM and swap partition are full) and so the bad_alloc exception is thrown.In the short run we should add a try/catch block and in the long run not read all the rows into memory.
Change History (7)
comment:1 by , 16 years ago
Owner: | changed from | to
---|
comment:2 by , 16 years ago
# comment by Tim Sutton
This is really a side effect of ticket https://svn.qgis.org/trac/ticket/135
The table display needs to be redesigned to use qt interview framework. I have some in progress work to do this, and martin has been doing some similar work in python.
comment:4 by , 15 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
I assume (no such large data at hand) it does solve it; please test and reopen it if appropriate
comment:5 by , 15 years ago
Resolution: | fixed |
---|---|
Status: | closed → reopened |
Opening a large attribute table still fails for me. In fact, if I leave it long enough without killing the qgis process, it hangs my whole system.
Using 1.0.2 on Ubuntu 9.04 -- downloaded from ppa repositories.
Is there some way to get debugging info that I could send through to help with troubleshooting this?
comment:6 by , 15 years ago
Resolution: | → fixed |
---|---|
Status: | reopened → closed |
The problem should be fixed in 1.1
Marcos fix is already in r7701