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 66954 - VM complains about not being able to create the heap
Summary: VM complains about not being able to create the heap
Status: RESOLVED WORKSFORME
Alias: None
Product: profiler
Classification: Unclassified
Component: Base (show other bugs)
Version: 5.x
Hardware: PC Other
: P4 blocker (vote)
Assignee: issues@profiler
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-10-17 13:19 UTC by Jiri Sedlacek
Modified: 2011-02-03 11:45 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jiri Sedlacek 2005-10-17 13:19:24 UTC 
Reported by the user:

(M9, NB5.0, JDK 1.5.0_04 32bit Client VM, Windows 2003 server 64bit, 4GB RAM, 
dual Opteron processors, remote profiling)

"I have modified our batch script to include the -agent param that is required. 
The vm complains about not being able to creating the heap. I removed the -Xms 
and -Xmx params and everything works and I am able to profile from Netbeans. 
Putting the params back and removing the -agent param causes everything to work 
as well.

The max memory parameter is set to 1442M. I was able to get it to work at 
1024M."

"This issue is very easy to reproduce:

   1. Download the remote profiler dlls and jars.
   2. Select any application and set -Xms256M and -Xmx1426M and then add the 
profiling flag (-agentpath).
   3. Start the application and everything should work.
   4. Exit the application and change the -Xmx flag to 1427M and try to start 
the application. The VM should exit and complain about the heap."
Comment 1 iformanek 2005-10-18 14:11:08 UTC 
Is this reproducible on machines other than Windows 2003 Server?
Comment 2 iformanek 2005-10-20 16:59:10 UTC 
I've done some experiments, here are the results:

Win XP, 1GB RAM, JDK 5.0u4

1. with -client VM
- the VM complains if the -Xms/-Xmx is larger than 1398M

2. with -server VM
- the VM complains if the -Xms/-Xmx is larger than 1426M

In both cases, the same behavior occurs with *and* without the profiler agent, 
there is no difference in the behavior.

The error message is:

Error occurred during initialization of VM
Could not reserve enough space for object heap
Could not create the Java virtual machine.
Comment 3 Jiri Sedlacek 2005-10-20 18:06:58 UTC 
Tested on Fedora Core 4, 2GB RAM, 2x Opteron 64bit

JDK 1.5.0_04 64bit:

1. with -server VM
- the VM complains if the -Xms/-Xmx is larger than 5697M


JDK 1.5.0_05 32bit:

1. with -client VM
- the VM complains if the -Xms/-Xmx is larger than 3658M (3686M with agent)

2. with -server VM
- the VM complains if the -Xms/-Xmx is larger than 3684M (3684M with agent)
Comment 4 iformanek 2005-12-11 13:46:57 UTC 
Will not address in 1.0
Comment 5 Tomas Hurka 2009-04-08 12:56:04 UTC 
Milestone cleanup: future->next
Comment 6 Tomas Hurka 2011-02-03 11:45:53 UTC 
I am not able to reproduce it.