This page was last modified 06:54, 12 December 2007.
Active Object Pitfalls
From Forum Nokia Wiki
A stray-event panic from the Active Scheduler ( E32USER-CBASE 46 error ) is a most common problem with an Active Objects. This is ussually caused by one ( or more ) of the following:
1. You forgot to call CActiveScheduler::Add() before starting the Active Object.
2. You dont call SetActive() after issuing an async request.
3. Passing the same iStatus to two service providers at the same time ( multiple requests outstanding on the same Active Object ).
Do not invoke DoCancel() directly - it should be private - always call Cancel(). Note that Cancel() should be always be called in the destructor of your derived class.
Other related pitfalls (triggering other panics)
4. Using your own TRequestStatus variable, instead of using the one provided by CActive.
5. Passing automatic variables when doing an asynchronous request.
| Related Discussions | ||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Hot To Use Active Objects For Performing Multiple Task Simultaneously | jitendra_bhuyan | General Symbian C++ | 3 | 2007-11-18 01:00 |
| 3rd的长时间运行的任务问题-请教 | Ralovet | Symbian | 6 | 2008-06-16 08:34 |
| wait note display/busy loop problem | s4028469 | General Symbian C++ | 2 | 2007-09-10 20:47 |
| RSocket connect fails | adinkesp | General Symbian C++ | 3 | 2007-06-20 20:55 |
| Active Objects Syncronization | gs_cmans | General Symbian C++ | 2 | 2006-02-15 17:38 |
