flex-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mihai Chira <mih...@apache.org>
Subject Re: What could cause Error #2015?
Date Thu, 15 Jan 2015 09:22:34 GMT
Bump. No ideas?

On 6 January 2015 at 11:34, Mihai Chira <mihai.chira@gmail.com> wrote:
> In our application we've been getting a bunch of reports of
> "ArgumentError: Error #2015 / at flash.display::BitmapData() / at
> ...etc." errors - thrown both in our custom code and in the SDK code.
> (The applications are AIR and run on PCs and Macs - non-mobile only.)
>
> Am I right in assuming that it's a case of the operating system
> refusing to allocate the memory required for the new BitmapData
> object? Could it be down to something else?
>
> PS: if the arguments to the BitmapData() constructor are wrong (either
> < 1, NaN, or their product is too large to allocate), the stack trace
> is "ArgumentError: Error #2015: Invalid BitmapData. / at
> flash.display::BitmapData/ctor() / at flash.display::BitmapData() / at
> ...etc.", so I imagine it's unrelated?

Mime
View raw message