Volume3DInt does not properly destroy

Bug #429406 reported by andrew reid on 2009-09-14
This bug affects 1 person
Affects Status Importance Assigned to Milestone
andrew reid

Bug Description


When using InterfaceVolumePanel to load volumes; if a volume is deleted and another one loaded, the 3D rendering of the shape is a mixture of the current and previous volumes. Somehow the Texture3D object persists despite being deleted and detached from the parent node.




Problem may be in how scene nodes destroy themselves; however, currently the ShapeSceneNode destruction procedure seems to work like it should: setting its shape node to null and detaching it, removing its children, and detaching itself. There is no simple explanation why the scene node should be reinserted into the graph with the instantiation of a new Volume3DInt after it has been detached; nor why the data should remain in memory at all. There is a possibility that this may be another Java 3D bug, but has yet to be reproduced outside of mgui.


None available.

andrew reid (typically) on 2009-09-14
Changed in modelgui:
assignee: nobody → andrew reid (typically)
importance: Undecided → Critical
milestone: none → core-1.0.0-beta
status: New → Confirmed
tags: added: graphic3d java3d volume3d
andrew reid (typically) on 2010-03-12
Changed in modelgui:
milestone: core-1.0.2-alpha → core-1.0.0-beta
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers