Lines Matching refs:jpeg_destroy
165 simply release it by calling jpeg_destroy().
169 jpeg_destroy() can work on either type of object.
469 the previous state of the object). Or you can call jpeg_destroy(), which
473 of the passed pointer. To avoid gripes from ANSI C compilers, jpeg_destroy()
477 it is your responsibility --- jpeg_destroy() won't. Ditto for the error
491 jpeg_destroy_compress() or jpeg_destroy() to release memory. This is
504 jpeg_destroy() and jpeg_abort() are the only safe calls to make on a JPEG
589 call jpeg_destroy() when you are done with the JPEG object, or call
717 jpeg_destroy_decompress() or jpeg_destroy(). The previous discussion of
728 jpeg_destroy() if you don't need the JPEG object any more, or
1480 clean up the JPEG object with jpeg_abort() or jpeg_destroy().
1597 term_destination() is NOT called by jpeg_abort() or jpeg_destroy(). If you
1675 term_source() is NOT called by jpeg_abort() or jpeg_destroy(). If you want
2596 (jpeg_destroy also releases the storage, of course.)
2789 state; or just call jpeg_destroy() if you don't need to reuse the object.