Is it possible that a developer can take a look into the following thread?

http://www.opserver.de/ubb7/ubbthreads.php?ubb=showflat&Number=273854#Post273854

I try to find out, how I can debug memory problems. Is it possible to get the function names out of the “function scheduler list?”

Thanks

You can see the number of running functions in the F11 panel. If this number permanently increases, then the bug is a repeated call to a function containing a wait() somewhere in your code. Should be easy to find.

If the number of entities permanently increases, then the reason is a repeated ent_create call. The +1KB increase that you describe in your thread is possibly an entity creation because their size is just 1 KB.

If it's none of both, but the "mem" value increases permanently, then it's another create function of an engine object, f.i. of a panel, bitmap, material, sound or the like.

Hi jcl,

MCKiller wrote that the number of functions and the number of entities are stable.

Isn't it possible to get the names of all currently running functions? If not maybe you could add it to a future version of gs?

It could be hard to find out which functions are currently running if the overall number of functions is big. And with that it could be hard to find out where a panel, bitmap, material, sound or the like is created in a loop.

Regards,
Pegamode

A way to list all running functions would be useful indeed. I'll implement this as an engine feature and also in the SED debugger.

My next suspect for a +1KB increase would be a material creation, or a truetype font creation. All other objects use either less or more than 1 KB. So, look for functions that create materials or fonts - or any functions that have "_create" in them.

That're great news ... thanks so much. That'll make debugging much easier.

Regards,
Pegamode.

That's realy great. I think it will help a lot of people.