Nape Physics.: Features/Development » Article on a memory issue we tracked very recently.

Members

Help

Home

Home » Nape Physics » Features/Development » Article on a memory issue we tracked very recently. (And how rubbish the VM can be sometimes.)

Show: Today's Messages :: Show Polls :: Message Navigator

E-mail to friend

Article on a memory issue we tracked very recently. [message #2101]

Sun, 26 February 2012 04:45

dELtaluca
Messages: 2228
Registered: July 2010
Location: Malden Rushett, Surrey

Senior Member
Administrator

http://jpauclair.net/2012/02/25/epic-memory-track-down/

It's certainly an interesting read and he has gone very deep into the heart of the issue.

For a summary, we track that doing:

var anon:*;
for(var i:int = 0; i<1000000; i++)
   anon = 3.3;

every frame, will allocate 'megabytes' of memory per second due to the untyped nature of the variable.

this is the simplest example found.

Please also vote on the bug report at adobe.

https://bugbase.adobe.com/index.cfm?event=bug&id=3123526 Shocked

[Updated on: Fri, 11 May 2012 00:28]

I created nape!

Report message to a moderator

Re: Article on a memory issue we tracked very recently. [message #2520 is a reply to message #2101]

Wed, 04 April 2012 00:05

dELtaluca
Messages: 2228
Registered: July 2010
Location: Malden Rushett, Surrey

Senior Member
Administrator

The bug has now been verified by Adobe and marked as ToTrack meaning a fix won't be coming in next release (aka 11.2 which was just released) but is known and will be fixed at some point... yay I guess.

I created nape!

Report message to a moderator

Previous Topic:	Nape + Stage3D = Premium Feature = %9 royalty for Adobe?
Next Topic:	Cutting demo - as3

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Sat May 25 08:50:28 BST 2013

Total time taken to generate the page: 0.07561 seconds

.:: Contact :: Home ::.