ginal Message-----
>> From: flashcoders-boun...@chattyfig.figleaf.com
>> [mailto:flashcoders-boun...@chattyfig.figleaf.com] On Behalf Of mike
>> donnelly
>> Sent: 06 September 2009 11:17
>> To: Flash Coders List
>> Subject: Re: [Flashcoders] Rather urgent a
Paul Steven wrote:
Thanks Paul
The clients PC is a brand new one with 4gb RAM and I imagine tons of space.
Not sure what a stack dump looks like but the client did send this info on
the error:
Event Type: Error
Event Source: Application Error
Event Category: None
Event ID: 1000
Dat
Paul
>
> -Original Message-
> From: flashcoders-boun...@chattyfig.figleaf.com
> [mailto:flashcoders-boun...@chattyfig.figleaf.com] On Behalf Of mike
> donnelly
> Sent: 06 September 2009 11:17
> To: Flash Coders List
> Subject: Re: [Flashcoders] Rather urgent advice on how to tr
oders List
Subject: Re: [Flashcoders] Rather urgent advice on how to track the cause of
a crash
I would go and get your client's machine. 40 minutes is way too long
to test changes! If you can't do that, i would use a remote desktop
app. http://www.uvnc.com is a good one as far as i rem
I would go and get your client's machine. 40 minutes is way too long
to test changes! If you can't do that, i would use a remote desktop
app. http://www.uvnc.com is a good one as far as i remember, and it's
free.
Also, replace the huge picture with a little one, and get rid of the
video. Basicall
-
From: flashcoders-boun...@chattyfig.figleaf.com
[mailto:flashcoders-boun...@chattyfig.figleaf.com] On Behalf Of Paul Andrews
Sent: 05 September 2009 19:04
To: Flash Coders List
Subject: Re: [Flashcoders] Rather urgent advice on how to track the cause of
a crash
Paul Steven wrote:
> Tha
Paul Steven wrote:
Thanks Jason
The weird thing is the client has reported the problem occurring (ie it
crashing) within a few seconds of the game starting. It seems to be totally
random which is why I wasn't sure if a memory leak could be the cause.
You need to know the spec of that machine
;
> -Original Message-
> From: flashcoders-boun...@chattyfig.figleaf.com
> [mailto:flashcoders-boun...@chattyfig.figleaf.com] On Behalf Of Ian Thomas
> Sent: 05 September 2009 16:49
> To: Flash Coders List
> Subject: Re: [Flashcoders] Rather urgent advice on how to track the cause of
> a cra
[mailto:flashcoders-boun...@chattyfig.figleaf.com] On Behalf Of Ian Thomas
Sent: 05 September 2009 16:49
To: Flash Coders List
Subject: Re: [Flashcoders] Rather urgent advice on how to track the cause of
a crash
You may not be using Bitmap functions - but any filters etc. will use
them under-the-hood
g.figleaf.com
[mailto:flashcoders-boun...@chattyfig.figleaf.com] On Behalf Of Ian Thomas
Sent: 05 September 2009 16:49
To: Flash Coders List
Subject: Re: [Flashcoders] Rather urgent advice on how to track the cause of
a crash
You may not be using Bitmap functions - but any filters etc. will use
t
m but this does not seem to be
> possible.
>
> Cheers
>
> Paul
>
> -Original Message-
> From: flashcoders-boun...@chattyfig.figleaf.com
> [mailto:flashcoders-boun...@chattyfig.figleaf.com] On Behalf Of Ian Thomas
> Sent: 04 September 2009 19:22
> To: Flash Coders
-
From: flashcoders-boun...@chattyfig.figleaf.com
[mailto:flashcoders-boun...@chattyfig.figleaf.com] On Behalf Of Ian Thomas
Sent: 04 September 2009 19:22
To: Flash Coders List
Subject: Re: [Flashcoders] Rather urgent advice on how to track the cause of
a crash
On Fri, Sep 4, 2009 at 6:16 PM, Paul
25
To: Flash Coders List
Subject: RE: [Flashcoders] Rather urgent advice on how to track the cause of
a crash
>> It took me over 40 minutes of continuous play to get the crash.
This sounds like a memory leak - memory allocations building up for your
allotment in RAM over time, until it there
On Fri, Sep 4, 2009 at 6:16 PM, Paul Steven wrote:
> The game is basically a top down flying game with a scrolling background
> (JPG 5120 X 4320). The flash movie is published at 1600 x 1200 30 FPS. It
> includes an embedded FLV video on the Splash screen which is apparently
> 639kb of video data.
>> It took me over 40 minutes of continuous play to get the crash.
This sounds like a memory leak - memory allocations building up for your
allotment in RAM over time, until it there is no more available slots -
I would check all the usual things to be sure you are garbage
collecting, removing li
15 matches
Mail list logo
