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 254209 - Crash NB after Test all
Summary: Crash NB after Test all
Alias: None
Product: platform
Classification: Unclassified
Component: Output Window (show other bugs)
Version: 8.0
Hardware: PC Windows 7
: P3 normal (vote)
Assignee: Jaroslav Havlin
Depends on:
Reported: 2015-08-07 18:16 UTC by dynasource
Modified: 2015-10-29 13:36 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

IDE log (68.26 KB, text/plain)
2015-08-07 18:16 UTC, dynasource

Note You need to log in before you can comment on or make changes to this bug.
Description dynasource 2015-08-07 18:16:08 UTC
Product Version = NetBeans IDE Dev (Build nbms-and-javadoc-179-on-20150730)
Operating System = Windows 7 version 6.1 running on amd64
Java; VM; Vendor = 1.8.0_45
Runtime = Java HotSpot(TM) 64-Bit Server VM 25.45-b02

I've been having this issue since the early NB 6.0 now. There seems to be some Memory leak which causes Netbeans to shutdown when a project is being tested.
This testing is done as follows:

1) PHP unit + custom bat file
2) bat file executes external test framework
3) the output tab in NB is filled with the results

But occassionally, every day 4 or 5 times, I guess 1 every 50 times I execute this Test All (or test file, doesnt matter), NB crashes.
Very occassionally, I do even have BSOD, failing in Netbeans dll.
Something thats points to memory leakage is that Chrome sometimes also get killed, but not every time.

If you ask me where to put the finger, I would say it has something to do with the I/O in the Netbeans Output tab/window.
 I have now allocated 12GB of RAM but is still occurs.
Comment 1 dynasource 2015-08-07 18:16:14 UTC
Created attachment 155223 [details]
IDE log
Comment 2 Jaroslav Havlin 2015-08-14 13:18:17 UTC
> Something thats points to memory leakage 
Memory leaks in NetBeans usually cause OutOfMemoryErrors, not BSOD.

NetBeans IDE probably is not causing this OS crash.
Output Window is using a file-mapped memory, but via standard Java API. If access to this memory caused this problem, it would be an OS issue.

After some searching, it seems that there can be some hardware (or driver) problem:

Some similar cases:
   (invalid RAM memory)

   (problem with SSD driver)

Please try running some diagnostic tools (memory check) to ensure you computer is healthy first.
Thank you.
Comment 3 dynasource 2015-08-14 16:56:07 UTC
hi Jaroslav Havlin ,

thanks for your detailed answer.

In fact, I am making use of a RAM disk for all of my temporary files, including Netbeans.

Do you think the problem could be in there?
Comment 4 Jaroslav Havlin 2015-08-17 07:02:23 UTC
> In fact, I am making use of a RAM disk for all of my temporary files,
> including Netbeans.
> Do you think the problem could be in there?
If the memory is broken, it could cause this problem. Otherwise, it should work normally, I think.

I'm sorry, I'm not much experienced in this area - bugs that involve OS and possibly hardware.
Comment 5 dynasource 2015-08-18 07:17:40 UTC
it does seem to be faulty SSD. Firmware fixes for crucials M4 still dont seem to do the trick. After switching, I havent had this issue anymore.

thnx for pointing me in the right direction Jaroslav Havlin!
Comment 6 Jaroslav Havlin 2015-08-18 07:24:11 UTC
You are welcome. I'm glad it helped :-)
Comment 7 dynasource 2015-09-08 11:57:39 UTC
Unfortunately, my issue also exists when using other SSD drives.

Is there a way to get relevant data to post here?
Comment 8 Jaroslav Havlin 2015-09-09 09:17:24 UTC
I'm sorry, I have no other idea. I don't know what could be wrong.
Comment 9 Jaroslav Havlin 2015-10-29 13:36:05 UTC
Please see bug 256160, it may be related to the problem you reported.