https://bugzilla.novell.com/show_bug.cgi?id=403464 User rguenther@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=403464#c1 Richard Guenther <rguenther@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |290807 --- Comment #1 from Richard Guenther <rguenther@novell.com> 2008-06-24 16:30:15 MDT --- Interestingly this could fix bug #290807 as well. Citing from the debian changelog: * amd64, i386/local-clone.diff: restore patch to fix gij running out of memory, as it has been lost upstream. which doesn't mention the unwind issue at all. Same patch needed for i386. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=403464 User rguenther@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=403464#c3 --- Comment #3 from Richard Guenther <rguenther@novell.com> 2008-06-25 05:22:07 MDT --- See now also http://sources.redhat.com/bugzilla/show_bug.cgi?id=6693 -- 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.

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 <matz@novell.com> 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.

https://bugzilla.novell.com/show_bug.cgi?id=403464 Richard Guenther <rguenther@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Found By|--- |Development -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=403464 User swamp@suse.com added comment https://bugzilla.novell.com/show_bug.cgi?id=403464#c8 Swamp Script User <swamp@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status Whiteboard| |maint:released:11.0:21210 --- Comment #8 from Swamp Script User <swamp@suse.com> 2009-01-01 10:04:55 MST --- Update released for: glibc, glibc-devel, glibc-html, glibc-i18ndata, glibc-info, glibc-locale, glibc-obsolete, glibc-profile, nscd Products: openSUSE 11.0 (debug, i386, i686, ppc, ppc64, x86_64) -- 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.