[svn:osmf:] 11139: Extending class with a 'processLoadingState' stub, invoked when load state is set to LOADING.

Question

Revision: 11139
Author:   [email protected]
Date:     2009-10-26 03:02:38 -0700 (Mon, 26 Oct 2009)
Log Message:
Extending class with a 'processLoadingState' stub, invoked when load state is set to LOADING.
Modified Paths:
    osmf/trunk/framework/MediaFramework/org/osmf/media/LoadableMediaElement.as

Answer 1

Strobe was used to verify that the problem was not with my OSMF implementation. Since the results were the same, I am more supsicious of OSMF itself or the underlying AIR framework than the player implementation. Either way, the information I've seen says that progressive download of h.264 video is supported on mobile devices with AIR. It would appear that this is not true in all cases.
The issue has not been observed on not occur on the desktop. It only occurs with StageVideo enabled playback with autoplay on.
In the actual product the videos play one at a time. Once the user has finished with a video, the player clears the references to the media. These are OSMF calls; the media assigned to the player is nulled. If this is not sufficient for garbage collection, then I am at a loss as to how to proceed. My test uses four videos that are roughly 1 MB. If there is a memory use problem, then it would appear something is broken in AIR or OSMF.
I want to be sure I report this correctly. The code involved is more than a snippet, it's a media player designed to be embedded in an app. Do I need to include the complete implementation or will a description be sufficient?