Hi Mark,

Can you make some test code you're working on, so I can join to debug 
process.

Thank you.
Eugene

On Friday, June 8, 2012 5:13:04 PM UTC+2, Mark Essel wrote:
>
> I've been bugging TJ on node-canvas (https://github.com/LearnBoost/ 
> node-canvas/issues/177#issuecomment-6154062<https://github.com/LearnBoost/node-canvas/issues/177#issuecomment-6154062>)
>  
> about a code speed up I'm 
> working on in a fork of his node module. 
>
> I found Canvas.toBuffer() to be killing our pipeline resources and 
> created an alternative that would simply convert from Canvas into an 
> Image without going through a png buffer/media url. The problem is 
> that cairo is a mysterious beast, and there's an additional level of 
> concern about memory allocated within node modules as not to get GC'd 
> by mother v8. 
>
> I was able to test the Canvas.loadImage(image) method thousands of 
> times on my mac setup (6.18), as well as stand alone tests on our 
> ubuntu/production servers running the same version of node. But when 
> the code is run as a stand alone process/server and coordinated by 
> Gearman I'm getting some "interesting" memory/segfaults. 
>
> I've tried recreating the problem and running it with gdb, node_g, and 
> all the node modules built with symbols and debug flags. But the error 
> crops up in a lib outside of the source I can get a stack trace for. 
>
> Any help, pro tips, assistance, or words of encouragement would be 
> appreciated.

-- 
Job Board: http://jobs.nodejs.org/
Posting guidelines: 
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

Reply via email to