public inbox for frysk-bugzilla@sourceware.org
help / color / mirror / Atom feed
From: "mcvet at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: frysk-bugzilla@sourceware.org
Subject: [Bug general/3915] Memory leakage
Date: Wed, 07 Feb 2007 14:48:00 -0000 [thread overview]
Message-ID: <20070207144841.30676.qmail@sourceware.org> (raw)
In-Reply-To: <20070124155300.3915.mcvet@redhat.com>
------- Additional Comments From mcvet at redhat dot com 2007-02-07 14:48 -------
Created an attachment (id=1541)
--> (http://sourceware.org/bugzilla/attachment.cgi?id=1541&action=view)
finalize() log file
A quick initial assessment shows that StackFrame.java, FrameCursor.java, and
the private class UnwindArgs in StackTraceCreator.java never seem to get
collected, while other objects associated with stepping do.
The attached file is a log of finalize() calls from a variety of classes, some
from the DOM, Dwfl and DwflLine.
StackFrame is a pure Java file, FrameCursor and UnwindArgs have native
bindings; the DOM classes are pure Java and the Dwfl classes have native
bindings.
Failure to reach the finalize() for UnwindArgs means that native clean-up
functions like unw_destroy_addr_space are not called.
--
http://sourceware.org/bugzilla/show_bug.cgi?id=3915
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next prev parent reply other threads:[~2007-02-07 14:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-24 15:53 [Bug general/3915] New: " mcvet at redhat dot com
2007-01-24 15:53 ` [Bug general/3915] " mcvet at redhat dot com
2007-02-02 21:35 ` rmoseley at redhat dot com
2007-02-07 14:48 ` mcvet at redhat dot com [this message]
2007-02-08 20:41 ` mcvet at redhat dot com
2007-02-14 17:45 ` mcvet at redhat dot com
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=20070207144841.30676.qmail@sourceware.org \
--to=sourceware-bugzilla@sourceware.org \
--cc=frysk-bugzilla@sourceware.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: link
Be 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).