Memory issue when Loading an asset with URLRequest from a remote location
I just noticed something odd today while profiling: when I do this: var loader:Loader = new Loader();loader.load( new URLRequest( fileUrl ) ); If the fileUrl is loaded from a relative url directly on...
View ArticleRe: Memory issue when Loading an asset with URLRequest from a remote location
That's definitely strange behavior, and something we want to look at. Please file a bug over at http://bugbase.adobe.com/. If you have a simplified example with source, that would help expedite an...
View ArticleRe: Memory issue when Loading an asset with URLRequest from a remote location
Hi Jeromie, I just opened a bug report here https://bugbase.adobe.com/index.cfm?event=bug&id=3496291I also attached a working example. Thanks.
View ArticleRe: Memory issue when Loading an asset with URLRequest from a remote location
Thanks! I've escalated this to the engineering team, and we're investigating now.
View ArticleRe: Memory issue when Loading an asset with URLRequest from a remote location
Hi Lorenzo, Can you provide me your system information and include information such as OS, browser, etc. so I can attempt to reproduce the issue?
View ArticleRe: Memory issue when Loading an asset with URLRequest from a remote location
Hi Robert, no problem, I already included this information in the bug ticket too. Test Configuration My Hardware and Environment details:Windows 7, Firefox, Chrome, IE, Flash Player 1.5 and Flash...
View ArticleRe: Memory issue when Loading an asset with URLRequest from a remote location
I just noticed the bug has been marked as cannot reproduce... This is a video of the issue to help the engineers find it http://screencast.com/t/asu22peG9KZT Let me know if they need more info.
View ArticleRe: Memory issue when Loading an asset with URLRequest from a remote location
Thanks. I had two different people look at it, and neither is seeing it. I've added your video and reopened it for investigation.
View ArticleRe: Memory issue when Loading an asset with URLRequest from a remote location
Lorenzo, One of the people that tested this and I both looked at this and tried to follow your video step-by-step (using Adobe tools) and we can't actually get your SWF to render in Chrome.When we...
View ArticleRe: Memory issue when Loading an asset with URLRequest from a remote location
Hi Jeromie,I compiled my SWF with FlashDevelop 4.2.0 and FlashPlayer 11.3. I checked the tests (local and remote) you sent me and they both seems to use same memory.I am a little puzzled :/ Although...
View ArticleRe: Memory issue when Loading an asset with URLRequest from a remote location
Yeah, we tried on both a Mac and Win7. We *are* testing with the currently available version of Flash Player, which is 11.6.602.167. It's already late here, but I'll look at this tomorrow myself....
View ArticleRe: Memory issue when Loading an asset with URLRequest from a remote location
No problem, thank you for looking into this. Tomorrow I will do some extratests to see if I can find anything different.
View ArticleRe: Memory issue when Loading an asset with URLRequest from a remote location
This is another video taken with 11.6 and using an JPG instead of a SWF, built in release mode and using the FlashDevelop profiler, you can still see some difference between the 2, not as much as SWF...
View ArticleRe: Memory issue when Loading an asset with URLRequest from a remote location
Okay, I spent a bunch of time looking at this today. I like Flash Pro much better than the other tools, so everything is just a FLA now. I've included copies of the examples, SWFs and Scout Files...
View ArticleRe: Memory issue when Loading an asset with URLRequest from a remote location
I understamd, The snippet of code I wrote is just to describe how I am getting it, we are not using that in the specific, in a real case I would be loading different files, not the same one over and...
View ArticleClik here to view.
Re: Memory issue when Loading an asset with URLRequest from a remote location
My guess is that we're not allocating buffers for the network transfer in the filesystem case. Because the Loader object is passed off directly to the displaylist, it never really gets deallocated,...
View Article
