Revision as of 06:46, 8 April 2015 by Stwr (Talk | contribs)


Mini NetCAT for redesigned Profiler in NetBeans 8.1


Due to the fact that profiling features in NetBeans IDE are used in other products and the support went through an user interface redesign recently it is important to have this core functionality tested as early as possible. That's why the former NetCAT 8.0 team was asked for help. This page contains all relevant information about this testing initiative.


ID Name Expertise Team Bugs/RFEs filed Test completed by
1 Michal Konrad Owsiak Unknown B [michal.owsiak] 02.04.2015
2 Alied Pérez Martínez Seasoned A [alied]
3 John McDonnell Novice C [satory]
4 James Hamilton Novice B [wjdhamilton]
5 Giuseppe Tino Novice C [-Silver-]
6 Hermien Pellissier Unknown B [mienamoo]
7 Angelo Quaglia Seasoned A [aquaglia]
8 Scott Palmer Unknown A [swpalmer]
9 Emmanuel Hugonnet Unknown A [ehsavoie]
10 Nigel Broadhead Novice C [nigel]
11 Eric Barboni Novice B [skygo]
12 Luca Mambretti Novice A [IrianR]
13 Marek Cendrowicz Novice C [stwr]
14 Richard Kolb Novice B [rjdkolb]
15 Kent Grundström Seasoned A [Chiana]
16 Cezariusz Marek Novice A [cezariusz]
17 Supun Liyanage User B [supunliyanage]
18 Yonathan W'Gebriel Novice C [ytn01]
19 Ahmad Hosny Novice C [thruminds]
20 Goutham Bandri Novice B [gokumar]
21 Rashmi Dixit Novice C [rashmidixit]


The testing must not be too detailed as we need feedback within 1-2 weeks but by April 18th at the latest. Every volunteer was assigned to a certain team. Everyone should download the latest development build of the NetBeans IDE and then with the help of Profiler 8.1 Redesign FAQs test the profiling features according to the following assignment:

  • Volunteers from Team A should use their own projects and with the redesigned NetBeans Profiler try to identify potential performance issues in these projects.
  • Volunteers from Team B should use BrainTeaser sample project and with the redesigned NetBeans Profiler try to identify potential slowness and its cause.
  • Volunteers from Team C should use MemoryLeakOrNot? sample project and with the redesigned NetBeans Profiler try to identify potential memory leaks in provided examples (some of them expose memory leaks, some of them not, but please let others discover that themselves).

Identified problems

Once every participant finishes her/his testing, s/he is required to summarize and record her/his findings into the following table:

Priority Issue Short summary Evaluation
P3 #251599 Profile button is not drawn correctly (shadow covers only half of it)
P2 #251607 Cannot open Java source using Build 201504020001
P3 #251610 Runtime exception when trying to save view of CPU Comparison as image Reproduced only so far
P3 #251687 NPE when trying to Profile Class 'External process' should not be in the list of the projects to profile
P3 #251688 Runtime exception when exiting the profiler session Unfortunately thrown randomly
P3 #251689 Both actions 'Profile Class' and 'Profile Method' do not make sense Not a bug, concern only
P3 #251693 NPE when taking a Thread Dump Caused by JDK bug
P3 #251695 Methods table does not contain any entries Invalid
P3 #251696 No hits for valid profiling point when profiling the class Caused by JDK bug
Not logged in. Log in, Register

By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2012, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo