search

diegoles / closure-library

Automatically exported from code.google.com/p/closure-library
0 stars 0 forks source link

SEVERE: Memory leak from Tracer.ThreadTrace when setTracerMode is set to OFF. #438

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 

What steps will reproduce the problem?
1. Disable your tracer via  
options.setTracerMode(CompilerOptions.TracerMode.OFF);      
2. Run compiler in a Java project.
3. Stop Tomcat 7 server.
4. View logs:

SEVERE: The web application [/translator] created a ThreadLocal with key of 
type [java.lang.ThreadLocal] (value [java.lang.ThreadLocal@62add0e8]) and a 
value of type [com.google.javascript.jscomp.Tracer.ThreadTrace] (value []) but 
failed to remove it when the web application was stopped. Threads are going to 
be renewed over time to try and avoid a probable memory leak.

4. MaxPermSize JVM setting helps mask the issue, but over time we have gotten 
OutOfMemory exceptions on our development and staging servers.

What is the expected output? What do you see instead?
No errors or memory leaks should be expected output, because the tracer should 
be disabled.

What version of the product are you using? On what operating system?
closure-compiler r1811

Please provide any additional information below.

Original issue reported on code.google.com by t...@sproutbuilder.com on 17 Mar 2012 at 12:17

GoogleCodeExporter commented 8 years ago 
Since this is likely a compiler issue, I have opened a corresponding bug in 
closure-compiler bug list:
http://code.google.com/p/closure-compiler/issues/detail?id=685

Meanwhile, marking this bug as WontFix.

Original comment by chrishe...@google.com on 20 Mar 2012 at 7:24