Created attachment 94049 [details]
stacktrace

Created attachment 97201 [details]
stacktrace

show allocation stack traces from profiler memory snapshot

Can you, please, provide steps how to reproduce it? Thanks.

- create Anagram sample project;
- start memory profiling (Record both object ... + Record stack trace ...);
- stop profiling and go to snapshot;
- right click on com.toy.anagrams.ui.Anagrams and Show Allocation stack traces;
->NPE 

http://statistics.netbeans.org/exceptions/exception.do?id=387304

Created attachment 99039 [details]
stacktrace

Applikation im Profiler (memory) gestartet
Applikation ist normal beendet worden 
Erstellung eines Speicherprofil
Erstellung des Aufrufstapel
=> Absturz

I am sorry, but the steps are still not clear to me. What do you mean by 
> - stop profiling and go to snapshot

Does it mean to quit Anagram sample via 'File -> Exit' in Anagram and than take the snapshot in 'Application Finished' dialog displayed by profiler or
take snapshot first and that invoke 'Profiler -> Stop profiling session'?
I tried the first variant and I was not able to reproduce it. :-(

*** Bug 187537 has been marked as a duplicate of this bug. ***

I do a memory profile
I do a right click on the byte[] node 
I chose show Allocation stack trace
I got NPE

I cannot save the results either

This works for me. Can you be more specific about (In reply to comment #8)
> I do a memory profile
> I do a right click on the byte[] node 
> I chose show Allocation stack trace
> I got NPE
> 
> I cannot save the results either

This works for me. Can you be more specific? Can you provide sample application, which can be used to reproduce it?

It happens always
this is my netbeans.conf

# ${HOME} will be replaced by JVM user.home system property
netbeans_default_userdir="${HOME}/.netbeans/6.8"

# Options used by NetBeans launcher by default, can be overridden by explicit
# command line switches:
netbeans_default_options="-J-client -J-Xverify:none -J-Xss2m -J-Xms32m -J-XX:PermSize=48m -J-XX:MaxPermSize=3000m -J-Dapple.laf.useScreenMenuBar=true -J-Dsun.java2d.noddraw=true -Xmx1g --laf javax.swing.plaf.metal.MetalTheme -J-Xmx1024m -J-XX:+UseConcMarkSweepGC -J-XX:+CMSClassUnloadingEnabled -J-XX:+CMSClassUnloadingEnabled"
# Note that a default -Xmx is selected for you automatically.
# You can find this value in var/log/messages.log file in your userdir.
# The automatically selected value can be overridden by specifying -J-Xmx here
# or on the command line.

# If you specify the heap size (-Xmx) explicitely, you may also want to enable
# Concurrent Mark & Sweep garbage collector. In such case add the following
# options to the netbeans_default_options:
# -J-XX:+UseConcMarkSweepGC -J-XX:+CMSClassUnloadingEnabled -J-XX:+CMSPermGenSweepingEnabled
# (see http://wiki.netbeans.org/wiki/view/FaqGCPauses)

# Default location of JDK, can be overridden by using --jdkhome <dir>:
netbeans_jdkhome="/usr/java/latest"

# Additional module clusters, using ${path.separator} (';' on Windows or ':' on Unix):
#netbeans_extraclusters="/absolute/path/to/cluster1:/absolute/path/to/cluster2"

# If you have some problems with detect of proxy settings, you may want to enable
# detect the proxy settings provided by JDK5 or higher.
# In such case add -J-Djava.net.useSystemProxies=true to the netbeans_default_options.

maybe it's jdk-specific
For me it's not reproducible on jdk 1.6.0_16 but reproducible on 1.6.0_18

I switched back from 1.6.0_20 to 1.6.0_16 and the problem disappeared

Maybe it is somehow related to issue #183107.

Created attachment 100927 [details]
stacktrace

This bug already has 20 duplicates 
see http://statistics.netbeans.org/exceptions/detail.do?id=165106

Created attachment 100932 [details]
stacktrace

This looks like duplicate of issue #183107. Reopen if you are able to reproduce it with JDK 1.6.0_21.