On 1/21/15, 2:41 AM, "Mihai Chira" <mihai.ch...@gmail.com> wrote:
>In my tests if I add an argument < 0 (in fact, < 1), the stack trace >of the RTE comes out with "at flash.display::BitmapData/ctor()", as I >mentioned. So I assumed that when the stack trace doesn't include the >ctor() function (which I guess is the C constructor) the cause is >different (most likely memory issues?) Don’t know. It could also be different player and swf versions give different stack traces. Is there a common caller to BitmapData() on the stack trace? You could try adding logging of what it passes and maybe available memory. -Alex
