-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Possible memory leak when using nonStandardResolutions in JavaFX #432
Comments
Hi @bogey4, I did a little profiling and it seems that old gen is clogged by the |
With this change memory consumption should be much smoother. Also rendering speed should perform faster on HD720p. |
I noticed that many heavy objects are created in runtime by JavaFX. These are rasters and images which are being held by the JFX internals. Not sure how to get rid of them. |
Sarxos, thanks for looking into this issue. I pulled the changeset referenced above, but still have the same issue, wherein the objects are surviving indefinitely (see attached profiler image). Is there any path forward to resolve this, or is the leak to remain? Again, thanks for your excellent work on this project. It's greatly appreciated! |
Hi @bogey4, Can you find out what are the objects that are clogging your memory? I used Eclipse Memory Analyzer (MAT) for this. First I'm doing heap dump from I'm almost sure those memory clogs are created by JavaFX, so I think you can definitely get rid of this problem by not rendering live image preview from JavaFX, but use |
I have adapted the CustomResolutionExample.java example to work with the webcam-capture-javafx example, and have encountered a potential memory leak. This was observed by profiling memory consumption in Netbeans 8.0.2 with java 1.8.60, and noticing that the Surviving Generations was constantly increasing. There was no such issue observed when the setCustomViewSize and setViewSize methods were not called.
To recreate:
Please let me know if I can clarify further.
The text was updated successfully, but these errors were encountered: