Mantis Bug Tracker

View Revisions: Issue #6586 All Revisions ] Back to Issue ]
Summary 0006586: CPU usage on a multi-sim instance jumps to 99% and stays there. Started noticing this issue about 3/15/2013.
Revision 2013-03-27 15:55 by kenvc
Description This is possibly related to mantis 0006582, but not sure. TPs have been very unreliable the last few days using daily dev master updates, but the source of the problem may not be related to teleporting, but that's when I usually notice it.

The last week or so, CPU usage on one of my instances will suddenly jump to 98-99% and stay there hogging all resources on the server. With my setup, the CPU usage is rarely over 15-40% even when starting up multiple instances with multiple sims. When this issue happens, you have to force close the instance that was hogging all the CPU time and then all is back to normal. So far the user logs have not shown any clue as to why this is happening, but when it does a lot of red errors start showing up in the log files because of the slowdown. This is not any easy issue to duplicate unless you are really pushing your I am still going through the process to git bisect to determine exactly when this issue began.
Revision 2013-03-26 20:27 by kenvc
Description This is possibly related to mantis 0006582. TPs have been very unreliable the last few days using daily dev master updates.

On multiple occasions, cancelling a non-responsive TP (no progress showing on TP progress bar after some time) cause the browser to close and made the CPU usage for that instance to jump to 99% and stay there. This effectively caused all other operations on the server to come to a halt until that instance was forcefully closed. The AV trying to TP was using the browsers built-in AO and was wearing no scripted attachments at all, just normal clothes and hair etc.
Attached is the user log pulled right after the instance was forcefully closed. Nothing looks unusual there. I am still going through the process to git bisect to determine exactly when this issue began.
Revision 2013-03-26 20:24 by kenvc
Description TPs have been very unreliable the last few days.

On multiple occasions, cancelling a non-responsive TP (no progress showing on TP progress bar after some time) cause the browser to close and made the CPU usage for that instance to jump to 99% and stay there. This effectively caused all other operations on the server to come to a halt until that instance was forcefully closed. The AV trying to TP was using the browsers built-in AO and was wearing no scripted attachments at all, just normal clothes and hair etc.
Attached is the user log pulled right after the instance was forcefully closed. Nothing looks unusual there. I am still going through the process to git bisect to determine exactly when this issue began.


Copyright © 2000 - 2012 MantisBT Group
Powered by Mantis Bugtracker