thyme garbage collection?

[Mr_Stabby]

Im building something that would REALLY benefit from a spawner engine, the trouble is that i specifically avoid using that type of propulsion due to the memory leak algodoo seems to have (every spawned object still says in memory even after its long gone from the scene thus slowing the program down till you restart), i dont know if its intentional by the coders or not but does anybody have a clue as to wether algodoo has a counter system for that and how to trigger it? or maybe a way to kill objects so that they are really dead?

[KarateBrot]

I never had this problem. Once they get deleted via thyme they're gone. What do you do to delete them?

[Mr_Stabby]

make a random spawner and check your task manager, it starts eating memory like crazy and even after you delete the spawned stuff via killing or a script or whatever the memory usage stays, this tells me algodoo doesent really delete objects but just disables them which is common for programs while they r running performance critical tasks, however usually what follows is garbage collection which seems to be missing from algodoo

[KarateBrot]

Maybe it's only your PC. I spawned circles over a period of 4 minutes and it was far from lagging. My CPU load was the same as usual (constant about 8%) and my swap file (about 840MB) didn't change either.

[Mr_Stabby]

well i just loaded up algodoo -> 255mb memory use 2% cpu, made a box to spawn b collide circles on laser hit, pointed 4 lasers at it for faster results 4 mins later my fps at 4, cpu 79%, memory 665mb with 18143 circles spawned. i hit undo and my cpu drops to around 30%, mem stays at 665 even tho there are only 3 planes, 4 lasers and 1 box in the scene. i hit go again and for a while the mem use climbs steadily to 800ish then the program freezes for half a sec and mem use drops to 550mb(the thing im looking for), 4 mins later my fps at around 4 again cpu @ 60% and memory @ 873mb but this time with only 12785 circles spawned, i delete everything cpu drops to 30% mem stays at 873 and from this point on even simple scenes and phunlets are kinda sluggish and laggy not to mention the scene that i wanna use it for which already has over 500 components

[KarateBrot]

weird. does somebody else get this problem?

[daniels220]

Yep, I was playing around with a crappy scripted "automatic shotgun" of sorts that spawned hundreds of circles in a little group using lasers. Messed around with it for a few minutes, must have spawned 10-20k circles total, and Algodoo got rather slow even though I had the ground plane on killer so none of the circles stuck around. Restarting Algodoo fixes the problem, and also frees up a ton of memory, so I'd say it's definitely a GC issue.

[Ivanlul]

Happens to me too.

[RA2lover]

same to me, but it only happens after about 1 hour of collideprobe polygon spawning, which means 3.6 million polygons spawned.

that's a huge aumount of them, and i think the memory leak doesn't exist - just computer's overheating

[canadian joe]

possibly the reason the shapes are not "dead" is so that the undo button keeps it's purpose. the system has to keep all things that happen in memory so that you can undo it. but i know nothing about computer memory storage so if im wrong don't hold it against me

[Chronos]

But you can only undo up to a certain amount (you can set it, of course). After that, they're unneeded.

[canadian joe]

good point. so i guess my info is no longer needed.

[Antotabo]

Have you tried to set Max Undo to zero?? maybe then you will get immediate results.

[Chronos]

Then you can't undo.

[ioncann0ns]

Then you can't undo.

Correct, you also have far less lag.

[RicH]

For the price of always being careful to not make a mistake ever again.

[Mr_Stabby]

the undo/redo option doesent really make sense to me tho because the moment you change anything after undo all your redo options are gone and since spawning stuff in an active scene is strictly a future thing from any point so should be gone all the spawned data. Also i wanna reexplain my original point which many seemed to miss -

Lets imagine all objects of the scene are stored in memory with a bunch of custom data arrays that hold all possible information about the object. What i suspect is that in that array there is also a "dead" variable so when object gets killed in the scene somehow, instead of erasing the entire array only the dead variable gets set to true which prevents it from interacting with anything else in the scene.. now while this makes sense from the roaming performance pov and is a technique used widely in all kinds of programs it has a downside of cluttering the memory with a bunch of dead objects after a while. Usually there is a countermechanism that at some point really deletes the objects by erasing them from ram completely instead of just flipping the dead switch but in algodoo it seems to be missing or faulty or whatever.

[Altro]

If I remember correctly, the best way to fix this was to refresh your ram with a tool somewhere. This worked for me, alas the tool is now long gone and I forgot it's name. The tool got rid of all the ram that wasnt being used, or something like that, ie for Algodoo (and Phun) it drasticly reduced the amount of Ram being used

Yes, the above message makes no what so ever (probably)