2009/1/17 Jasper van de Gronde
<th.v.d.gronde@...528...>
J.B.C.Engelen@...1578... wrote:
> The windows build has become very unstable the last few weeks. I'm
> working on it, and hope to have found the cure soon.
> Sorry :-(
> Johan
I've also been looking into it. My guess is that the problem (if it is
just one) was introduced between 28-12 and 04-01, because three of the
rendering tests suddenly started crashing during that period.
At least one of the tests crashes in Path::AddPoint (the pts.push_back
line) in Path.cpp (while being called during Glyph rendering, I can
provide more details if needed). I haven't looked closely at the other
three, but it is at least suspicious that all three tests have text in
them (while pretty much all other tests don't).
The "crash on start" bug seems to crash inkscape right AFTER calling
(and exiting) the first idle loop. I haven't looked deeper into this,
but from what I'm seeing I'm guessing there is some memory
corruption/initialization issue. This could also explain the different
behaviour on different platforms.
------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
Inkscape-devel mailing list
Inkscape-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/inkscape-devel