Opened 9 years ago
Closed 9 years ago
#3026 closed defect (fixed)
[Atlas] crash when zooming out on a map
Reported by: | serveurix | Owned by: | philip |
---|---|---|---|
Priority: | Must Have | Milestone: | Alpha 18 |
Component: | Atlas editor | Keywords: | crash, atlas, vbo |
Cc: | Patch: |
Description (last modified by )
I'm editing some maps with the last svn, and when I zoom out, Atlas segfaults at a certain level of zoom, with the following message:
ERROR: Failed to create VBOs (64*32827) ERROR: Failed to allocate VBO for vertex array Erreur de segmentation
Could this be related to: r16241 ?
Debian Jessie with Radeon R9 280X, Catalyst driver. Edit: happens with radeon too.
Update: When I'm moving the camera angle sometimes I get the error messages printed on screen, but no crash. I also have a shadow appearing all over the map under certain camera angles.
Update: The map on which I have the problem. Note that this map was created *before* the last VBO commit.
Attachments (3)
Change History (17)
comment:1 by , 9 years ago
Description: | modified (diff) |
---|
comment:2 by , 9 years ago
comment:3 by , 9 years ago
Component: | Core engine → Atlas editor |
---|
comment:4 by , 9 years ago
Description: | modified (diff) |
---|---|
Milestone: | Backlog → Alpha 18 |
Priority: | Should Have → Must Have |
Summary: | Atlas : crash when zooming out on a map → [Atlas] crash when zooming out on a map |
comment:5 by , 9 years ago
I thought I could get away with making the VBOs a bit smaller (2MB instead of 4MB) to reduce the wasted memory, but evidently I can't :-(
comment:6 by , 9 years ago
Hmm, actually I'm not sure that's really the problem... Even on a huge map like "Eire and Albion", I don't see any allocations larger than 64*10327, which easily fits within the 2MB limit, so I'm not sure what's causing such a huge allocation in this case.
It would probably be helpful to get a stack trace by running it in gdb - that should indicate where the allocation is happening. If it happens repeatedly on a particular map, it would be helpful to know which map (or get a copy if it's a custom map).
by , 9 years ago
Attachment: | ziggurat4.xml added |
---|
by , 9 years ago
Attachment: | ziggurat4.pmp added |
---|
comment:8 by , 9 years ago
Description: | modified (diff) |
---|
by , 9 years ago
Attachment: | logs.tar.gz added |
---|
comment:9 by , 9 years ago
Here's some instructions on how to get a 0 A.D. crash backtrace on Linux: Debugging
follow-up: 11 comment:10 by , 9 years ago
Description: | modified (diff) |
---|
comment:12 by , 9 years ago
Looks like art/meshes/structural/pers_gardens_struct.dae has a crazy number of vertexes - normally 32410, and if you turn on preferglsl+gentangents it goes up to 32827. Each vertex takes 64 bytes in the VBO, so 32827 exceeds 2MB and it fails. I can increase the limit back up to 4MB. (Seems an excessively large mesh, though...)
comment:13 by , 9 years ago
It's because of all the plants on it, Enrique did a really good detail job on it.
Could you provide a crashdump and system info ? :)