<html>
    <head>
      <base href="https://bugs.freedesktop.org/" />
    </head>
    <body>
      <p>
        <div>
            <b><a class="bz_bug_link 
          bz_status_NEW "
   title="NEW - Assertion "(_cairo_atomic_int_get (&(&surface->ref_count)->ref_count) > 0)""
   href="https://bugs.freedesktop.org/show_bug.cgi?id=91967#c5">Comment # 5</a>
              on <a class="bz_bug_link 
          bz_status_NEW "
   title="NEW - Assertion "(_cairo_atomic_int_get (&(&surface->ref_count)->ref_count) > 0)""
   href="https://bugs.freedesktop.org/show_bug.cgi?id=91967">bug 91967</a>
              from <span class="vcard"><a class="email" href="mailto:alberts.muktupavels@gmail.com" title="Alberts Muktupāvels <alberts.muktupavels@gmail.com>"> <span class="fn">Alberts Muktupāvels</span></a>
</span></b>
        <pre>Created <span class=""><a href="attachment.cgi?id=118325" name="attach_118325" title="cairo-xlib-surface: set image to NULL after destroying it">attachment 118325</a> <a href="attachment.cgi?id=118325&action=edit" title="cairo-xlib-surface: set image to NULL after destroying it">[details]</a></span> <a href='page.cgi?id=splinter.html&bug=91967&attachment=118325'>[review]</a>
cairo-xlib-surface: set image to NULL after destroying it

Please consider applying this simple patch.

Trying to destroy surface for second time results in assertion which ends with
crash. And that is serious problem.

Image at that point is already destroyed and not valid so setting it to NULL is
safe. That will prevent from trying to destroy surface for second time and more
importantly I can handle this error now in code: I can use cairo_surface_status
and/or cairo_status to detect this failure.</pre>
        </div>
      </p>
      <hr>
      <span>You are receiving this mail because:</span>
      
      <ul>
          <li>You are the QA Contact for the bug.</li>
      </ul>
    </body>
</html>