About Viewsrv 11 panic
They occur when the Viewsrv active object in your, or any other, application does not respond to the view server in time. Typically 10-20 seconds is the maximum allowed response time.
Guidelines for avoiding common causes of this problem:
1, Do not have long running synchronous operations. e.g. “while (1) { GameStep(); }”.
2, Ensure that your active objects don’t swamp the scheduler. The active scheduler processes active objects strictly in priority order, and for those of the same priority, active objects added first have priority. Active objects that run often and use a lot of processing time should run at low priority. The Viewsrv active object runs at CActive::EPriorityStandard, so busy active objects should run at a lower priority. One note of warning: if you use EPriorityLow, ensure it is scoped as CActive::EPriorityLow, otherwise you may get thread priority EPriorityLow, which is actually a very high priority value for an active object!
3) Allow some CPU time for other applications.
4) Do not use User::WaitForRequest();
5) On some platforms, be aware that launching waiting dialogs (or performing other blocking actions) from ViewActivatedL(); or ViewDeactivatedL(); can also cause Viewsrv 11 panics.
Assesmbled from here: http://www3.symbian.com/faq.nsf/0/894657c7845917a380256d98005baff7?OpenDocument
Popularity: 25% [?]
Add comment 04月 23rd, 2008