@dickhirsch : I had to stop all my tracks yesterday because of it

Memory usage is better now. I think it is linked to the track functionality

ok, same here. Thanks!

@ok : restart always works

@ok : Yes, the more tracks you create that have lots of esmets the higher your memory usage increase as the esmets are updated. Irregardless of whether you create esmets or not

The memory issue is with the AIR client? Had the same experience yesterday. Occasional restart worked. I would have thought it would be a client bug. Any other assumptions?

Restarted client with no tracks. Let's see if that is better

Memory back up to 435M. Restarting

Memory back down to 196. Forcing things a bit by using tracks for ESME core team

After lunch, memory is once again really high 345 M

@dickhirsch : Everything was fine during DJ..actually ESME was faster than the live broadcast from Las Vegas :)

Memory appaers to be better but also little traffic on the system

profiling the AIR app for memory performance .. need a good message flow

profiling the AIR app for memory performance .. need a good message flow

profiling the AIR app for memory performance .. need a good message flow

I have stopped my tracks as well now

@dickhirsch : yup

@mrinal : That is why tracks are so memory-intensive

@dickhirsch : memory is consumed in rendering each message and keeping the image in memory .. I will optimize .. more messages more memory .. will optimize after server setting

@mrinal : memory problem is better since I dropped my tracks. If you want to get the memory problem real quick. track our names

the memory problem gets bad aget you have 200-300 messages .. 2nd on my list todo @dickhirsch

Now up to 263 M Mem usage

Now up to 150 M. Maybe, it is because Im tracking "hirsch"

During updates, memory jusmps and then falls again. Maybe due to pictures?

Notification task is present in the windows tasks manager although it is not visible

Mem usage now at 90M