Search:

Type: Posts; User: KevinWorkman

Search: Search took 0.11 seconds.

  1. Re: Dooes the "removeNodeFromParent" method from DefaultTreeModel remove grandchildren?

    Like I said, that's called an island of isolation.



    There is no black voodoo magic, and you can read all about how the garbage collector works. I agree that you shouldn't really worry about...
  2. Re: Dooes the "removeNodeFromParent" method from DefaultTreeModel remove grandchildren?

    That situation is, funnily enough, called an "island of isolation", and you can google that for more info. Basically those objects are unreachable and are eligible for garbage collection.


    ...
  3. Re: Dooes the "removeNodeFromParent" method from DefaultTreeModel remove grandchildren?

    Can you give us an example? The only one I can think of is a WeakReference, but that's a pretty special case.



    The OP's question is whether those sub-graphs are reachable. (Although, a...
  4. Re: Dooes the "removeNodeFromParent" method from DefaultTreeModel remove grandchildren?

    This is a bit of an oversimplification. Sure, the garbage collector will take care of eligible memory, but he's asking whether that memory is eligible. It's actually not immediately obvious whether...
  5. Re: Dooes the "removeNodeFromParent" method from DefaultTreeModel remove grandchildren?

    You could try creating a program that constantly adds and removes nodes using that method and check what the memory does over time. Or you could dig through the source, which is including with the...
Results 1 to 5 of 5