Microsoft Developer Network >
Página Inicial dos Fóruns
>
Live Framework
>
Live Framework Client MeshAppMonitor.exe consumes too much CPU and RAM when Idle
Live Framework Client MeshAppMonitor.exe consumes too much CPU and RAM when Idle
- I have an Intel Xeon based Windows Server 2008 system. When the Live Framework Client's MeshAppMonitor.exe is loaded and running Idle, it consumes too much memory and CPU resources and the system runs very slow and sluggish. With the MeshAppMonitor.exe shut down the system runs quickly and is much more responsive.
There is no reason why an Idle system monitor should have such a huge affect on Server performance.
MSFT should do some work to drastically reduce the impact of the MeshAppMonitor when Live Framework is not being used.
What can be done to reduce the impact of the MeshAppMonitor.exe when idle, other than terminating it?
Why does MeshAppMonitor.exe consume so much CPU and RAM when Idle?- EditadoDonBaechtel terça-feira, 16 de junho de 2009 16:25
- Tipo AlteradoDonBaechtel quinta-feira, 2 de julho de 2009 16:00looking for answers
- Tipo AlteradoBen Williams - MSFTMSFT, Moderadorquinta-feira, 25 de junho de 2009 19:30lack of response
- Tipo AlteradoBen Williams - MSFTMSFT, Moderadorquinta-feira, 2 de julho de 2009 15:54
- Tipo AlteradoDonBaechtel quinta-feira, 25 de junho de 2009 19:58looking for answers to questions asked.
Respostas
- As you might have seen annoucement in our blogs and herein this forum, we are closing this CTP Program w.e.f Sept 8, 2009.
I am closing this thread for now, you can check for new annoucements/updates later at this forum or at http://dev.live.com
Thanks,
Vikas
This posting is provided "AS IS" with no warranties, and confers no rights.- Marcado como RespostaVikas-AhujaMSFT, Moderadorterça-feira, 8 de setembro de 2009 5:56
Todas as Respostas
- Hi Don, can you create a bug on http://connect.microsoft.com/liveframework/feedback and attach the logs for your machine to it? The instructions for capturing the log files are on the bug submission form.
thanks,
Ben
This posting is provided "AS IS" with no warranties, and confers no rights.- Não Marcado como RespostaDonBaechtel terça-feira, 16 de junho de 2009 16:23
- Marcado como RespostaBen Williams - MSFTMSFT, Moderadorterça-feira, 16 de junho de 2009 15:14
- Hi Don, In order to investigate we need to open a bug as I suggested above. That is why I marked it "answered" as this type of investigation needs to be handled as a bug instead of in this forum. Once you log the bug and send the logs we can start having a look at what may be causing this.
thanks,
Ben
This posting is provided "AS IS" with no warranties, and confers no rights. - Hi Don, I havent seen any new bugs like this so I assume you havent submitted one. To answer your questions directly, I have seen anectdotal reports of similar behavior but without any diagnostic information we cannot tell for sure what is causing this in order to make changes to prevent it for you and other users.
When you get a chance, please let us know if you want to continue to help us in finding the resolution by opening a bug and following the instructions on the bug submission form for gathering the appropriate data. For the moment, I am converting this into thread into general discussion. You can always convert this back to question by clicking on options and choosing "change type".
thanks,
Ben
This posting is provided "AS IS" with no warranties, and confers no rights. - I would like to find a fix or workaround to the problem with MeshAppMonitor.exe.
What diagnostic information can I provide that will assist with the investigation of this problem? - Submit a bug at https://connect.microsoft.com/liveframework/feedback/ by clicking the Submit Feedback entry then click the link for "Submit your Bug".
When you submit the bug you will be given the option of attaching log files to your bug after you click the submit button below.
To create the log files for Live Framework Client reporting:
1. Click Start
2. Select All Programs so that you are looking at the program folder for Live Framework Client (see screenshot below).
3. Click Collect Logs
4. Your logs will be bundled together in a cab file named LiveFxClientLogs.cab saved on your desktop.
5. Complete the bug form and provide as much details as possible for our team to be able to understand and investigate your issue
6. Submit your bug. You will attach the cab file after the bug has been submitted.
7. On the bottom of the next page click attach files.
8. Attach the LiveFxClientLogs.cab saved on your desktop.
Once someone can review these logs then we can either take action or may need additional information from there. But that is the first step. Thanks!
Ben
This posting is provided "AS IS" with no warranties, and confers no rights. - As you might have seen annoucement in our blogs and herein this forum, we are closing this CTP Program w.e.f Sept 8, 2009.
I am closing this thread for now, you can check for new annoucements/updates later at this forum or at http://dev.live.com
Thanks,
Vikas
This posting is provided "AS IS" with no warranties, and confers no rights.- Marcado como RespostaVikas-AhujaMSFT, Moderadorterça-feira, 8 de setembro de 2009 5:56
