It's very possible all the times Cairo crashed it was the cause of corrupted memory from something else... But of course not every library is so sensitive to that stuff. Either way don't read too much into it... it's just a vague impression I've built over the years.
Also, after comments from Simon, I'm even more excited about GLPlot/GLVisualize than I was before, and it will probably fill the needs nicely. (fingers crossed! :) On Wednesday, September 16, 2015, Andreas Lobinger <[email protected]> wrote: > OK. My experience is a little bit different. One thing is, cairo is not > very tolerant to pointer trouble. While other toolkits just silently > discard uncorrect pointers, cairo complains. > > On Wednesday, September 16, 2015 at 7:51:05 AM UTC+2, Tom Breloff wrote: >> >> I've just seen so many core dumps that happen within Cairo over my >> career. They may not be Cairo's fault, but I've just gotten it in my head >> that it can be a little unstable at times. YMMV >> >> On Wed, Sep 16, 2015 at 1:21 AM, Andreas Lobinger <[email protected]> >> wrote: >> >>> >>> On Tuesday, September 15, 2015 at 6:01:37 PM UTC+2, Tom Breloff wrote: >>> >>>> I know very little about it, but it could possibly be faster and more >>>> stable than Cairo for 2D graphics, with a lighter dependency footprint. It >>>> is a C++ package, so this is something that will depend on a stable Cxx.jl. >>>> >>> >>> Could you clarify what you mean with "more stable than Cairo for 2D >>> graphics"? >>> >>
