NegativeArraySizeException

[Slaxmi Raj]

when i run this program,i got the "NegativeArraySizeException" ,please tell me How can i reduce this?

public class HugeArray {

	
	public static void main(String[] args) {
		
int n=1000;
int a[]=new int[n*n*n*n];
for(int i=0;i<a.length;i++)
{
	a[i]=i;
	System.out.println(a[i]);
}	}

}

[dennis deems]

The size of an array can not be larger than http://docs.oracle.com/javase/6/docs/api/java/lang/Integer.html#MAX_VALUE

Everything else you need to know can be found at the web site where that code was copied:
http://introcs.cs.princeton.edu/java/14array/HugeArray.java.html

[Seetharaman Venkatasamy]

int n=1000;
int m = n*n*n*n;
System.out.println(m);//overflow

[Anayonkar Shivalkar]

The maximum length of an array in Java can be Integer.MAX_VALUE. Even if you try to declare an array which is that large in size, chances are that you'll get OutOfMemoryError - a single such array will take approx. 4.3GB of memory.

Apart from that, I'm just thinking - what kind of application requires such a huge array (having length of 1 trillion - which will take 1TB of memory)

[Henry Wong]

Anayonkar Shivalkar wrote:The maximum length of an array in Java can be Integer.MAX_VALUE. Even if you try to declare an array which is that large in size, chances are that you'll get OutOfMemoryError - a single such array will take approx. 4.3GB of memory.

Apart from that, I'm just thinking - what kind of application requires such a huge array (having length of 1 trillion - which will take 1TB of memory)

Actually, each int element takes 4 bytes, so such an array will require (in the ballpark range of) 4 times the 1TB of memory....

Henry

[Anayonkar Shivalkar]

Yes

It will take 4TB of memory. In real life, I've never seen a machine with 4TB of RAM (rather this code will need 4TB of 'JVM' itself)

[Campbell Ritchie]

We have all been on about arrays too large. But the question was not about arrays too large. It was about arrays too small. I know exactly why it was too small, but does Slaxmi Raj?

[dennis deems]

Campbell Ritchie wrote:We have all been on about arrays too large. But the question was not about arrays too large. It was about arrays too small. I know exactly why it was too small, but does Slaxmi Raj?

He does if he followed the Princeton link, and read and understood the source of the unattributed code he copied and pasted in his post.

[Slaxmi Raj]

thank you so much for your explanation. Iam beginer in java, this is competitive question.

[Campbell Ritchie]

If it is competitive, you ought to produce an answer.

[Rob Spoor]

Anayonkar Shivalkar wrote:Yes

It will take 4TB of memory. In real life, I've never seen a machine with 4TB of RAM (rather this code will need 4TB of 'JVM' itself)

It doesn't need 4TB of physical RAM - the OS can use swap files for the data that does not fit into memory. However, this will significantly decrease performance as the disk will be accessed quite a bit for the swapping.

[Henry Wong]

Rob Spoor wrote:

Anayonkar Shivalkar wrote:Yes

It will take 4TB of memory. In real life, I've never seen a machine with 4TB of RAM (rather this code will need 4TB of 'JVM' itself)

It doesn't need 4TB of physical RAM - the OS can use swap files for the data that does not fit into memory. However, this will significantly decrease performance as the disk will be accessed quite a bit for the swapping.

"significantly decrease performance" is an understatement. The garbage collector and the swap file system are, in my opinion, mortal enemies. The job of swap is to put the least recently used pieces of memory out to disk. And the garbage collector's job is to find the garbage, which generally are the least recently used pieces -- not to mention that it needs to traverse all of memory (as the Sun/Oracle implementation does GC when the heap is full).

IMO, never ever run a JVM with swapped memory !!!

Henry