PDA

View Full Version : Memory Leak?



ftanner
06-06-2015, 09:54 AM
Does anyone else experience memory leaks with the Mezzmo "client" if you leave it open in the system tray? It takes days, sometimes as much as a few of weeks, but the memory consumed grows and grows and eventually crashes somewhere around the 1GB to 1.5GB mark. The interface tends to get slower and slower as this happens.

Also as a weird note, I have noted that sometimes with the latest version of Mezzmo, there is sometimes multiple copies of the MezzmoMediaServer.exe*32 process in the Tasks tab. Usually when there have been problems playing a video, but sometimes "just because". Only one of them is consuming CPU time, but both of them are consuming RAM. These multiple processes seem to cause issues with each other as well.

Paul
06-08-2015, 07:20 PM
We have fixed a few memory leaks for the upcoming Mezzmo v5.0, so possibly we have caught the one that you are experiencing. We'll make sure we run the upcoming Mezzmo v5.0 on a test computer here for a few weeks during the Beta testing period to check if the leak is still there.

ftanner
06-09-2015, 10:02 AM
We have fixed a few memory leaks for the upcoming Mezzmo v5.0, so possibly we have caught the one that you are experiencing. We'll make sure we run the upcoming Mezzmo v5.0 on a test computer here for a few weeks during the Beta testing period to check if the leak is still there.

Coolness. Thank you very much. Any idea on the funky MezzmoMediaServer.exe*32 process issue? Is it possible it's somehow related to the memory leak?

Paul
06-09-2015, 10:23 AM
Coolness. Thank you very much. Any idea on the funky MezzmoMediaServer.exe*32 process issue? Is it possible it's somehow related to the memory leak?

Sorry - missed replying to your other issue. We have also found and fixed the issue where multiple MezzmoMediaServer.exe*32 processes may be present.

ftanner
06-09-2015, 11:54 AM
Sorry - missed replying to your other issue. We have also found and fixed the issue where multiple MezzmoMediaServer.exe*32 processes may be present.

Sweet! Thank you.