Korg Legacy collection is what causes Out of Memory error

Hi guys
I'm pretty sure i've narrowed it down to this. I don't seem to get it unless i've got a few instances of it. Anyone able to offer advise/confirm/comment?
Thanks guys
Eddie

Being a rompler, the legacy coll. is a RAM hog. Try using it in multimode to save memory. It should have a "dump unused samples" feature, but it doesn't

Similar Messages

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.

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

[N95 8GB]Out of Memory error when opening 15MB pdf...

What is the file size limit when opening a pdf file? I have a 15MB pdf file that cause 'Out of memory' error when I opened it with the PDF Reader that comes with the phone.
Thanks.

Hi,
It seems that problem is file specific, so could you please share a file with me. I sending you a private message.
Regards,
Anoop

Logic pro 8 wont validate korg legacy collection

the AU for korg legacy collection works on other apps except logic. logic says that "cant be opened" + if i manually try to go to au manger to enable it, it says " updating properties of AU legacy(x) by KORG...FAILED!" x = cell, ms-20 etc. what do i do?

this came when i re scanned the plug ins in au manger:
AU Validation Tool
Version: 1.2.1b3
Copyright 2003-2007, Apple, Inc. All Rights Reserved.
Specify -h (-help) for command options
VALIDATING AUDIO UNIT: 'aumf' - 'KLFV' - 'KORG'
Manufacturer String: KORG
AudioUnit name: MDE-X
Component Info: MDE-X
Component Version: 1.2.1 (0x10201)
Component's Bundle Version: 1.2.1
* * PASS
TESTING OPEN TIMES:
COLD:
2007-12-05 11:32:55.969 auvaltool[1210:80f] Error loading /Library/Audio/Plug-Ins/Components/MDE-X.component/Contents/MacOS/MDE-X: dlopen(/Library/Audio/Plug-Ins/Components/MDE-X.component/Contents/MacOS/MDE-X, 262): no suitable image found. Did find:
/Library/Audio/Plug-Ins/Components/MDE-X.component/Contents/MacOS/MDE-X: mach-o, but wrong architecture
FATAL ERROR: OpenAComponent: result: -50,0xFFFFFFCE
validation result: successfully validated
updating properties of AU MDE-X by KORG...FAILED!

TS5249 Problems with the Korg Legacy Collection in the new version of Garageband in Mavericks.

Hello!
I'm having problems with the Korg Legacy Collection in the new version of Garageband in Mavericks. When I try to load the AU, I get this error message:
"Failed to load Audio Unit, please contact the manufacturer for an updated version or further assistance. (-10110)"
They seem to work fine in Ableton Live 8 Lite, also running in Mavericks. So, I think it is something with Garageband. In addition, Korg updated to 64bit early last year.
Anyone know how to fix the problem? Or is Korg or Apple's problem?
Thanks.

They seem to work fine in Ableton Live 8 Lite, also running in Mavericks. So, I think it is something with Garageband. In addition, Korg updated to 64bit early last year.
Have you checked, if you have the newest 64-bit version installed? There may still be an older version sitting around - check both plug-in folders, the one in your Home folder and the one in the system library:
~/Library/Audio/Plug-Ins/
/Library/Audio/Plug-Ins/
Some programs may still be able to use 64-bit plug-ins, but GarageBand will not use them: http://support.apple.com/kb/TS5249

Out of Memory error caused by huge result set

Hi,
I'm using version 3.3.4 of KODO with the enterpise license. Our
application has some places where we're using straight SQL to create a
query using the following statement:
Query query = pm.newQuery ("javax.jdo.query.SQL", queryString);
There is one query that performs an inner join and returns over 2 billion
results. Of course this throws an out of memory error when we try to add
the results to a list. I printed out the exact SQL statement that is
being executed and it should return 0 results. The application is hitting
an Oracle 9i database, and running the query through the Oracle tool
SQLPlus returns the correct result. I'm stumped as to why this massive
result set is being returned when we use KODO. Here is the SQL string for
your examination:
SELECT T_ORDERITEM.* FROM T_ORDERITEM INNER JOIN T_REVENUE ON
T_ORDERITEM.ORDER_HOID = T_REVENUE.HOID WHERE T_ORDERITEM.COMMODITY_HOID
= '1871816913731466' AND T_ORDERITEM.DATESHIPPED BETWEEN
TO_DATE('12/25/2005', 'MM/DD/YYYY') AND TO_DATE('01/24/2006',
'MM/DD/YYYY') AND T_REVENUE.CUSTOMER_HOID IN (1844203535241210)
Thanks for your help,
Bennett

I'm also using JDK 1.4.2 so I'm not sure why you wouldn't be running into
the issue using the ArrayList constructor.
-Bennett
Paul Mogren wrote:
What result list implementation are you using? What's your JDK
version? I'm sure I've written new ArrayList(results) numerous times
without trouble, though I have not used Kodo 3.3.4. I had a look at
the JDK 1.4.2 source code for ArrayList(Collection) and
ArrayList.addAll(Collection), and it looks to me like the latter would
consume more memory than the former. However, it might be worth noting
that the former invokes size() on the argument.
-Paul Mogren, CommerceHub
On Thu, 19 Jan 2006 22:10:50 +0000 (UTC), [email protected]
(Bennett Hunter) wrote:
Nevermind, issue resolved. This wasn't due to the query, but rather how
we were creating a list with the results returned. This issue is probably
already posted, but I'll give the info. again:
You can't create an arraylist by passing in the kodo collection of results
to the constructor of ArrayList. For example: List l = new
ArrayList(results) .... that will throw the out of memory error because of
the way that the constructor builds the kodo collection. Maybe the bug is
with the kodo collection. However, the way around this is to create the
list with an empty constructor and then do an addAll() operation.
Bennett Hunter wrote:
Hi,
I'm using version 3.3.4 of KODO with the enterpise license. Our
application has some places where we're using straight SQL to create a
query using the following statement:
Query query = pm.newQuery ("javax.jdo.query.SQL", queryString);
There is one query that performs an inner join and returns over 2 billion
results. Of course this throws an out of memory error when we try to add
the results to a list. I printed out the exact SQL statement that is
being executed and it should return 0 results. The application is hitting
an Oracle 9i database, and running the query through the Oracle tool
SQLPlus returns the correct result. I'm stumped as to why this massive
result set is being returned when we use KODO. Here is the SQL string for
your examination:
SELECT T_ORDERITEM.* FROM T_ORDERITEM INNER JOIN T_REVENUE ON
T_ORDERITEM.ORDER_HOID = T_REVENUE.HOID WHERE T_ORDERITEM.COMMODITY_HOID
= '1871816913731466' AND T_ORDERITEM.DATESHIPPED BETWEEN
TO_DATE('12/25/2005', 'MM/DD/YYYY') AND TO_DATE('01/24/2006',
'MM/DD/YYYY') AND T_REVENUE.CUSTOMER_HOID IN (1844203535241210)
Thanks for your help,
Bennett

Getting out of memory errors in Indesign 5.5. What can I do to fix it?

Getting out of memory errors in Indesign 5.5. What can I do to fix it?

Tell your dumb friend to pay you for a new phone as he damaged it. You cannot get help here for a phone that has been taken apart, as it is not user servicible. Your dumb friend also voided your warranty and, even if the warranty were expired Apple will never touch that phone.
Time to get smarter friends.

Out of Memory Error, Buffer Sizes, and Loop Rates on RT and FPGA

I'm attempting to use an FPGA to collect data and then transfer that data to a RT system via a FIFO DMA, and then stream it from my RT systeam over to my host PC. I have the basics working, but I'm having two problems...
The first is more of a nuisance. I keep receiving an Out of Memory error. This is a more recent development, but unfortunately I haven't been able to track down what is causing it and it seems to be independent of my FIFO sizes. While not my main concern, if someone was able to figure out why I would really appreciate it.
Second, I'm struggling with overflows. My FPGA is running on a 100 MHz clock and my RT system simply cannot seem to keep up. I'm really only looking at recording 4 seconds of data, but it seems that no matter what I do I can't escape the problem without making my FIFO size huge and running out of memory (this was before I always got the Out of Memory error). Is there some kind of tip or trick I'm missing? I know I can set my FPGA to a slower clock but the clock speed is an important aspect of my application.
I've attached a simplified version of my code that contains both problems. Thanks in advance for taking a look and helping me out, I appreciate any feedback!

David-A wrote:
The 7965 can't stream to a host controller faster than 800MB/s. If you need 1.6GB/s of streaming you'll need to get a 797x FPGA module.
I believe the application calls for 1.6 GB over 4s, so 400 MB/s, which should be within the capabilities of the 7965.
I was going to say something similar about streaming over ethernet. I agree that it's going to be necessary to find a way to buffer most if not all of the data between the RT Target and the FPGA Target. There may be some benefit to starting to send data over the network, but the buffer on the host is still going to need to be quite large. Making use of the BRAMS and RAM on the 7965 is an interesting possibility.
As a more out there idea, what about replacing the disk in your 8133 with an SSD? I'm not entirely sure what kind of SATA connection is in the 8133, and you'd have to experiment to be sure, but I think 400 MB/s or close to that should be quite possible. You could write all the data to disk and then send it over the network from disk once the aquisiton is complete. http://digital.ni.com/public.nsf/allkb/F3090563C2FC9DC686256CCD007451A8 has some information on using SSDs with PXI Controllers.
Sebastian

Uploading large files from applet to servlet throws out of memory error

I have a java applet that needs to upload files from a client machine
to a web server using a servlet. the problem i am having is that in
the current scheme, files larger than 17-20MB throw an out of memory
error. is there any way we can get around this problem? i will post
the client and server side code for reference.
Client Side Code:
import java.io.*;
import java.net.*;
// this class is a client that enables transfer of files from client
// to server. This client connects to a servlet running on the server
// and transmits the file.
public class fileTransferClient
private static final String FILENAME_HEADER = "fileName";
private static final String FILELASTMOD_HEADER = "fileLastMod";
// this method transfers the prescribed file to the server.
// if the destination directory is "", it transfers the file to
"d:\\".
//11-21-02 Changes : This method now has a new parameter that
references the item
//that is being transferred in the import list.
public static String transferFile(String srcFileName, String
destFileName,
String destDir, int itemID)
if (destDir.equals(""))
destDir = "E:\\FTP\\incoming\\";
// get the fully qualified filename and the mere filename.
String fqfn = srcFileName;
String fname =
fqfn.substring(fqfn.lastIndexOf(File.separator)+1);
try
//importTable importer = jbInit.getImportTable();
// create the file to be uploaded and a connection to
servlet.
File fileToUpload = new File(fqfn);
long fileSize = fileToUpload.length();
// get last mod of this file.
// The last mod is sent to the servlet as a header.
long lastMod = fileToUpload.lastModified();
String strLastMod = String.valueOf(lastMod);
URL serverURL = new URL(webadminApplet.strServletURL);
URLConnection serverCon = serverURL.openConnection();
// a bunch of connection setup related things.
serverCon.setDoInput(true);
serverCon.setDoOutput(true);
// Don't use a cached version of URL connection.
serverCon.setUseCaches (false);
serverCon.setDefaultUseCaches (false);
// set headers and their values.
serverCon.setRequestProperty("Content-Type",
"application/octet-stream");
serverCon.setRequestProperty("Content-Length",
Long.toString(fileToUpload.length()));
serverCon.setRequestProperty(FILENAME_HEADER, destDir +
destFileName);
serverCon.setRequestProperty(FILELASTMOD_HEADER, strLastMod);
if (webadminApplet.DEBUG) System.out.println("Connection with
FTP server established");
// create file stream and write stream to write file data.
FileInputStream fis = new FileInputStream(fileToUpload);
OutputStream os = serverCon.getOutputStream();
try
// transfer the file in 4K chunks.
byte[] buffer = new byte[4096];
long byteCnt = 0;
//long percent = 0;
int newPercent = 0;
int oldPercent = 0;
while (true)
int bytes = fis.read(buffer);
byteCnt += bytes;
//11-21-02 :
//If itemID is greater than -1 this is an import file
transfer
//otherwise this is a header graphic file transfer.
if (itemID > -1)
newPercent = (int) ((double) byteCnt/ (double)
fileSize * 100.0);
int diff = newPercent - oldPercent;
if (newPercent == 0 || diff >= 20)
oldPercent = newPercent;
jbInit.getImportTable().displayFileTransferStatus
(itemID,
newPercent);
if (bytes < 0) break;
os.write(buffer, 0, bytes);
os.flush();
if (webadminApplet.DEBUG) System.out.println("No of bytes
sent: " + byteCnt);
finally
// close related streams.
os.close();
fis.close();
if (webadminApplet.DEBUG) System.out.println("File
Transmission complete");
// find out what the servlet has got to say in response.
BufferedReader reader = new BufferedReader(
new
InputStreamReader(serverCon.getInputStream()));
try
String line;
while ((line = reader.readLine()) != null)
if (webadminApplet.DEBUG) System.out.println(line);
finally
// close the reader stream from servlet.
reader.close();
} // end of the big try block.
catch (Exception e)
System.out.println("Exception during file transfer:\n" + e);
e.printStackTrace();
return("FTP failed. See Java Console for Errors.");
} // end of catch block.
return("File: " + fname + " successfully transferred.");
} // end of method transferFile().
} // end of class fileTransferClient
Server side code:
import java.io.*;
import javax.servlet.*;
import javax.servlet.http.*;
import java.util.*;
import java.net.*;
// This servlet class acts as an FTP server to enable transfer of
files
// from client side.
public class FtpServerServlet extends HttpServlet
String ftpDir = "D:\\pub\\FTP\\";
private static final String FILENAME_HEADER = "fileName";
private static final String FILELASTMOD_HEADER = "fileLastMod";
public void doGet(HttpServletRequest req, HttpServletResponse resp)
throws ServletException,
IOException
doPost(req, resp);
public void doPost(HttpServletRequest req, HttpServletResponse
resp)
throws ServletException,
IOException
// ### for now enable overwrite by default.
boolean overwrite = true;
// get the fileName for this transmission.
String fileName = req.getHeader(FILENAME_HEADER);
// also get the last mod of this file.
String strLastMod = req.getHeader(FILELASTMOD_HEADER);
String message = "Filename: " + fileName + " saved
successfully.";
int status = HttpServletResponse.SC_OK;
System.out.println("fileName from client: " + fileName);
// if filename is not specified, complain.
if (fileName == null)
message = "Filename not specified";
status = HttpServletResponse.SC_INTERNAL_SERVER_ERROR;
else
// open the file stream for the file about to be transferred.
File uploadedFile = new File(fileName);
// check if file already exists - and overwrite if necessary.
if (uploadedFile.exists())
if (overwrite)
// delete the file.
uploadedFile.delete();
// ensure the directory is writable - and a new file may be
created.
if (!uploadedFile.createNewFile())
message = "Unable to create file on server. FTP failed.";
status = HttpServletResponse.SC_INTERNAL_SERVER_ERROR;
else
// get the necessary streams for file creation.
FileOutputStream fos = new FileOutputStream(uploadedFile);
InputStream is = req.getInputStream();
try
// create a buffer. 4K!
byte[] buffer = new byte[4096];
// read from input stream and write to file stream.
int byteCnt = 0;
while (true)
int bytes = is.read(buffer);
if (bytes < 0) break;
byteCnt += bytes;
// System.out.println(buffer);
fos.write(buffer, 0, bytes);
// flush the stream.
fos.flush();
} // end of try block.
finally
is.close();
fos.close();
// set last mod date for this file.
uploadedFile.setLastModified((new
Long(strLastMod)).longValue());
} // end of finally block.
} // end - the new file may be created on server.
} // end - we have a valid filename.
// set response headers.
resp.setContentType("text/plain");
resp.setStatus(status);
if (status != HttpServletResponse.SC_OK)
getServletContext().log("ERROR: " + message);
// get output stream.
PrintWriter out = resp.getWriter();
out.println(message);
} // end of doPost().
} // end of class FtpServerServlet

OK - the problem you describe is definitely what's giving you grief.
The workaround is to use a socket connection and send your own request headers, with the content length filled in. You may have to multi-part mime encode the stream on its way out as well (I'm not about that...).
You can use the following:
http://porsche.cis.udel.edu:8080/cis479/lectures/slides-04/slide-02.html
on your server to get a feel for the format that the request headers need to take.
- Kevin
I get the out of Memory Error on the client side. I
was told that this might be a bug in the URLConnection
class implementation that basically it wont know the
content length until all the data has been written to
the output stream, so it uses an in memory buffer to
store the data which basically causes memory issues..
do you think there might be a workaround of any kind..
or maybe a way that the buffer might be flushed after
a certain size of file has been uploaded.. ?? do you
have any ideas?

Out of memory error in IBM JVM

Hi i am using websphere application server's dyna cache for getting performance optimiztion in my application.
I am able to load values into the cache using the command cache api in the dyna cache.When i clear the cache for loading another set of values the cache gets cleared but still ,while loading the second set of values i get an out of memory error
The dynacache is an distributed map
i want to know whether the error is due to improper garbage collection
on this map,if so help me to overcome this
The JVM configuration are as follows
Min 256mb
Max 768mb
I have a total of 1Gb ram

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 : unable to create new native thread

Hi Experts,
The details are given below -
1. Sun Java System Application Server 7
2. Java 1.4.2_05
3. Solaris 9 (OS)
4. RAM 8 GB
There are 3-4 applications deployed on this Sun Server 7. Some times we got "Out Of Memory" Error while displaying any jsp. Then we restart the Sun Server, the problem is resolved for some time.
This all is happening on production environment. We can not start the Sun Server again & again on production.
We have also set the java parameters as -Xms 3584M & -Xmx 3584M i.e 3.5 GB around.
If we change this parameter means less or more from 3584M, then our site becomes down.
Please help us out as soon as possible.

How do you expect anyone to give you a sensible answer to this? What server are you using to execute the JSP's? Tomcat? Is the code in the JSP causing the out of mem or is it a server related issue (unlikely...)?
Drill down to the core of the problem before posting...

FCP - Out of Memory Error in 10.6.6

Running a MacBook Pro 17" (A1261) and while I edit, I got a "Out of Memory" Error and an "Invalid Operation". Can't reopen the sequence on my MacBook but it opens with no problem on a Mac Pro.
Gonna re-install the OS and see if that helps.

I just had something very similar happen. A sequence that I've been editing for over a month now no longer opens (since installing the 10.6.6 update) I'm getting the same "out of memory" and I/O error codes.
I'm at a loss what to do. Other editing projects open fine. But so far I haven't been able to open
any of the project files I've vaulted from the last six weeks.
Does anyone have any idea what changes 10.6.6 might have made to cause this and how
it could be rectified. I really need to get back into my project file.

Frm-40024 out of memory error

I am trying to upgrade forms 10g to 11g.
after installing the weblogic 10.30.2 , fusion middleware 11.1.1.2.0, I compiled the old forms to a new version.
there was no compile error and .fmx file generated very successfully.
I runned the file in my local computer. there was no problem.
So,
I uploaded .fmx into the WAS Server, and when I opened the form screen in the menu, I got an error!!!!
"frm-40024 out of memory error"
what is the problem?

Hi user13763783
The error is direct and straight forward ...
Error Message: FRM-40024: Out of memory.
Error Cause:
Internal error. Your computer does not have enough memory to run the form.
Action:The designer might be able to modify the form so that it will run.
If that is not feasible, your installation must make more memory available, either by modifying the operating system parameters or by adding more memory to the computer.
Level: >25 Type: ErrorHope this helps...
Regards,
Abdetu...

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

Korg Legacy collection is what causes Out of Memory error

Similar Messages

Maybe you are looking for