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

Memory leak #74

Open
hig-dev opened this issue May 26, 2019 · 1 comment
Open

Memory leak #74

hig-dev opened this issue May 26, 2019 · 1 comment

Comments

@hig-dev
Copy link

hig-dev commented May 26, 2019

Steps to reproduce:

Hint: You have to enable native profiling and disable Just My Code in the memory profiling settings.

  1. Debug the sample app "VisualizationPlayer" with memory profiling
  2. Open a music file
  3. Force GC and make memory snapshot
  4. Repeatedly open the same or another music file. On every new opening of a music file the memory usage will increase. Do this 5-10 times.
  5. Force GC and make memory snapshot
  6. You will see that the memory usage has increased a lot.

Screenshot:
image

Link to diagsession (300MB):
https://send.firefox.com/download/f52b09a111a056c9/#2wL5zmgjieB-jPciQQTAcg

@hig-dev
Copy link
Author

hig-dev commented May 26, 2019

I now found the exact source of the memory leak, after opening a music file, a new ring buffer will be allocated and the old one won't be released from memory:
image

Better diagsession (275MB):
https://send.firefox.com/download/d5a2a65ca2046481/#ZZYWME7FDG5vUhWMZkZ5wg

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

1 participant