Summary: | Memory leak in Jasper | ||
---|---|---|---|
Product: | JasPer | Reporter: | Alex Cherepanov <alex> |
Component: | Decoder | Assignee: | Henry Stiles <henry.stiles> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | christinedelight.top85, lars, masaki.ushizaka |
Priority: | P4 | ||
Version: | 1.701.0 | ||
Hardware: | PC | ||
OS: | Windows NT | ||
Customer: | Word Size: | --- | |
Attachments: | Sample file. |
Description
Alex Cherepanov
2007-05-10 18:23:54 UTC
Created attachment 6647 [details]
Sample file.
The file has been deleted from comparefiles/ as by the rev. 3210 as a duplicate to
the file in tests_public/pdf/ and later replaced with a new set of JP2 files
by the rev. r10177.
The leak is still there and it's proportional to the number of times the file runs. (In reply to comment #2) > The leak is still there and it's proportional to the number of times > the file runs. Yes I am looking at the code in jas_cm.c around line 194: default: if (!(iccprof = jas_iccprof_createfromclrspc(clrspc))) goto error; if (!(prof = jas_cmprof_createfromiccprof(iccprof))) goto error; #if 0 jas_iccprof_destroy(iccprof); #else prof->iccprof = iccprof; #endif if (!jas_clrspc_isgeneric(clrspc)) prof->clrspc = clrspc; break; } return prof; This doesn't make sense, iccprof should be destroyed and there should be no assigment to prof->iccprof, exactly the opposite of the conditional directive. jas_cmprof_createfromiccprofile() makes a copy of the profile passed in as a parameter and puts it in `prof'. Sigh, the leak is also fixed in jasper 1.9 I guess we never upgraded. A consultant is going to start integrating openjpeg shortly so I'm not going to attempt upgrading jasper. We don't use jasper anymore, closing. |