Is there a memory leak

[hxcliff]

[hxcliff]

It seems that memory is not freed after calling get_text() or get_image().

[hxcliff]

It seems that other platforms are the same

I set_image a picture of about 5 mb size about 8 or 9 times, the whole program about 67mb. then found that the memory area 0x53e32400000-0x53e36000000 is basically the content of this picture data about 60mb. then there are some CLIPBOARD, CLIPBOARD_ MANAGER, ARBOARD_CLIPBOARD strings. I wonder if there is some memory leak or memory not freed in time.

A comparison of the memory when the program is opened and after the completion of the set_image test shows that there is a clear exception in 53e32400000.

[hxcliff]

The memory dump file is here http://47.100.174.226:8080/s/vmIj

[ArturKovacs]

Thanks for reporting this! I think I'll get to this after sorting out #23

[hxcliff]

Thanks for reporting this! I think I'll get to this after sorting out #23

okay

[hxcliff]

Hi, any progress so far?

[ArturKovacs]

Unfortunately not. On that note: I'm intending to stop working on this crate.

[hxcliff]

Unfortunately not. On that note: I'm intending to stop working on this crate.

Oh, not good news. Maybe I'll try to maintain one myself

[hxcliff]

My share-clip project relies heavily on this crate

🥲

[ArturKovacs]

I would definitely consider merging a PR if you find a solution to this.

[mchaliadzinau]

@morn-0 was you able to find the issue? I think I've run into this issue but for get_text() as well (have not tried get_image yet...).

[hxcliff]

was you able to find the issue? I think I've run into this issue but for get_text() as well (have not tried get_image yet...).

Sorry, I haven't had the chance to delve deeper into this issue recently.

[complexspaces]

I am going to close this issue since I'm not aware of any more memory leaks in arboard. All of the macOS ones have been removed (and tested) in previous releases. Thanks for reporting this before.