Java3D node not destroyed with Graphics3D
Bug #423278 reported by
andrew reid
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ModelGUI |
Fix Released
|
High
|
andrew reid |
Bug Description
Synopsis:
When a Graphics3D window is destroyed, it does not appear to release its Java3D scene node. This is evident when a new Graphics3D window is set to the same model; a second light source is visible. This is a potential memory leak.
Version:
1.0.0-alpha
Description:
This is likely a problem with ShapeModel3D and InterfaceGraphi
Workaround:
None available.
Related branches
Changed in modelgui: | |
assignee: | nobody → andrew reid (typically) |
importance: | Undecided → High |
milestone: | none → core-1.0.0-beta |
status: | New → Confirmed |
summary: |
- Java3D Node not destroyed with Graphics3D + Java3D node not destroyed with Graphics3D |
tags: | added: graphics graphics3d shapemodel3d |
tags: |
added: graphic3d removed: graphics3d |
tags: | added: java3d |
Changed in modelgui: | |
milestone: | core-1.0.2-alpha → core-1.0.0-beta |
To post a comment you must log in.
Fix released with mgui-1.0.8-alpha.