Lines Matching full:jpeg_destroy
164 simply release it by calling jpeg_destroy().
168 jpeg_destroy() can work on either type of object.
468 the previous state of the object). Or you can call jpeg_destroy(), which
472 of the passed pointer. To avoid gripes from ANSI C compilers, jpeg_destroy()
476 it is your responsibility --- jpeg_destroy() won't. Ditto for the error
490 jpeg_destroy_compress() or jpeg_destroy() to release memory. This is
503 jpeg_destroy() and jpeg_abort() are the only safe calls to make on a JPEG
588 call jpeg_destroy() when you are done with the JPEG object, or call
716 jpeg_destroy_decompress() or jpeg_destroy(). The previous discussion of
727 jpeg_destroy() if you don't need the JPEG object any more, or
1319 clean up the JPEG object with jpeg_abort() or jpeg_destroy().
1435 term_destination() is NOT called by jpeg_abort() or jpeg_destroy(). If you
1512 term_source() is NOT called by jpeg_abort() or jpeg_destroy(). If you want
2433 (jpeg_destroy also releases the storage, of course.)
2626 state; or just call jpeg_destroy() if you don't need to reuse the object.
2807 or jpeg_destroy() for any active JPEG objects. A handler is not needed with
