question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Potential memory leak in ProbeScheduler

See original GitHub issue

Description

On one of the Che master instances, I’ve noticed potentially high memory consumption. 15 29 58 Heap dump shows one object with ~ 1.2G. 15 21 16 Deep dive show that this is 15139 TimterTask in ProbeScheduler 15 22 11 AFAIK this probes should be ~ NUM of workspecase * num of servers.

From what I can find number of workspaces ~500-700 15 23 00

The goal of this task is to

  • study if that was expected to see TimterTask in ProbeScheduler can take 1.3 G
  • Make sure that fields probeThread and httpUrlConnection in HttpProbe are not cousing any leak and should/can be dereferenced.

Reproduction Steps

OS and version:

Diagnostics:

Issue Analytics

  • State:closed
  • Created 5 years ago
  • Reactions:1
  • Comments:14 (9 by maintainers)

github_iconTop GitHub Comments

1reaction
garagatyicommented, Dec 20, 2018

@ibuziuk If it is TimeoutTask that bugs the memory then something like this diff should help https://github.com/eclipse/che/compare/master...garagatyi:probeMemoryLeak?expand=1 But if it is not only that task but something else in addition then we would need to investigate additionally.

0reactions
ibuziukcommented, Jan 2, 2019

Merged into master and part of 6.16.0 release. Closing

Read more comments on GitHub >

github_iconTop Results From Across the Web

Understanding Memory Leaks in Java - Baeldung
A memory leak is bad because it blocks memory resources and degrades system performance over time.
Read more >
Potential memory leak? - Stack Overflow
But I am wondering whether there is a memory leak here? Arguably, yes, this is still a leak since it (temporarily) uses more...
Read more >
Configuring the memory leak policy - IBM
You can configure a leak detection, prevention, and action policy to accommodate your applications and environment so that potential memory leaks are ...
Read more >
How to Detect Memory Leaks in Java: Causes, Types, & Tools
Excessive usage of static fields can potentially lead to a memory leak. In Java, static fields usually remain in memory as long as...
Read more >
Debugging Spring Boot Applications for Memory Leaks
Finding memory leaks in Java applications can be tricky. ... One could potentially use a memory profiling tool to track down the memory...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found