Bug #769 (closed)
Opened 12 years ago
Closed 12 years ago
Rendering Engine Memory Leak
| Reported by: | cxallan | Owned by: | cxallan |
|---|---|---|---|
| Priority: | major | Cc: | |
| Sprint: | n.a. | ||
| Total Remaining Time: | n.a. |
Description
As part of milestone:3.0-Beta2, we enabled an optimization to reduce repeated memory allocations inside the rendering engine's rendering strategy. The basic premise of this optimization is to keep the return buffer for renderAsPackedInt() from being re-allocated every invocation. The rendering engine's currently have passivation disabled, and keeping this buffer around results in gradual memory exhaustion. Finally, usage requires that the buffer be zero'd out prior to every call, reducing any perceived performance gain down to a negligible (sub 10ms) amount.
Change History (6)
comment:1 Changed 12 years ago by cxallan
- Owner changed from jmoore to callan
- Status changed from new to assigned
comment:2 Changed 12 years ago by cxallan
comment:3 Changed 12 years ago by cxallan
- Resolution set to fixed
- Status changed from assigned to closed
comment:4 Changed 12 years ago by jmoore
- Milestone changed from 3.0-Beta3 to 3.0-Beta2.2
comment:5 Changed 12 years ago by cxallan
- Milestone changed from 3.0-Beta2.2 to 3.0-Beta2.3
- Resolution fixed deleted
- Status changed from closed to reopened
There is now a similar issue that relates to image lookup tables that has cropped up with the new start and end changes.
comment:6 Changed 12 years ago by cxallan
- Resolution set to fixed
- Status changed from reopened to closed
Lookup table memory leaks resolved in r1966.
Fixed in r1739.