[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gnash-dev] Re: Unexpected exception during rendering calls

From: strk
Subject: Re: [Gnash-dev] Re: Unexpected exception during rendering calls
Date: Thu, 16 Nov 2006 11:11:41 +0100

On Thu, Nov 16, 2006 at 11:06:02AM +0100, Markus Gothe wrote:
> For printing out a chart kcachegrind will do the work as a front-end for 
>  callgrind which is part of the valgrind suite, long story short 
> 'apt-get install kcachegrind'. ;)

I've used 'massif' with valgrind.
See bug #18309, seems a problem with AGG.
I suggest you guys try with another renderer to see if this
case is AGG-specific.


> Rob Savoye wrote:
> >strk wrote:
> >>Well, if we're taking too much memory we can't really tell
> >>when we'll going to run out of it. I guess a proper approach
> >>would be producing a diagram of where most memory goes,
> >
> >  While mudflap won't print out a chart, it will tell you about every
> >access to see if there is a problem. Often I've seen bugs that trash the
> >stack create various weird errors, hiding the original problem. I also
> >have some code that instruments the malloc buffers in the kernel, which
> >can also be useful at times like this.
> >
> >     - rob -

reply via email to

[Prev in Thread] Current Thread [Next in Thread]