please report an issue with the code snippet to https://bugs.adobe.com/jira/browse/FM .
SMP was not designed and certified against such usage - so the problem could be in yorur code, SMP, OSMF, AIR or undelying Flash. I would bet on the fact that the downloaded assets are not cleaned from the memory when you end the playback. I would suggest to try streaming assets for low-memory systems as the portable devices, not progressive.
Could you replicate the issue on AIR on desktop?
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?
Ideally a snippet replicating the issue is the best thing to attach to a bug report. If not (and the code is secret), a description would be enough - this will allow us to make a simple app to replicate it, when we start investigating the bug.
I would say that it's not an OSMF bug, but an AIR issue on that device.
I have reported the issue in the Strobe project in the bug tracker as suggested. If it is an AIR issue, should I report it elsewhere or will it be transferred internally? I do have a workaround I can put in place until AIR and the development tools are updated, so my project can continue at least.