Opened 12 years ago
Closed 9 years ago
#265 closed defect (invalid)
WMS fill pyramid fails on large collections
Reported by: | Dimitar Misev | Owned by: | Dimitar Misev |
---|---|---|---|
Priority: | major | Milestone: | Future |
Component: | rasgeo | Version: | 8.3 |
Keywords: | Cc: | Peter Baumann | |
Complexity: | Very Hard |
Description
It fails to allocate memory as it seems, i.e. it needs to be fixed to fetch less data per transaction:
working on domain [0:180259,0:29695]: fetching map information from database...ok performing database update with pyramid: pyramid layer haiti_vnir_pyr, factor 0.5, target domain [0:90129,0:14847]...terminate called after throwing an instance of 'std::bad_alloc' what(): std::bad_alloc Caught signal 6: Abort (ANSI) or IOT trap (4.2 BSD). Exiting. fill_pyramid.sh: done.
Change History (2)
comment:1 by , 12 years ago
Milestone: | → Future |
---|
comment:2 by , 9 years ago
Complexity: | → Very Hard |
---|---|
Resolution: | → invalid |
Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
this request seems to try to scale a tile of about 9 GB. Hence, it may be a consequential of a base layer inserted untiled into the database, going away with fixing ticket #294. Hence, proper action is to resolve #294 and then check again.
The probable root cause, tiles larger than main memory, is a consequence of the architecture (and any architecture based on tiles), so it will not be addressed as such.