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 84941 - Duration informations lost during profiling
Summary: Duration informations lost during profiling
Status: RESOLVED WORKSFORME
Alias: None
Product: profiler
Classification: Unclassified
Component: Base (show other bugs)
Version: 5.x
Hardware: PC Windows XP
: P3 blocker (vote)
Assignee: J Bachorik
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-09-14 20:02 UTC by rbuss
Modified: 2007-08-13 17:00 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
profiler snapshot 1 (338.14 KB, application/octet-stream)
2006-09-14 20:04 UTC, rbuss
Details
Profiler snapshot 2 (340.07 KB, application/octet-stream)
2006-09-14 20:09 UTC, rbuss
Details
Netbeans 5.0 log (65.35 KB, application/octet-stream)
2006-09-15 10:59 UTC, rbuss
Details

Note You need to log in before you can comment on or make changes to this bug.
Description rbuss 2006-09-14 20:02:52 UTC
When profiling an application with option 'Analyze Performance' , 'Part of Application' with
filter 'Profile all classes' we could see that the duration of inner methods of the profiled
method got lost after a while.
There were no profiler error messages during the calculation of the profiled application. 
I will attach two snapshots. The first one shows the correct durations, second one misses durations
The interesting method is TimeSeriesSingleCobGenerationService.doFillTimeSeriesHistory(). In first
snapshot duration of this method is the sum of all child method durations.
In the second snapshot the sum of child durations is only about 10 percent. 
We reproduced this behaviour several times and increased the heap of the ide during this.
Is that an error or do we see something wrong ? The code is rather large. So I can send only the snapshots
Comment 1 rbuss 2006-09-14 20:04:59 UTC
Created attachment 33964 [details]
profiler snapshot 1
Comment 2 rbuss 2006-09-14 20:09:24 UTC
Created attachment 33965 [details]
Profiler snapshot 2
Comment 3 J Bachorik 2006-09-15 08:02:20 UTC
Could you, please, describe the exact steps to reproduce the behaviour?
Comment 4 rbuss 2006-09-15 10:02:14 UTC
Sorry. I cannot describe the actions we did in a more detailed way than:
'Profile Main Project', 'Analyze Performance' , 'Part of Application' with
method 'doFillTimeSeriesHistory', filter set 'Profile all classes' .
The whole action runs in a single thread. 
The application we profiled is rather large and uses several database tables
and views. So it is not possible to extract a small test program to be able
to reproduce. I was hopeful that anyone else had a similar problem.
Comment 5 J Bachorik 2006-09-15 10:08:13 UTC
And you do nothing regarding profiler between taking those two snapshots - just
take 2 successive snapshots? Correct?
Comment 6 rbuss 2006-09-15 10:58:07 UTC
Correct. I took 6 snapshots within 1 hour. We made this several times with
the same effect. I will attach the ide - logfile. Please have a look upon
the last lines. I think there is a profiler exception written.
Comment 7 rbuss 2006-09-15 10:59:12 UTC
Created attachment 33997 [details]
Netbeans 5.0 log
Comment 8 J Bachorik 2006-09-15 17:39:16 UTC
I still have no luck in reproducing the problem. 
I did some manual calculations and taking into account the ms/invocation ratio
it looks rather as multiplying the duration of the doFillTimeSeriesHistory()
method cca. 10 times than disappearing inner methods.
We will need to investigate the primary reason for this misbehaviour.
As no data is lost I would lower the priority to P3
Meanwhile, could you try upgrading your jdk to jdk1,5_08 - this release contains
numerous bugfixes durectly realated to profiler and let me know if the issue
persists?
Comment 9 rbuss 2006-09-21 11:57:22 UTC
Hi,
I tried the same profiling session with jdk1.5.0_08.
Unfortunately with the same results as before.
Comment 10 J Bachorik 2007-01-09 08:02:35 UTC
is it possible, by any chance, to get hands on your testing application?
Comment 11 Alexander Kouznetsov 2007-08-13 17:00:17 UTC
Closing due to no response on INCOMPLETE status. Please reopen if necessary.