[CONTROLLER-1466] Memory leak during controller run Created: 07/Jan/16  Updated: 19/Oct/17  Resolved: 08/Jan/16

Status: Resolved
Project: controller
Component/s: config
Affects Version/s: Helium
Fix Version/s: None

Type: Bug
Reporter: ankit Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


External issue ID: 4889

 Description   

I freshly checked out the code for controller and changed to stable/hydrogen branch. after the successful build, when i start the controller, it reports the following issue.

"2016-01-07 16:30:29.813 IST [nettyThreadgroupModule$NioEventLoopGroupCloseable-6-1] ERROR io.netty.util.ResourceLeakDetector - LEAK: ByteBuf.release() was not called before it's garbage-collected. Enable advanced leak reporting to find out where the leak occurred. To enable advanced leak reporting, specify the JVM option '-Dio.netty.leakDetectionLevel=advanced' or call ResourceLeakDetector.setLevel()
"

Please have a look at this. I am new to this project so there is a possibility that i raised this bug with limited information.

-Ankit Kumar



 Comments   
Comment by Vratko Polak [ 07/Jan/16 ]

> Version: Helium
> changed to stable/hydrogen branch

So which one, Hydrogen or Helium?
Either way, I believe both release trains are not supported anymore.
Please use Lithium-SR3 release, Lithium snapshots (stable/lithium branch) or Beryllium snapshots (master branch currently).

Comment by Tony Tkacik [ 08/Jan/16 ]

stable/hydrogen branch is not supported since release of Helium (2014-09).

This bug was fixed in subsequent releases and release trains.

Comment by Robert Varga [ 08/Jan/16 ]

I will note that Helium has also been desupported.

Generated at Wed Feb 07 19:55:37 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.