| Summary: | Leaks monitor objects | ||
|---|---|---|---|
| Product: | Ghostscript | Reporter: | Tim Waugh <twaugh> |
| Component: | Color Management | Assignee: | Michael Vrhel <michael.vrhel> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | chris.liddell |
| Priority: | P4 | ||
| Version: | 9.14 | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Customer: | Word Size: | --- | |
| Attachments: | ghostscript-pthread-leak.patch | ||
I hadn't seen this report, and this was fixed as a result of working on related issues from another source. But yes, Tim, you are exactly right - thanks! |
Created attachment 10969 [details] ghostscript-pthread-leak.patch In gsicc_manage.c, gx_monitor_alloc() is used to allocate profile->lock but gs_free_object() is used to free it. Shouldn't gx_monitor_free() be used for this (patch attached)?