This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 62438 - ResourceBundle instances not shown
Summary: ResourceBundle instances not shown
Status: CLOSED DUPLICATE of bug 62476
Alias: None
Product: profiler
Classification: Unclassified
Component: Base (show other bugs)
Version: 4.x
Hardware: PC Windows ME/2000
: P3 blocker (vote)
Assignee: iformanek
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-08-17 03:57 UTC by fuege
Modified: 2007-02-20 18:08 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Test app (without package path!) (2.32 KB, application/octet-stream)
2005-10-21 18:16 UTC, fuege 		Details
Test app (without package path!) (2.32 KB, application/octet-stream)
2005-10-21 18:17 UTC, fuege 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description fuege 2005-08-17 03:57:44 UTC 
I wonder why my ResourceBundle instances are not displayed on the results list 
when I'm chosing "Analyzing memory usage|Record object creation only|Track 
every 1 allocation".

My bundles are classes named like the following:
tld.domain.project.resources.ProjectResources
tld.domain.project.resources.ProjectResources_en
and the like.

Don't know if its a) a bug or b) a decision (to filter some stuff implicitly).
It's not really critical, but raises the question "What else might be missing?".

So, if b) is true, I'd like to know about the profiler's strategy to filter.
Comment 1 iformanek 2005-10-21 15:41:51 UTC 
For memory profiling, no classes are filtered out. This sounds like a bug of 
some sort. Are you sure that the instances of those classes are created? Are 
the resource bundle classes on the application classpath?

Perhaps if there was a small test app that the problem would be reproducible 
with it would be much easier for us to hunt down the problem.
Comment 2 fuege 2005-10-21 18:10:37 UTC 
Yes and Yes.

Please try the test app attached (note: the Res.Bundle classes are located in a 
subpackage, but I don't think that's critical).

In the LiveResult list I usually filter for e. g. "tld.domain.project", but 
none of my bundle instances appears.

Looking for "java.util.Locale", you'll see the growing "Allocated Instances", 
but neither "java.util.ResourceBundle" nor "java.util.ListResourceBundle" 
instances are shown (but: some inner classes of Res.Bundle 
like "java.util.ResourceBundle$1" etc.).
Comment 3 fuege 2005-10-21 18:16:14 UTC 
Created attachment 26233 [details]
Test app (without package path!)
Comment 4 fuege 2005-10-21 18:17:13 UTC 
Created attachment 26234 [details]
Test app (without package path!)
Comment 5 fuege 2005-10-21 18:20:16 UTC 
Sorry, duplicated the attachment by mistake.
Comment 6 iformanek 2005-11-22 18:09:18 UTC 
The reason for this is that the resource bundle instances are allocated 
dynamically via the Class.newInstance call, which th ememory profiling 
currently does not track. The other issue that you filed covers the root cause 
for this, marking this one as a duplicate.

*** This issue has been marked as a duplicate of 62476 ***
Comment 7 ehucka 2006-10-09 12:10:36 UTC 
Verification of old issues.
Comment 8 Alexander Kouznetsov 2007-02-20 10:20:23 UTC 
Closing old issues
Comment 9 Alexander Kouznetsov 2007-02-20 18:08:50 UTC 
Reverting to original Target Milestone value changed by mistake. Sorry for
inconvenience.