public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "thebohemian at gmx dot net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libgcj/26063] New: memory leak in _Jv_Linker::link_symbol_table Date: Wed, 01 Feb 2006 13:44:00 -0000 [thread overview] Message-ID: <bug-26063-10268@http.gcc.gnu.org/bugzilla/> (raw) My patch for PR 24616 introduced a memory leak in _Jv_Linker::link_symbol_table because some ffi structures and a String are not reachable by the garbage collector. It was decided to accept this problem because the above mentioned patch got bigger and bigger. -- Summary: memory leak in _Jv_Linker::link_symbol_table Product: gcc Version: 4.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libgcj AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: thebohemian at gmx dot net http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26063
next reply other threads:[~2006-02-01 13:44 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-02-01 13:44 thebohemian at gmx dot net [this message] 2006-02-01 14:43 ` [Bug libgcj/26063] " pinskia at gcc dot gnu dot org 2006-02-01 16:52 ` thebohemian at gmx dot net 2006-02-01 16:57 ` aph at gcc dot gnu dot org 2006-02-01 18:32 ` tromey at gcc dot gnu dot org 2006-02-02 12:06 ` thebohemian at gmx dot net 2006-02-02 12:10 ` aph at gcc dot gnu dot org 2006-02-02 12:52 ` [Bug libgcj/26063] memory leak in _Jv_Linker::link_symbol_table & ffi usage breaks build on ARM thebohemian at gmx dot net 2006-02-02 12:56 ` thebohemian at gmx dot net 2006-02-02 12:56 ` pinskia at gcc dot gnu dot org 2006-02-02 19:26 ` thebohemian at gmx dot net 2006-02-04 2:50 ` [Bug libgcj/26063] memory leak in _Jv_Linker::link_symbol_table tromey at gcc dot gnu dot org 2006-02-08 20:07 ` tromey at gcc dot gnu dot org 2006-02-08 20:10 ` tromey at gcc dot gnu dot org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-26063-10268@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).