Skip to content
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

Vulture threads appearing in JRuby v1.7.16.1 #2351

jsgoecke opened this issue Dec 27, 2014 · 0 comments

Vulture threads appearing in JRuby v1.7.16.1 #2351

jsgoecke opened this issue Dec 27, 2014 · 0 comments


Copy link

@jsgoecke jsgoecke commented Dec 27, 2014

On Dec 27, 2007 the vulture thread in the ObjectProxyCache was commented out with "vulture daemon thread prevents finalization, find alternative approach":


The issue is, on JRuby v1.7.16.1 we are seeing what might be a thread leak with the format of:

"ObjectProxyCache 75 vulture"
"ObjectProxyCache 16 vulture"
"ObjectProxyCache 60 vulture"

What is strange, is that the checkin changes the thread name as follows:

-        vulture = new Thread("ObjectProxyCache vulture") {
+        this.vulture = new Thread("ObjectProxyCache "+id+" vulture") {

And then commented out calling it. Two things. First, why would the developer change the name and then comment it out? Second, we are actually seeing the new format in our thread list, not the old one before it was commented out. I have searched the JRuby codebase, and see the only place that vultures is referenced is here:

This is private, although with reflection you might be able to get at it. But we are not calling it anywhere in our Java code or Ruby scripts. And yet it is appearing in our thread list.

Any ideas on how this might be getting spawned regardless?

@jsgoecke jsgoecke changed the title Vulture threads appearing in JRuby v1.7.8 Vulture threads appearing in JRuby v1.7.16.1 Dec 27, 2014
@jsgoecke jsgoecke closed this Dec 27, 2014
@enebo enebo added this to the Invalid or Duplicate milestone Jan 30, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
None yet

No branches or pull requests

2 participants