Skip to main content

memory pooling

4 replies [Last post]
pepe
Offline
Joined: 2003-06-10

While i was debugging in core, i entered what seemed to be memory pooling classes (FreeMemoryList, FreeListManager ).
Are those classes really needed now that Generational GC is on and works more than nicely?

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
Chien Yang

Frederic,
Yes, these classes were created to reduce "hiccup" in rendering, in the
early days, with jdk1.2.1_04 or jdk1.3. It is quite likely that these
classes are less useful with the new jdk, but it is still an educated
guess. :-)

- Chien.

java3d-interest@javadesktop.org wrote:
> While i was debugging in core, i entered what seemed to be memory pooling classes (FreeMemoryList, FreeListManager ).
> Are those classes really needed now that Generational GC is on and works more than nicely?
> ---
> [Message sent by forum member 'pepe' (frederic barachant)]
>
> http://www.javadesktop.org/forums/thread.jspa?messageID=22440&#22440
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: interest-unsubscribe@java3d.dev.java.net
> For additional commands, e-mail: interest-help@java3d.dev.java.net
>

---------------------------------------------------------------------
To unsubscribe, e-mail: interest-unsubscribe@java3d.dev.java.net
For additional commands, e-mail: interest-help@java3d.dev.java.net

pepe
Offline
Joined: 2003-06-10

I was wondering if that pool could not be responsible for undereferenced images and tree graph bug report we see from time to time.
Misusing it, that is not adding an object to free list could lead to that.

Am i dreaming or are we back into ooold days of C and its memory handling problems?

I'm not sure if removing it would lead to much better performance (i think anyway it might play a role) but it would imho certainly enhance stability and memory useage, simply by being less sensible to human factor.
I've been checking how hard and how long it would be to remove that pooling, and it seems that architecture is oriented to the use of pools. I'll have to look more again.

kcr
Offline
Joined: 2004-03-17

I doubt that the existing memory leaks are related to the use of object pools, but it's possible we missed some.

In any case, I would be very hesitant to make a change as major as removing the memory pools for the 1.4 version (and certainly not for 1.3.2), but this is exactly the sort of thing that should be done for 1.5/2.0.

-- Kevin

pepe
Offline
Joined: 2003-06-10

> I doubt that the existing memory leaks are related to the use of object pools, but it's possible we missed some.
That's what i meant, in fact. Sorry if i was unclear.