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

Add JEditorPane memory leak prevention #27

Closed
dany52 opened this Issue Jan 12, 2015 · 2 comments

Comments

Projects
None yet
2 participants
@dany52

dany52 commented Jan 12, 2015

JEditorPane registers different editorKits in sun.awt.AppContext
(see "SwingUtilities.appContextPut" strings in JEditorPane source)

something like

new JEditorPane("text/plain", "dummy");

will be enough to prevent this memory leak

@mjiderhamn

This comment has been minimized.

Show comment
Hide comment
@mjiderhamn

mjiderhamn Jan 24, 2015

Owner

I think I was a bit quick there. It would seem to me that this leak should already be handled by the library via it's call to javax.imageio.ImageIO.getCacheDirectory(), that also calls sun.awt.AppContext.getAppContext(). Do you see this leak even when using latest version of the library?

I have however updated the list of known offenders to include JEditorPane.

Owner

mjiderhamn commented Jan 24, 2015

I think I was a bit quick there. It would seem to me that this leak should already be handled by the library via it's call to javax.imageio.ImageIO.getCacheDirectory(), that also calls sun.awt.AppContext.getAppContext(). Do you see this leak even when using latest version of the library?

I have however updated the list of known offenders to include JEditorPane.

@dany52

This comment has been minimized.

Show comment
Hide comment
@dany52

dany52 Feb 3, 2015

I used version 1.11.0 when faced with this problem.
java javax.imageio.ImageIO.getCacheDirectory()not enough. I spent a lot of time trying to understand what's going on :)

dany52 commented Feb 3, 2015

I used version 1.11.0 when faced with this problem.
java javax.imageio.ImageIO.getCacheDirectory()not enough. I spent a lot of time trying to understand what's going on :)

@mjiderhamn mjiderhamn reopened this Feb 19, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment