If I'm not mistaken, the default VM size is now 64MB (previously 16MB).
I know this is the case for the plug-in. I'd hope that it's the same
for both.
-j
Mona Wong wrote:
>
> > When I am executing the following Code I am getting the following error
> > java.lang.OutOfMemoryError <>
> >
>
> When I am executing the following Code I am getting the following error
> java.lang.OutOfMemoryError <>
>
> How can optimize this code and Improve the Performance.
One way is to allocate more memory to java by using the -mx flag. For
example:
java -mx64m jdend
Cheers,
M
This has been our #1 headache with running applets in the plug-in.
The user has to manually change it. I heard rumors that in a future
release of the plug-in that it would pick a memory size based on
what the machine actually has available. What a concept
In a memory intensive API like Jav
Ravi,
You need to increase the Java heap size to execute your program,
eg. java -Xmx128m Foo ( type "java -X" for more info. )
As of performance and memory footprint issues, you should download
the latest java3d1.3beta1 release.
To download Java 3D, Version 1.3, Beta 1, go to:
I've had some issues with running out of resources in conjunction with
manipulating BranchGroups and Shape3ds as well under J3D 1.2.
For context, the app I have is used for terrain visualization using a
quadtree
to determine which tiles are visible when compared to the view frustum.
This culling
"b. white" wrote:
>
> Please don't suggest -Xmx or -Xmx this is not my problem
>
> First Thanks Justin for letting me know that swing componets hog more
> memory than awt components, I haven't switched over yet to check this out
> for myslef but I will try it.
Mainly due to the way that Swi
JayT wrote:
>
> I have a rather large app with many items in the scenegraph and
> having an OutOfMemoryError is not uncommon to me. It IS quite
> frustrating. I try to design optimized code and utilize the command
> line optimizations and I've come to the conclusion that it's going to
> be a par
I have a rather large app with many items in the scenegraph and
having an OutOfMemoryError is not uncommon to me. It IS quite
frustrating. I try to design optimized code and utilize the command
line optimizations and I've come to the conclusion that it's going to
be a part of my code. The thing
Try looking in the java3d faq (j3d.org) and the archives of this mail list.
the solution is to increase the memory allocated to the jvm by including a
statement like -Xmx200m (to allocate 200 meg)
-Original Message-
From: b. white [mailto:[EMAIL PROTECTED]]
Sent: Friday, June 30, 2000 11
