Archived:MIDlet may fail in deallocating the memory reserved for M3G graphics object in S60 3rd Edition (Known Issue)
Archived: This article is archived because it is not considered relevant for third-party developers creating commercial solutions today. If you think this article is still relevant, let us know by adding the template {{ReviewForRemovalFromArchive|user=~~~~|write your reason here}}.
The article is believed to be still valid for the original topic scope.
The article is believed to be still valid for the original topic scope.
Article Metadata
Tested with
Devices(s): Reproduced on Nokia N93 (sw version 20.0.058), Nokia N95 (sw version 11.0.026)
Compatibility
Platform(s): S60 3rd Edition, S60 3rd Edition FP1
Article
Created: User:Technical writer 1
(26 Sep 2007)
Last edited: hamishwillee
(28 Jun 2012)
Overview
MIDlets may fail in deallocating the memory reserved for an M3G graphics object, and the application crashes when allocating too many 3D objects.
Description
Sometimes MIDlets fail in deallocating the memory reserved for an M3G graphics object. Because of this, allocating too many new 3D objects might crash the application. For example, using the Loader.load("filename.m3g") method iteratively can cause the M3G application to crash with (or without) an OutOfMemory error message. When the MIDlet tries to allocate memory from the heap by using memory which should be automatically deallocated but is instead still allocated, the application crashes.
Solution
Reuse the created 3D objects and minimize the amount of loaded objects.
(no comments yet)