Namespaces

Variants
Actions

Please note that as of October 24, 2014, the Nokia Developer Wiki will no longer be accepting user contributions, including new entries, edits and comments, as we begin transitioning to our new home, in the Windows Phone Development Wiki. We plan to move over the majority of the existing entries over the next few weeks. Thanks for all your past and future contributions.

Archived:MTM components unloaded from memory after a period of inactivity

From Wiki
Jump to: navigation, search

Archived.pngArchived: 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}}.


Article Metadata
Compatibility
Platform(s): S60 3rd Edition
S60 3rd Edition (initial release)
Article
Created: User:Technical writer 2 (30 Mar 2007)
Last edited: hamishwillee (14 Jun 2012)

Overview

MTM components unloaded from memory after a period of inactivity

Description

MTM developers should be aware of a messaging server memory preservation rule that will unload unused MTM components after a period of five minutes. This can introduce unexpected problems with especially MTM UI components. In a scenario where the MTM UI opens a message into an editor or viewer component, and that component is open for more than 5 minutes, the underlying MTM UI can be unloaded by the messaging server.
This means that any handle to the MTM UI (if passed over to the editor/viewer) may not be valid when the edit/view process is completed.
Note also that even though the MTM UI component is unloaded from memory, the CMsvOperation-derived operation object that is returned for the edit/view operation will not get unloaded and can be trusted to be valid.

This page was last modified on 14 June 2012, at 07:05.
73 page views in the last 30 days.

Was this page helpful?

Your feedback about this content is important. Let us know what you think.

 

Thank you!

We appreciate your feedback.

×