Searched refs:jpeg_destroy (Results 1 – 19 of 19) sorted by relevance
72 jpeg_destroy(j_common_ptr cinfo) in jpeg_destroy() function
75 jpeg_destroy(cinfo); in error_exit()
105 jpeg_destroy((j_common_ptr)cinfo); /* use common routine */ in jpeg_destroy_compress()
105 jpeg_destroy((j_common_ptr)cinfo); /* use common routine */ in jpeg_destroy_decompress()
1060 EXTERN(void) jpeg_destroy(j_common_ptr cinfo);
167 simply release it by calling jpeg_destroy().171 jpeg_destroy() can work on either type of object.471 the previous state of the object). Or you can call jpeg_destroy(), which475 of the passed pointer. To avoid gripes from ANSI C compilers, jpeg_destroy()479 it is your responsibility --- jpeg_destroy() won't. Ditto for the error493 jpeg_destroy_compress() or jpeg_destroy() to release memory. This is506 jpeg_destroy() and jpeg_abort() are the only safe calls to make on a JPEG591 call jpeg_destroy() when you are done with the JPEG object, or call719 jpeg_destroy_decompress() or jpeg_destroy(). The previous discussion of730 jpeg_destroy() if you don't need the JPEG object any more, or[all …]
411 * think that jpeg_destroy can do an error exit, but why assume anything...)
844 (typically via jpeg_destroy) upon abnormal termination. This may require a
46 jpeg_destroy @ 45 ;
45 jpeg_destroy @ 44 ;
43 jpeg_destroy @ 42 ;
61 jpeg_destroy(cinfo); in skjpeg_error_exit()
35 jpeg_destroy(cinfo); in CatchError()
81 jpeg_destroy(cinfo); in CatchError()
382 return CALLVJPEG(sp, jpeg_destroy(&sp->cinfo.comm)); in TIFFjpeg_destroy()
1263 jpeg_destroy((jpeg_common_struct*)(&(sp->libjpeg_jpeg_decompress_struct))); in OJPEGLibjpegSessionAbort()