Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 1.5.2
    • Fix Version/s: 1.6.0
    • Component/s: j3d-core
    • Labels:
      None
    • Environment:

      Operating System: Windows XP
      Platform: All

    • Issuezilla Id:
      520

      Description

      It appears that memory associated with a Texture3D object is retained by Java 3D
      even after that object is flushed from the scene.

      The config is:
      JDK 1.6.0_02, Java 3D 1.5.2-pre1 Sep04 daily, 6600GT (93.71), WinXP SP2 OGL

      Attached test case illustrates the issue. To run do:

      1. deflate the tex3DLeak.jar
      2. javac *.java
      3. java Texture3Dtest

      Upon launching, the Memory Monitor shows a used memory of ~50MB. Press the
      "Flush" button to flush everything including the Texture3D object on the content
      side of the scenegraph. On my system, I notice that the used memory refuses to
      come down.

      It doesn't, however, appear that the memory leak is cumulative.

        Activity

        Hide
        nvaidya added a comment -

        Created an attachment (id=309)
        Testcase to demo issue

        Show
        nvaidya added a comment - Created an attachment (id=309) Testcase to demo issue
        Hide
        kcr added a comment -

        Set target milestone to 1.6.0

        Show
        kcr added a comment - Set target milestone to 1.6.0

          People

          • Assignee:
            java3d-issues
            Reporter:
            nvaidya
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated: