Out of memory Error with jdk 1.6

Hello,
I have a swing application launched on the client with the help of Java web start. The applications works fine in jre 1.4 and jre 1.5. The heap sizes are :
initial-heap-size="5m" max-heap-size="24m"
But when I run this using jre 1.6.0_05-b13, I am getting Out of memory Error, java heap size. And I see the memory usage is growing rapidly which I didn't notice in other jre versions (1.4 and 1.5).
Does anyone have any idea on this?
Thanks in advance,
MR.

Thanks for your response Peter. During my continuous testing I identified that error happens on jdk 1.5 also. And I have increased the min-heap-size to 24 MB and max-heap-size to 64 MB. But in that case also I noticed the out of memory error. The interesting thing is, the min-heap-size is never increased from 24MB and lot of free memory also.
Memory: 24,448K Free: 12,714K (52%) ... completed.
The Outofmemoryerror triggers from the reader thread which does the job of reading the data from the InputStream. One thing is we are continuously pushing more data on the output stream from the other end. Is that any limitation on InputStream which can hold some definite amount of data.
Please throw some light on this.

Similar Messages

Out of memory error with 80Kb file?

Hi, my pc has 2Gb of Ram, a page file that is setup correctly
and the physical ram is almost non-used (500Mb)
When I start DW and load a php file of 80Kb approx., it just
hangs/locks up. When I wait for it, it gives me an "out of memory"
error, and when you look in windows task manager, it just keeps
hogging up ram.
My laptop is a "simple", 1Gb Hp pavillion, and when I open
the file there, it just works like it's supposed to, using about
70Mb of ram, instead of the gigabyte(s) it does on my developer
machine....
Adjusting virtual memory has absolutely no effect.. It seems,
after some reading, that people using 2gb of ram, have the most
problems in this area?
Adobe, please help here !
EDIT: i just tested another file, 136Kb large, that loads
normal!, so it has to do with the files in specific... If you want
to test the files, just download "Simplemachines Forum" and load
the "load.php" or the "post.php" files from the source directory,
to trigger the lockup...

mmm... just tried using a "workaround" if you still can call
it that
Installed a virtual machine (xp) with less than 2gigs, and it
works... I really hope someone else has got these kind of errors
yet.... 2500$ + software, wich I can't use for now... Using
notepad2 for time being...

Java heap out of memory error with -Xms1g -Xmx4g 64 bit VM

We are getting Java Heap memory error for the application we are running on linux 64 bit machine (VM).
The OOM came when heap usage was 1.7gb though we have specified min as 1gb and max as 4gb. If I understand correctly then it should not have been thrown as we have specified max as 4gb. If address space was the problem then it should have thrown swap space error.
Also, there were no other processes running on this node.
Below are the specifics of linux node we are using:
linux kernel: 2.6.18-128.el5
Linux Version: Red Hat Enterprise Linux Server release 5.3 (Tikanga) 64 Bit
Ulimts
[ppoker@aquariusvir11 ~]$ ulimit -a
core file size (blocks, -c) unlimited
data seg size (kbytes, -d) unlimited
scheduling priority (-e) 0
file size (blocks, -f) unlimited
pending signals (-i) 139264
max locked memory (kbytes, -l) unlimited
max memory size (kbytes, -m) unlimited
open files (-n) 100000
pipe size (512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
real-time priority (-r) 0
stack size (kbytes, -s) 10240
cpu time (seconds, -t) unlimited
max user processes (-u) 139264
virtual memory (kbytes, -v) unlimited
file locks (-x) unlimited
Java Version
[ppoker@aquariusvir11 ~]$ java -version
java version "1.6.0_21"
Java(TM) SE Runtime Environment (build 1.6.0_21-b06)
Java HotSpot(TM) 64-Bit Server VM (build 17.0-b16, mixed mode)
Kernel Semaophores
[ppoker@aquariusvir11 ~]$ ipcs -l
------ Shared Memory Limits --------
max number of segments = 4096
max seg size (kbytes) = 67108864
max total shared memory (kbytes) = 17179869184
min seg size (bytes) = 1
------ Semaphore Limits --------
max number of arrays = 128
max semaphores per array = 250
max semaphores system wide = 32000
max ops per semop call = 32
semaphore max value = 32767
------ Messages: Limits --------
max queues system wide = 16
max size of message (bytes) = 65536
default max size of queue (bytes) = 65536
Please suggest what could be the reason for this error.
Thanks,
Ashish

javaguy4u wrote:
the OOM error ... wasn't coming when we had set min and max both as 4 GB.You deviously withheld that information.
When the JVM needs to grow the heap it asks the OS for a bigger memory block than the one it has.
The OS may refuse this and the JVM will throw an OOME.

Out of memory error with last jvm

Hi,
i have written a program which run perfectly under java jre 1.4.2_03. But when I test it with the last java jre 1.4.2_05, I get a java.lang.OutOfMemoryError. Is there something different in the JVM?
I have log out the garbage collector for the both JVM and it shows me that with the last java release the memory allocated is fully increasing. Trying to allocate more heap memory to the jvm do not change anything.
Have any one an idea? or encounterd this problem?
here is the listing from java142_03:
[GC 511K->93K(1984K), 0.0158240 secs]
[GC 17915K->16431K(25580K), 0.0235110 secs]
[GC 18095K->16550K(25580K), 0.0187630 secs]
[GC 18214K->16511K(25580K), 0.0095240 secs]
[GC 18175K->16541K(25580K), 0.0100360 secs]
[GC 18205K->16598K(25580K), 0.0085490 secs]
[GC 18261K->16677K(25580K), 0.0088590 secs]
Here is the listing from java142_05
[GC 8652K->8347K(9012K), 0.0165860 secs]
[Full GC 8347K->8347K(9012K), 0.5212970 secs]
[GC 9435K->8789K(15068K), 0.0167740 secs]
[GC 9877K->9222K(15068K), 0.0187010 secs]
[GC 10310K->9654K(15068K), 0.0184040 secs]
[GC 10742K->10084K(15068K), 0.0196390 secs]
[GC 11172K->10511K(15068K), 0.0203420 secs]
[Full GC 14101K->14101K(15196K), 0.7232510 secs]
[GC 15643K->14695K(25200K), 0.2429610 secs]
[GC 22448K->22157K(25200K), 0.0621640 secs]
[GC 23757K->23582K(25200K), 0.0506020 secs]
[GC 25182K->24892K(26608K), 0.0644240 secs]
[Full GC[Unloading class sun.reflect.GeneratedMethodAccessor16]
24892K->24892K(26608K), 1.1170130 secs]
[GC 27695K->27186K(44560K), 0.4203820 secs]
[GC 42058K->41883K(44816K), 0.0457160 secs]
[Full GC 41883K->40172K(44816K), 2.3119850 secs]
[GC 44268K->43989K(65088K), 0.0923610 secs]
[GC 48085K->47342K(65088K), 0.1587490 secs]
[GC 51438K->50693K(65088K), 0.1573160 secs]
[GC 54789K->54044K(65088K), 0.1593800 secs]
[GC 58140K->57396K(65088K), 0.1578900 secs]
[Full GC 61492K->60747K(65088K), 2.5820780 secs]
[Full GC 65087K->64298K(65088K), 2.6938250 secs]
[Full GC 65087K->64944K(65088K), 2.6716200 secs]
[Full GC 65087K->63781K(65088K), 3.4285840 secs]
[Full GC 64664K->64504K(65088K), 2.6915320 secs]
[Full GC 64504K->64504K(65088K), 2.6798100 secs]

Maybe your program's memory usage is rubbing against the upper limit, and something about the latest JVM caused it to break through.
Try using the command line parameter -mx500m (for 500 megs or whatever amount you neeed)

Out of memory error - large project

I'm consulting on a feature doc edit, and the primary editor (Avid guy) is having serious problems accessing anything from the original project.
It's an hour and 15 minute show, with probably close to 100 hours of footage.
The box is a D2.3 G5 with 1.5 g of RAM, and the media is on two G-Tech drives: a G-RAID and a G-Drive. Plenty of headroom on both (now) and the system drive is brand new, having been replaced after the original died, and there's nothing loaded on it but FC Studio. The FCP version is 5.1.4. The project file is well over 100 MB.
We started getting Out of Memory errors with this large project, and I checked all of the usual suspects: CMYK graphics, hard drive space, sufficient RAM... all checked out okay, except possibly the less-than-ideal amount of RAM.
I copied the important sequences and a couple of select bins to a new project, and everything seems workable for now. The project is still 90 MB, and I've suggested breaking it up into separate projects and work on it as reels, but we can edit and trims work efficiently at the moment. However, the other editor has gotten to a point now where he can't even open bins in the old, big project. He keeps getting the OOM error whenever he tries to do anything.
I have no similar problems opening the same project on my G5, which is essentially identical except I have 2.5 G RAM (1 G extra). Can this difference in RAM really make this big a deal? Is there something else I'm missing? Why can't this editor access even bins from the other project?
G4 Mac OS X (10.2.x)

Shane's spot on.
What I often do with large projects is pare down, just what you have done. But 90 out of 100 is not a big paredown by any stretch. In the new copy throw away EVERYTHING that's outdated: old sequences are the big culprit. Also toss any render files and re-render.
Remember that, to be effective fcp keeps EVERYTHING in ram, so that it can instantly access anything in your project. The more there is to keep track of the slower you get.

"out of memeory" error with Adobe Reader x & IE8

Hello,
Getting an "out of memory" error with Adobe Reader X & IE8. This is a locked down bank environment so upgrading to a higher version of Adobe is out of the question.
I looked around on the web and noticed that many people are experiencing this "out of memory error" but no fix has been provided.
Can you help?

Thanks for the reply and suggestion - unfortunately, I get this error when I open Adobe Reader X itself in addition to launching a pdf within IE9 (my OS is Win7x64 Ultimate). I can launch Adobe Reader X, but when I open any kind of PDF file (local copy, remote, web, etc...) the error dialog box pops up. Everything seems functional with Reader, it's just a frustrating (er, irritating!) thing! I think after the weekend I will 'give up' and remove the Reader X and go back to my 'old' (but functioning!) Reader - thanks for the comment and suggestion tho!

Overcoming Out of Memory Error

hi, i need to initialize a 3 dimensional array at
[21] [21] [500,000] = 220,500,000 * 8 bytes = 1,764,000,000 = 1.764 Gig
its currently at 1/100 the size
[21] [21] [5000] = 2,205,000 * 8 bytes = 17,640,000 = 17 Meg
and working fine.
I am getting an Out of Memory error with anything much higher.
What is the max i can set the OS (windows 2000 or Xp) to accept?
Thanks Alot!

haha, thanks guys (or girls). thats what i figured.
this is actually a graphing program that is reading in
long strangely formatted files (3,000 lines)
sorting and arranging them and then plotting them.
Every plot requires at least 40 columns all with the same length
(always above 2000).
Someone persists that 5,000 plot points isnt enough so im
humoring them and looking in to make it bigger.
id think about plotting off the files themselves but in XP the
plotting is ridiculously slow as it is. we're talking 2 or 3 second refreshs
to load a jpanel with the plot.
I think ill just let the user reconfigure WHERE the length will be
as in, enter,
[x] [y] [z] so you can do [ 1] [40] [ 55,000 ] or whatever
as opposed to the standard [21][21][5000].
thanks for your responses!

Jrockit out of memory error

We are getting out of memory error with jrockit1.4.2_08. We used memory debugger tools to find the leak. Apparently there do not seem to be a leak from application perspective. Here is the core dump. Please help me resolve this.
===== BEGIN DUMP =============================================================
JRockit dump produced after 0 days, 05:37:55 on Thu Jun 5 20:39:11 2008
Additional information is available in:
/opt/obs/obs_app/obs31.0/user_projects/admin/jrockit.17430.dump
No core file will be created because core dumps have been
disabled. To enable core dumping, try "ulimit -c unlimited"
before starting JRockit again.
If you see this dump, please open a support case with BEA and
supply as much information as you can on your system setup and
the program you were running. You can also search for solutions
to your problem at http://forums.bea.com in
the forum jrockit.developer.interest.general.
Error code: 52
Error Message: Null pointer exception in native code
Signal info : si_signo=11, si_code=2
Version : BEA WebLogic JRockit(TM) 1.4.2_08 JVM R24.5.0-61 ari-49095-20050826-1856-linux-ia32
Threads / GC : Native Threads, GC strategy: parallel
: mmHeap->data = 0x40416000, mmHeap->top = 0x7ec16000
: mmStartCompaction = 0x45236000, mmEndCompaction = 0x4a056000
CPU : Intel Pentium 4 (HT)
Number CPUs : 4
Tot Phys Mem : 4021997568
OS version : Red Hat Enterprise Linux ES release 2.1 (Panama)
Linux version 2.4.9-e.72smp ([email protected]) (gcc version 2.96 20000731 (Red Hat Linux 7.2 2.96-129.7.2)) #1 SMP Tue Jul 3 22:04:51 EDT 2007
State : JVM is running
Command Line : -Djava.class.path=<my own jars list>
java.library.path=/opt/obs/wls/jrockit-j2sdk1.4.2_08/jre/lib/i386/jrockit:/opt/obs/wls/jrockit-j2sdk1.4.2_08/jre/lib/i386:/opt/obs/wls/jrockit-j2sdk1.4.2_08/jre/../lib/i386:/opt/mqm/java/lib:/opt/tib/rv7.1.2/lib:/opt/obs/obs_app/obs31.0/thirdparty:/opt/obs/wls/wls8.1sp3/weblogic81/server/lib/linux/i686:/opt/obs/wls/wls8.1sp3/weblogic81/server/lib/linux/i686/oci920_8
C Heap : Good; no memory allocations have failed
Registers (from context struct at 0x8d5b724/0x8d5b80c):
EAX = 000005f4 EBX = 0000007f
ECX = 7ff8bd90 EDX = 24a18f94
ESI = 7ff46af0 EDI = 00000100
ESP = 7f262bc0 EIP = 4026d58f
EBP = 7f262bd8 EFL = 00010203
CS = 0023 DS = 002b ES = 002b
SS = 002b FS = 00df GS = 00df
Stack:
7f262bc0 :00000000 7ff46af0 00000f94 00000000 00028000 00000000
7f262bd8 :7f262c08 401ffcae 7ff8bd90 24a18f94 00028000 a0000000
7f262bf0 :0a5f1800 7f262c74 08d137a0 00000050 00000000 7f262c34
7f262c08 :7f262c48 4028a7fb 24a18f94 00000000 08d137a0 08d139e4
7f262c20 :581a664c 00000003 08d137a0 00000001 7f262c74 00000000
7f262c38 :7f262ca8 402c28bd 7f262c74 20040144 7f262ca8 402c292f
7f262c50 :7f262c74 00000000 00000000 7f262c84 581a6640 08d137a0
7f262c68 :08d1382c 414d2db8 210d41e8 0a5f1800 08d137a0 7f262d9c
7f262c80 :24a18f95 00000002 00000000 7f262cf8 08d1382c 581a6640
7f262c98 :00000000 00000000 00000000 00000000 7f262ce8 402e0861
7f262cb0 :08d137a0 581a6640 00000020 7f262cf8 210cc499 00000001
7f262cc8 :00000000 7f262ce4 08d139e8 7f262cf0 581a66c0 53b8d780
7f262ce0 :00000000 00000020 08d137a0 210cc43e 08d1382c 08d139e4
7f262cf8 :08116840 08d139e4 00000000 581a6400 210b41ff 00000001
7f262d10 :581a6618 581a6560 210cc499 581a6565 581a6618 581a6560
7f262d28 :210d2744 581a62f0 581a6560 210d2725 2112a995 2112a985
7f262d40 :2112a975 23a67584 581a6578 00000001 00000001 220e35a9
7f262d58 :23a53381 581a62f0 00000000 00000000 581a6548 00000046
7f262d70 :00000000 00000002 00000000 581a62f0 00000001 00000000
7f262d88 :00000000 00000000 581a6530 581a62f0 23a56e15 24a18f95
7f262da0 :24a18ba3 00000000 581a6130 210bead9 581a6038 581a6038
7f262db8 :581a6038 53b88f50 40fa9ca8 581a6308 55b54b00 40fa9c38
7f262dd0 :80000000 55a06030 581a6020 581a6038 581a6020 24a189bb
7f262de8 :40fa9c38 581a6020 40fa9ca8 581a60c0 55a06030 53942ff8
7f262e00 :55b54b00 40fa9ca8 40fa9c38 08d137a0 7f262e24 210b34d8
7f262e18 :40fa9c38 40fa9c68 40fa9ca8 24a18800 402e3a4d 7f262fb3
7f262e30 :0000002c 00000003 7f262ec4 08d1382c 24b196e0 249c4f84
7f262e48 :581a5390 00000000 00000058 7f262e84 402b861a 249c4f84
7f262e60 :7f262e80 08d1382c 00000001 00000001 00000008 00000013
7f262e78 :00000005 581a5fd8 08d139dc 7f262e18 00000003 00000005
7f262e90 :00000005 00000000 00000000 55a06030 55b54b00 7f262e24
7f262ea8 :7f262e24 08d137a0 7f262ee0 24a18800 210b34a0 0000002c
7f262ec0 :7f262fb3 7f262f04 402c8931 08d1382c 1aea85c0 24b196e0
7f262ed8 :00000000 7f262f5c 402c8b74 7f262f54 401aaab0 00000000
7f262ef0 :7f262f5c 7f262f54 401aaab0 401aa6a0 1aea85c0 7f262f64
7f262f08 :402c8c41 08d1382c 249c4f84 00000000 7f262f5c 402c8b74
7f262f20 :00000000 7f262f54 08d13dd0 08d1382c 7f262f9c 00000000
7f262f38 :00000000 7f262f7c 402f2b2d 08d137a0 00000001 7f262f7c
7f262f50 :402f2b24 08d13dd0 402f2b24 7f262fd4 08d1382c 7f262f94
7f262f68 :402dbd4c 08d1382c 08d139dc 249c4f84 7f262fd4 08d139e4
7f262f80 :581a5ee0 00000000 476bd4c0 210b67f6 00000000 08d137a0
7f262f98 :210e7b1b 08d1382c 08d139e0 249c4f84 08d139dc 7f262fd4
7f262fb0 :083e6898 08d139dc 00000000 210eb30d 40fa9ca8 210eb184
7f262fc8 :405bff10 00000005 210e7c48 581a5fb8 581a5fb8 581a5fe0
7f262fe0 :00000000 00000000 581a5690 210e7253 581a5fb8 00000009
7f262ff8 :73a44aa8 73a44aa8 00000005 581a5fb8 00000009 581a5690
7f263010 :246e7cd0 581a5fb8 581a53e8 581a5f48 40fa9b90 40fa9be8
7f263028 :55a06030 55b54b00 40fa9be8 40fa9bd0 246e7b13 55b54b00
7f263040 :55a06030 40fa9b60 55b54b00 55a06030 581a5378 246e79b6
7f263058 :55a06030 55b54b00 57712968 405c6858 40fa9b40 00000001
7f263070 :40fa9b40 2426bab4 55a06030 57712968 57712928 57712968
7f263088 :55b54b00 55b54b00 4b345448 2426ba1b 2426b717 53b88f50
7f2630a0 :405c6858 5393c038 53b88f50 00000002 53b88f40 24266f1f
7f2630b8 :53b88f50 53b88f50 53b88f40 5393c038 53b849c0 00000000
7f2630d0 :53912b90 5393acd0 5393c038 53912b90 242613c8 5393c038
7f2630e8 :00000000 5393acd0 00000000 5393aa60 5393c038 24658a31
7f263100 :5393acd0 4a0dbf40 00000000 4a0dbf40 539125c0 23a74a88
7f263118 :539126e8 00000001 6553be00 539125c0 246587dc 53ebb610
7f263130 :4a0dbf40 00000000 4a124210 00000000 00000000 5393aa60
7f263148 :218aff64 09ccec00 221aa582 5393a440 4a1507e8 4a1507e8
7f263160 :536f07d8 533cdee0 5393a440 533cdee0 000378b6 536f07d8
7f263178 :5393a430 00000004 210b48f0 00000050 0000000f 211080dd
7f263190 :40576ec8 21108145 5393a480 5393aa60 5393aa60 21108074
7f2631a8 :00000003 536f07d8 4a124210 7d1c9048 5393a430 654d5040
7f2631c0 :4a090428 232a5328 7d1c9048 4a124210 229f2aeb 7d1c9048
7f2631d8 :4a124210 4a127090 538f80a8 654d5040 536f07d8 4a127090
7f2631f0 :536f07d8 242438f0 536f07d8 7d1c9048 7d1c9048 538f80a8
7f263208 :5393a418 7d1c9048 229f2a12 536f07d8 7d1c9048 22147208
7f263220 :40528fa8 4056b138 00000000 00000000 405d4858 7d1c9048
7f263238 :2214718a 5393a418 7d1c9048 229f239d 5393a418 536f07d8
7f263250 :7d1c9048 4056b138 41356f20 00000000 536f07d8 40528fa8
7f263268 :4a127090 7d1c9048 5393a418 538f80a8 42562b68 538f81e0
7f263280 :229f2230 219161d1 41356f20 218e2089 42562b6d 41356f20
7f263298 :7f2632b4 210b8c73 402e37ef 7f2633e8 08d137a0 7f2632b4
7f2632b0 :210b3478 210b8c60 402e3a4d ffffffff 00000010 00000000
7f2632c8 :7f263354 08d1382c 200920e0 200282cc 00000000 00000000
7f2632e0 :00000000 7f263314 402b861a 200282cc 7f263310 08d1382c
7f2632f8 :00000001 00000001 00000006 00000006 00000001 08d137a0
7f263310 :00000000 7f2632b4 00000000 00000001 00000001 00000000
7f263328 :00000000 00000000 42562b68 7f2632b4 7f2632b4 08d137a0
7f263340 :00000000 210b8c60 210b3440 00000010 ffffffff 7f263394
7f263358 :402c8931 08d1382c 080d97e0 200920e0 00000000 7f2633e8
7f263370 :402e3550 7f2633cc 00000000 08d1382c 08d1382c 7f263aac
7f263388 :00000000 00000000 080d97e0 7f2633d4 402c9e9f 08d1382c
7f2633a0 :200282cc 00000000 7f2633e8 402e3550 00000001 7f2633cc
7f2633b8 :00000000 00000000 00000000 00000000 00000000 00000000
Code:
4026d48f :83403d9a 008bf4c4 166be850 c4830009 f4c48310 a817e853
4026d4a7 :b70f0009 c0010643 06438966 0ff8c483 048dc0b7 02e0c140
4026d4bf :08438b50 57b7e850 43890003 20c48308 53f4c483 09a87ce8
4026d4d7 :9a38a100 8b64403d 30050300 83403d9a c48310c4 50008bf4
4026d4ef :0915f4e8 084b8b00 4574c985 0f0c558b 8d0443b7 14894004
4026d507 :10558b81 0443b70f c140048d 430302e0 04508908 0f14558b
4026d51f :8d0443b7 e0c14004 08430302 66085089 b80443ff 00000001
4026d537 :b48d09eb 00000026 8bc03100 ec89e85d 768dc35d e5895500
4026d54f :570cec83 458b5356 08558b08 00fc45c7 83000000 b70ff4c4
4026d567 :478d0478 8df8d101 e852ff58 0009a7ed 8310c483 4974fffb
4026d57f :084d8b90 8b5b148d 048d0841 0c558b90 77045039 0850391c
4026d597 :188b0f72 51f4c483 09a7fce8 ebd88900 fc5d892e 768d05eb
4026d5af :8bdf8900 de89fc4d 8939148d 1fe8c1d0 d1101c8d 75f339fb
4026d5c7 :08458bb8 50f4c483 09a7cce8 8dc03100 5e5be865 5dec895f
4026d5df :e58955c3 571cec83 458b5356 fc45c70c 00000000 04788366
4026d5f7 :c7627400 0000f845 558b0000 f8458b0c 8b084203 8b118b08
4026d60f :388b0442 8b08428b 8b028b30 f8c48300 8b04598b 08418b10
4026d627 :5040d829 145d2b52 52575653 10458b53 2c406850 558b4036
4026d63f :bae85208 8bc7ddb3 c4830c55 f8458330 fc45ff0c 0442b70f
4026d657 :7cfc4539 d8658da5 895f5e5b 89c35dec e58955f6 572cec83
4026d66f :38a15356 64403d9a 0503008b 403d9a30 8bf4c483 5ee85000
4026d687 :83000914 c48310c4 e45d8df4 19bbe853 b2e80009 e8000918
Loaded modules:
(* denotes the module causing the exception)
0x08048000-0x0804ce46 /opt/obs/wls/jrockit-j2sdk1.4.2_08/bin/java
0x4001d000-0x40029fab /lib/i686/libpthread.so.0
0x4004e000-0x4006fb42 /lib/i686/libm.so.6
0x40071000-0x4007300c /lib/libdl.so.2
0x40075000-0x401a76e5 /lib/i686/libc.so.6
0x401b2000-0x40388eef* /opt/obs/wls/jrockit-j2sdk1.4.2_08/jre/lib/i386/jrockit/libjvm.so
0x7ec57000-0x7ec66fa5 /opt/obs/wls/jrockit-j2sdk1.4.2_08/jre/lib/i386/libverify.so
0x7ec75000-0x7ec94a0f /opt/obs/wls/jrockit-j2sdk1.4.2_08/jre/lib/i386/libjava.so
0x7ec9c000-0x7ecae3ba /lib/libnsl.so.1
0x7ec97000-0x7ec98705 /opt/obs/wls/wls8.1sp3/weblogic81/server/lib/linux/i686/libweblogicunix1.so
0x7f5f2000-0x7f5f3eff /opt/obs/wls/wls8.1sp3/weblogic81/server/lib/linux/i686/libmuxer.so
0x7f5f6000-0x7f5f95c1 /opt/obs/wls/jrockit-j2sdk1.4.2_08/jre/lib/i386/libioser12.so
0x80318000-0x8031f8bf /opt/obs/obs_app/obs31.0/thirdparty/libXMLC.so
0x80344000-0x8034c66f /opt/tib/rv7.1.2/lib/libtibrvj.so
0x8034e000-0x803563e0 /opt/tib/rv7.1.2/lib/libtibrvcmq.so
0x803d2000-0x803e66bb /opt/tib/rv7.1.2/lib/libtibrvcm.so
0x7fef9000-0x7fefdcaf /opt/tib/rv7.1.2/lib/libtibrvft.so
0x803e8000-0x804341a4 /opt/tib/rv7.1.2/lib/libtibrv.so
Thread Stack Trace:
WARNING: Memory exhausted
at java/lang/Throwable.fillInStackTrace0(Native Method)@0x210cc3f0
at java/lang/Throwable.fillInStackTrace(Unknown Source)@0x210cc499
at java/lang/Throwable.<init>(Unknown Source)@0x210d2744
at java/lang/Exception.<init>(Exception.java:41)@0x210d2725
at java/lang/RuntimeException.<init>(RuntimeException.java:43)@0x2112a995
at java/lang/IllegalArgumentException.<init>(IllegalArgumentException.java:36)@0x2112a985
at java/lang/NumberFormatException.<init>(NumberFormatException.java:38)@0x2112a975
at java/lang/NumberFormatException.forInputString(NumberFormatException.java:48)@0x23a67584
at java/lang/FloatingDecimal.readJavaFormatString(FloatingDecimal.java:1207)@0x220e35a9
at java/lang/Double.parseDouble(Double.java:220)@0x23a56e15

I can't tell from the crash dump what the exact problem is - maybe you are running out of native memory?
You are running a very old JRockit version. Since you are a Oracle/BEA customer, you can get a newer one from BEA Support, or through edelivery.oracle.com.
-- Henrik

Can anyone help with an out of memory error on CS2?

Hello,
I have been battling with an out of memory error on a dell laptop running 2gb of ram. I have had no prior issues with this laptop running CS2 until last week when I started getting the out of memory errors. I have seen several articles about this occuring on later versions of illustrator. Just prior to this issue appearing I had to delete and rebuild the main user profile on the computer due to it consistently logging into a temporary account.
Once the new profile was established and all user documents and profile settings were transferred back into it, this problem started showing up. The error occurs when clicking on files listed as Illustrator files, and when opening the illustrator suite. Once I click on the out of memory error it still continues to load illustrator. The files are located on a server and not on the remote computer. I have tried to copy the files to the local hard drive with the same result when I try to open them. I also tried to change the extension to .pdf and got no further. I tried to open a file and recreate the work and all I got was the black outline of the fonts. none of the other artwork appeared. once rebuilt, when trying to save, It gives the out of memory error and does not save the file.
Illustrator was installed on another dell laptop, same model, etc and works fine. no problem accessing network files. I just attempted to use Illustrator from the admin profile on the machine in question and it works fine and lightening fast. Just not from the new rebuilt profile. I have tried to uninstall and reinstall the software. it has not helped. could there be stray configuration settings that we transfered over to the new profile that should not have been?
Any insights will be helpful.
Thank You,
Brad Yeutter

Here are some steps that could help you:
http://kb2.adobe.com/cps/320/320782.html
http://kb2.adobe.com/cps/401/kb401053.html
I hope this helps!

Data merge with football tickets. Printing causes out of memory errors. Can only print 10 at a time!

Here's the deal. Printing football tickets for the local high school. 10 tickets per 8.5 x 11 sheet. All black and white. I couldn't data merge into one whole document of tickets because it was failing to do that. So, I end up with 3 documents. First two have 50 pages of tickets and the last has 37 pages.
When I go to print, I can only print 10 pages at a time or InDesign straight up crashes or I get an "Out of Memory" error which is bull because I've got plenty of ram available (unless it's complaining about lack of HD space for some reason)
Incredibly frustrating.
Each ticket has 3 images on it. Two of the images are the same. Those two images are about 103kb .ai files. Very very simple. The other image is a TIFF that is about 76kb. So there are 1000 .ai files / document and 500 TIFFs.
Here's a video I took of it ripping: http://www.youtube.com/watch?v=UCjvdmXuaYs&feature=c4-overview&list=UUf_1UFp80YLZJfCyIxXEg kg
Also, when printing, I have the Send Data set to Optimized Subsampling instead of "All". That's not seeming to help.
Any thoughts?
IDCS 5.5
OSX 10.8.4

I just ran a sample on my laptop.
AI file, duplicated, is 284k. Image is roughly 200k. The CSV has 2054 records, and the merged document with 10 per page is 250 megabytes. PDF is just under 50 megs.
This laptop has only 4 gigs memory but has a lot of free disk space. It took a good amount of time to do the merge, a bit longer to create the PDF-X1a PDF.
Mike

Report with more than 600 kb image - BO Server getting Out Of memory Error

Hi,
   We have a report which displays images and size is above 600 KB.We are getting an "Out Of memory" Error while previewing this report in Business Object Server.
In another situation we tried by giving a dynamic path to the OLE object, but the report is not showing error. We are not able to view the image whose size is more than 600KB
Notes: 1. Image is stored as a BLOB in Oracle Database
           2. Connection used inside the report is OLEDB
           3. UNIX Environment
Regards,
Sathish

Please re-post if this is still an issue to the Business Objects Forum or if you have a valid support contract create a case on line.

Loading JPEG/Gif images causes Out Of Memory Error

Hello Java gurus, please shed some light on this.....
I am not a java newbie, but I am a java newbie in the area of dealing with graphics. I am using JDK 1.4.2_01 on Win XP with 2.4ghz and 512 RAM. When I try to read in a (or a few) JPEG image into a JLabel using ImageIcon, I get an out of memory error everytime. This happens whether I am reading the image out of a jar file or out of a local directory. The JPEG's are 8.5" x 11", and range between 150kb to 900kb. I am trying to load approximately 10 images in a JTabbedPane using new JLabel(ImageIcon) on individual JPanels (one JPanel for each JPEG). Now I get the java.lang.outofmemory error whether I try to load 1 image or 10 images. Anyone got a clue as to what I am doing wrong? I actually do get one image loaded before the error gets thrown. So I do know that it is trying to load the right image. What is going on here? Is it an ImageIcon problem, or are there others who have run into this. It has brought this project to a grinding halt, and I had thought this would be the easier part!!!! Please help me out gurus! Thanks!

What options/values are you suggesting that I set? Or do you mean something else? Thank you for any ideas that can help me solve this problem. I never had any issues dealing with using ImageIcon for toolbar button graphics (file sizes of 1-3kb), but now with dealing with full page graphics I have run into a brick wall with this out of memory error.

Out of Memory Error - JBOSS - JRocket

I continue to see my jrocket/jboss/linux servers crash daily in production for out of memory errors. When we trace back the stack to find a query that does not appear to have nearly enough data to bring the server to an out of memory state. Heap useage pattern does not indicate any leak in the application.
Using RedHat Linux ES - rel. 4 - Nahant Update 4
startup with 1536m Xms/x
Any thoughts or previous expereince. This is a Java application servicing a Flex UI

Check your Linux kernel version.
If you have an unpatched Linux kernel, which is not compliant, you will see these errors for all Jrocket.
The 2,6,9-5 kernel is not compliant without patches, see:
http://e-docs.bea.com/jrockit/jrdocs/suppPlat/prodsupp.html#wp999048
excerpt
The JRockit JDK is supported on the default Linux kernel, which varies with the distribution and architecture. See the Notes field in the Summary of Supported Configurations by Release for details. If you require a different kernel, such as the hugemem kernel, contact Oracle Support for current support status.
Also, see references to x_86 64bit?
http://jira.jboss.org/jira/browse/JBPAPP-158
This is a 32bit ES - rel 4 correct?
This link also shows a fairly excellent step by step Out of Memory Troubleshooting session.

JNI and Out of Memory errors

Hi,
At my job, we seem to have a memory leak related to JNI. We know we
have a memory leak because we keep getting Out of Memory errors even
after increasing the maximum heap size to more than 256 megs. And we
know that this is the application that is eating up all the system
memory.
We are running under Windows 2000, with both JDK 1.3.0 and JDK 1.4.1.
We tried looking at the problem under JProbe, but it shows a stable
Java heap (no problems, except that the Windows task manager shows it
growing and growing...)
I tried a strip down version, where I set the max heap size to 1 Meg,
and print out the total memory, memory used, and maximum memory used at
a 5 sec interval.
Memory used = Runtime.getRuntime().totalMemory() - Runtime.getRuntime().freeMemory().
Well, I let that strip down version running for about a day. The
maximum memory used has stabilized to about 1.1 Meg, and has not
increased. The current memory used increases until it gets to some
threshold, then it decreases again. However, the Windows task manager
shows the memory increasing -- and currently it is at 245 Megs!
In the lab, the behavior we see with the Windows task manager is as
follows:
1. Total memory used in the system increases until some threshold.
2. Then it goes back down by about 100 Megs.
3. This cycle continues, but at each cycle the memory goes back down
less and less, until the app crashes.
Now, our theory is that JNI is consuming all this memory (maybe we are
using JNI wrong). That's the only explanation we can come up with to
explain what we have seen (Java showing an OK heap, but the task
manager showing it growing, until crashing).
Does that make sense? Can the new operator throw an Out of Memory
error if the system does not have enough memory to give it, even if
there is still free heap space as far as the Runtime object is
concerned? Does the Runtime object figures objects allocated through
JNI methods into the heap used space?
Note that I know the task manager is not a reliable indicator.
However, I don't think a Java app is supposed to runaway with system
memory -- the problem is not simply that the Java app is consuming too
much memory, but that it seems to always want more memory. Besides, we
do get the Out of Memory error.
Thanks for your help,
Nicolas Rivera

Hi,
there are two sources of memory leakage in JNI:
- regular leaks in c/c++ code;
- not released local/global references of java objects in JNI.
I think that the first issue in not a problem for you. The second is more complex. In your JNI code you should check
- how many local references alive you keep in your code as their number is restricted (about 16 and can be enlarged). The good style is not to store local references but keep only global.
- any local reference accepted from java call in JNI are released by JVM. You should release local references you created in JNI and also global references.
- do not use a large number of java object references. Each new reference gets new memory in JVM. Try to reuse refences.
I guess that is your problem.
Vitally

Weblogic 6.1 deployment out of memory error - please help

I am getting an out of memory error when deploying an ear to a weblogic 6.1 server. I tried increasing heap size with the startup param. I also tried upgrading the jdk to 1.3.1_02. Here is how I am starting weblogic -
"%JAVA_HOME%\bin\java" -hotspot -XX:MaxPermSize=256m -ms64m -mx64m -classpath "%CLASSPATH%" -Dweblogic.Domain=mydomain -Dweblogic.management.discover=false -Dweblogic.Name=myserver "-Dbea.home=C:\bea" -Dweblogic.management.password=%WLS_PW% -Dweblogic.ProductionModeEnabled=%STARTMODE% "-Djava.security.policy==C:\bea\wlserver6.1/lib/weblogic.policy" weblogic.Server
I tried 64, 128, and 256 for the MaxPermSize param and the larger I make this number, the longer the deploy takes. I also tried lowering the session timeout to 1 min from 30. Now, when I deploy to the weblogic connection, jdev writes the war, then hangs. The rest of my desktop is slow but responsive, but I let jdev go for up to 1hr when running this deploy, and it never even starts the weblogic.deploy call. I end up killing it. This ear is not very big and is a simple servlet.
Any thoughts?

repost

Out of memory Error with jdk 1.6

Similar Messages

Maybe you are looking for