With NetBeans 7.0 recently going into Beta 2 phase, now is the time to test it out properly and report issues. The development team has been squashing bugs, including memory issues with the PHP bundle.

There are some great new PHP related features in NetBeans 7.0, so you know you want to try it out.

If you identify something wrong with NetBeans, please report it following the guidelines http://wiki.netbeans.org/IssueReportingGuidelines

Depending on the issues, data to attach to the report is mentioned on: http://wiki.netbeans.org/FaqLogMessagesFile and http://wiki.netbeans.org/FaqProfileMeNow

If you have a memory issue then a memory dump would also be useful. Run the jmap tool for this. There is some background information on http://wiki.netbeans.org/FaqMemoryDump. Here's how I used it.

First I set my environment to match the JDK used by NetBeans. In my case I am using a nightly build so the JDK is in the configuration file under $HOME/netbeans-dev-201102210501:

$ egrep netbeans_jdkhome $HOME/netbeans-dev-201102210501/etc/netbeans.conf
netbeans_jdkhome="/home/cjones/src/jdk1.6.0_24"
$ export JAVA_HOME=/home/cjones/src/jdk1.6.0_24
$ export PATH=$JAVA_HOME/bin:$PATH

Next, I found the correct process number to examine:

$ ps -ef | egrep 'netbeans|jdk'
cjones   23230     1  0 16:07 ?        00:00:00 /bin/bash /home/cjones/netbeans-
cjones   23438 23230  2 16:07 ?        00:00:09 /home/cjones/src/jdk1.6.0_24/bin

Finally I used the parent JDK process as the jmap argument: