Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pupil Player 3.5.8 memory leak #2232

Open
ZdenekM opened this issue Apr 19, 2022 · 1 comment
Open

Pupil Player 3.5.8 memory leak #2232

ZdenekM opened this issue Apr 19, 2022 · 1 comment

Comments

@ZdenekM
Copy link

ZdenekM commented Apr 19, 2022

On a machine with Ubuntu 20.04 and 20 GB of RAM, I'm experiencing problems with Pupil, which memory consumption is growing while playing video. When I open htop I can see how MEM% raises by 0.1% every two seconds until the memory is exhausted. Is there some log I could provide or anything else which may help to debug this issue? Thanks.

@papr
Copy link
Contributor

papr commented Apr 21, 2022

Hi,

Yes, Pupil Player can be quite hungry for memory. There are various factors that influence the amount of required memory. Recording length and the type of enabled plugins are the two most influential ones.

Could you let us know the length of your recording and which plugins you are using?

It is also known that Player allocates further memory as it buffers frames in the background to ensure smooth playback. The deallocation of the frames is subject to the garbage collector which we do not call explicitly.

That said, I had a look at Player's memory consumption in the past. Unfortunately, the tools that I encountered only provided insight about the total amount of memory, not about specific parts of the software. This newly released software promises to change that: https://bloomberg.github.io/memray/

Currently, it is only available on Linux and I won't have access to a Linux machine until the 2nd of May. If you have the time to setup and run Pupil Capture from source, then it would be helpful if you could make a memray recording while performing your described use case.

Best,
Pablo

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants