I have some interesting observation, When I am testing a memory intensive video streaming applications in Nokia third edition phones.

In nokia N93 Symbian OS sends EikCmdExit (to my application) after starting multiple memory intensive applications (gallary, camera etc). This is quite logical.

When I am testing a memory intensive video streaming applications, I found some interested scenarios.

In nokia N93 Symbian OS sends EikCmdExit (to my application) after starting multiple memory intensive applications (gallery, camera etc). This is quite logical.

But I have observed an N91 device (s/w version: V 3.00.060 03-11-06 RM-43 N91) , after opening native browser, Symbian OS sending EikCmdExit to my application.

When exploring this issue further, I found, Symbian Heap allocator inefficiently allocating dynamic memory. During startup, Application is getting whatever heap memory mentioned minimum in EPOCHEAPSIZE instruction in mmp file.

Ex: EPOCHEAPSIZE 1000000 2000000
During application startup, application getting 1MB heap memory allocated.

Do you guys think, OS must be conservative about such allocations? An application with wrong memory expectation can affect the co-existence of other applications.

For Symbian signing recommendation has EikCmdExit handling is mandatory.