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 244974 - Profile snapshot corrupted due to 100 frame limit
Summary: Profile snapshot corrupted due to 100 frame limit
Status: RESOLVED FIXED
Alias: None
Product: profiler
Classification: Unclassified
Component: Engine (show other bugs)
Version: 8.0.1
Hardware: PC Linux
: P3 normal (vote)
Assignee: Tomas Hurka
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-06-10 10:11 UTC by Jaroslav Tulach
Modified: 2014-07-11 08:56 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jaroslav Tulach 2014-06-10 10:11:21 UTC
When profiling programs with deep thread frames (like for example Nashorn scripts where one frame in JavaScript maps to 6-7 frames in Java), the profiler snapshot is confusing as it shows strange "roots".

This seems to be caused by taking just lowest 100 frames of the call and ignoring the rest. As a result the real root of the call is ignored and artificial roots appear.

One option is to increase the number of taken frames. Other is to adopt dynamically: whenever all requested frames are filled, ignore the query, double number and request again.
Comment 1 Tomas Hurka 2014-06-23 11:01:47 UTC
Fixed in profiler-main

changeset:   274562:9afecaf89990
user:        Tomas Hurka <thurka@netbeans.org>
date:        Mon Jun 23 12:53:24 2014 +0200
files:       lib.profiler/native/src-jdk15/Stacks.c
description:
bugfix #244974, MAX_FRAMES increased to 16384
Comment 2 Quality Engineering 2014-06-25 02:31:39 UTC
Integrated into 'main-silver', will be available in build *201406250001* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)

Changeset: http://hg.netbeans.org/main-silver/rev/9afecaf89990
User: Tomas Hurka <thurka@netbeans.org>
Log: bugfix #244974, MAX_FRAMES increased to 16384