https://bugzilla.novell.com/show_bug.cgi?id=403464
User matz@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=403464#c5
--- Comment #5 from Michael Matz 2008-06-25 08:55:19 MDT ---
And just for reference, the whole topic is discussed starting at:
http://gcc.gnu.org/ml/gcc/2006-12/msg00293.html
The theory for why this creates a memleak in java is, that one thread
does a backtrace (for whatever reason) and stores the places somewhere.
Due to glibc having the patch adding cfi directives, but libgcc_s not
having the patch for the unwinder this creates an endless loop, hence
that thread stores the same info again and again, probably appending to
a list or something. So everything continues to work, just that one thread
sucks up memory. That's only a theory, though.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.