Re: image-access memory leak
"Tim Bradshaw (as tfb at tfeb dot org)" <[email protected]>
| Newsgroups | gmane.lisp.lispworks.general |
|---|---|
| Message-ID | <[email protected]> |
I can confirm that, on macOS, lots of calls to this function (with the same image) leak a lot of memory, which does not show up in ROOM output that I can see. I tried some variants which also leak. > On 9 Jun 2025, at 15:05, Krupka Michal (as michal dot krupka at upol dot cz) <[email protected]> wrote: > > (defun test-load-image (path &optional vector) > (let* ((im (gp:load-image *test-pane* > (gp:read-external-image path) > :editable t)) > (vec (if vector > vector > (make-array (* (gp:image-height im) (gp:image-width im) 4) > :element-type '(unsigned-byte 8)))) > (acc (gp:make-image-access *test-pane* im))) > (gp:image-access-transfer-from-image acc) > (gp:image-access-pixels-to-bgra acc vec) > (gp:free-image-access acc) > (gp:free-image *test-pane* im) > vec))