I've a class derivating from CActive object (first time I do that), when I launch an instance of this task, all is good, but after the last RunL call its destructor is not called, and so at the application destruction, there is memory not free corresponding to this object.
And at the end of the last RunL, iActive is false, and iStatus is -1 (Test done in error case, CActive object on normal fct need gprs to run, i can't debug it: it seems to be too complex to make internet works on emulation)
Normally, I don't have to delete my task in the last RunL call, no ? What could lock the CActive object ?
An other question In many cases displaying dialog boxes in RunL causes application to hang or in one case paint problem on dialog boxes, does it be "normal": dialog boxes use forbidden in RunL ? or does it be caused by others problems ?
Thanks by advance for help