Memory leak when browsing through records

Hello,
I have a problem with any page containing the component related to each other on three or more levels. (1st level ADF Table, 2nd level ADF Table and 3rd level ADF Form)
By navigating through the records of the first level, there is refreshment at other levels (using partial triggers), but suddenly there is loss of memory (memory leak) for components of type Select One Choice.
Precisely, the problem appears when browsing another Show Detail Item in the same page.
Screenshot showing the Data Control in my page: [http://www.infotun.net/usersimages/1/adf/structure.jpg]
Capture screen representing the initial state where all is well: [http://www.infotun.net/usersimages/1/adf/initial.jpg]
Capture screen representing the final state after memory loss: [http://www.infotun.net/usersimages/1/adf/final.jpg]
I'm using JDeveloper Studio 11.1.1.2.0
JDK: 1.6.0_14
Operating System: Windows 7.
Any help/advice is highly appreciated !
Thanks
Edited by: InfoTun on 10 juin 2012 16:22
Edited by: InfoTun on 10 juin 2012 16:26

Hi,
the screenshot does not indicate a memory leak. Memory leaks show by the server memory consumption that leads to slow performance or stale applications. Your issue seems to be different from that and doesn't really explain in the screen shots. If you have a support contract then customer support is the recommendation I like to give
Frank

Similar Messages

Memory Leak when running Contacts

I am having a big memory leak when running the app Contacts on a MB Air. It gobbles up 2 GB of ram in just a few minutes forcing a reboot. I have re-installed Mountain Lion 10.8.2 and it still leaks memory. Watching Activity Monitor shows the rapid increase in Ram being gobbled up by Contacts. Used Mackeeper to clear cache as well as ran Cocktail, all to no avail. Any tips would be greatly appreciated.

The size of oracle.exe is not an indication of how the Java VM GC works; so you are not comparing apples to apples. It'll be too long to explain here but in my upcoming book (see hereafter), I gave a detailled explanation of the various memory areas the Java VM uses and how these are GCed and also how you can meausre their size (not all, though).
In short you want to use OracleRuntime methods such as
OracleRuntime.getSessionSize(); --> get he current size of Sessionspace
OracleRuntime.getNewspaceSize(); --> get he current size of Newspace
there are other memory areas described in the book
http://www.oracle.com/technology/pub/articles/mensah_dws.html
http://www.elsevier.com/wps/find/bookdescription.cws_home/706089/description#description
Sample chapter: http://www.oracle.com/technology/books/pdfs/mensah_ch1.pdf
Kuassi

App Memory Leak When Open iPhoto

Hi everyone,
Does anyone have experienced app memory leak when open iPhoto? My free memory immediate dropped from 5000 mb to 15mb when I open iPhoto and the app never open. If I force to quit iPhoto, all return to normal and everything work fine. I only have iPhoto app running, not sure what caused the memory leak???
Looking for help.
Thanks
JHML

Actually the new library was a test to see if the problem occurred only with your current library or with all libraries. The fact that switching libraries cleared up the problem is just serendipitous.

Memory leak when using Threads?

I did an experiment and noticed a memory leak when I was using threads.. Here's what I did.
======================================
while( true )
     Scanner sc = new Scanner(System.in);
     String answer;
     System.out.print("Press Enter to continue...");
     answer = sc.next();
     new TestThread();
========================================
And TestThead is the following
========================================
import java.io.*;
import java.net.*;
public class TestThread extends Thread
public TestThread() { start(); }
public void run() { }
=====================================
When I open windows Task Manager, every time a new thread starts and stops, the java.exe increases the Mem Usage.. Its a memory leak!? What is going on in this situation.. If I start a thread and the it stops, and then I start a new thread, why does it use more memory?
-Brian

MoveScanner sc = new
Scanner(System.in);out of the
loop.Scanner sc = new Scanner(System.in);
while (true) {
That won't matter in any meaningful way.
Every loop iteration creates a new Scanner, but it also makes a Scanner eligible for GC, so the net memory requirement of the program is constant.
Now, of course, it's possible that the VM won't bother GCing until 64 MB worth of Scanners have been created, but we don't care about that. If we're allowing the GC 64 MB, then we don't care how it uses it or when it cleans it up.

Memory Leak when TOMCAT connects to Oracle 10g RAC using JDBC Thin driver.

We had experienced Memory leak when a Oracle 10g (10.2.0.3) RAC node was evicted. TOMCAT app server is connecting to the Oracle 10g RAC database instances using JDBC 10.2.0.3 thin driver.
Anyone had similar experience?
Any ideas? Any bugs reported/fixed?
Thanks,
Raj

If you're doing XA, we absolutely do not support
driver-level load-balancing OR failover. Use neither.
For non-XA, you can use driver-level failover. For
non-XA, you could set load-balancing, but it won't
help because we get connections from the driver,
and keep them indefinitely, so the driver never gets
the chance to affect which connections the pool
uses after that.

Memory leak when transferring files Lion

hi all, help I'm experiencing a memory leak since upgrading to Lion when transferring shared files between my macbook pro and imac. This occures through ethernet (wireless/wired) and firewire 800. No other apps are open except activity montior and finder. I am trying to transfer about 100g of itunes music / video files and pictures. Time machine backups to my TC do not have this affect.
When transfer starts the free memory slowly decreases whilst the inactive memory increases. Eventually the free memory drops below 10mg, active memory is approx 5-6gb and wired/active is about 2gb. Bascially as the free memory decreases the inactive memory increases however does not get realocated so the mac grinds to a halt and dies with lots of page outs etc.
this only happens when trying to transfer files. I have tried whole folders and just small individual ones and noticed the same event. I am struggling to find the cuase of the problem - any ideas?
mac os x 10.7.1
processor 2.53 GHz Intel Core i5
Memory 8 GB 1067 MHz DDR3
cheers, Kevin

I dont think you have a memory leak. I think the problem is the xml file is 1000000 records long and takes up too much memory. Even if you find a way to increase memory size, you are loading down the server too much for other people's applications to run. I suggest instead reading up on xml and learning how to read in only a few records at a time, processing it, and getting the next set of records to process. There are two methods to parse an xml file using an xml parser, one is to parse it all and put it in memory, the other is to process one record at a time (an xml book explains it better).
However, I question why you have reports that are 1000000 records long. end-users cannot effectively use such records (you cant scroll through 1000000 records). I suggest finding a way to greatly decrease the number of records in each file such as by providing just the records a particular user needs to do his job and not all records. For instance, put a textfield on his screen to let him only fetch records within a certain date range.
Lastly, I suggest putting your code in a try/catch/finally block where the finally block actually closes the objects. Example:
finally{
if(conn!=null)
conn.close();
}

Memory leak when transferring pdf...help needed

Dear All,
I'm a newbie in developing java app. I'm making a web based application in reporting using JSP. java 1.6.02, jasper report 204, i-report 2.0.0
Client : OS : Win xp, memory 512MB
Server : Tomcat 6.0
DB Server : SQL Server 2005
OS Server : Windows Server 2003, memory 1GB
Report spec : .pdf based, with up to 1million record
Here's the code :
String query;
        try {
        String filereport = request.getRealPath("division/accounting/template/POReport.jrxml");
        InputStream input = new FileInputStream(filereport);
        Class.forName(odbcDriver);
        Connection conn = DriverManager.getConnection(odbcURL,username,passwd);
        ResultSet rset = null;
        CallableStatement cs = null;
        query = "{ call sp_tpo_list }";
          cs = conn.prepareCall(query);
          rset = cs.executeQuery();
        JRDataSource dataSource = new JRResultSetDataSource(rset);
        JasperDesign design = JRXmlLoader.load(input);
        JasperReport report = JasperCompileManager.compileReport(design);
        JasperPrint print = JasperFillManager.fillReport(report, null, dataSource);
        ByteArrayOutputStream baos = new ByteArrayOutputStream();
        JasperExportManager.exportReportToPdfStream(print, baos);
        response.setContentType("application/pdf");
        response.setContentLength(baos.size());
        ServletOutputStream sos;
        sos = response.getOutputStream();
        baos.writeTo(sos);
        sos.flush();
        rset.close();
        cs.close();
        conn.close();
        sos.close();
        baos.close();
        input.close();
        catch (FileNotFoundException fe) {}
        catch (JRException jre) {}
        catch (ClassNotFoundException cnfe) {}
        catch (SQLException sqle) {}
        catch (IOException ioe) {}I've already increase heap memory in Tomcat Manager -Xms 64Mb -Xmx 512Mb.
But when i test with 1million record, out of heap memory error is coming out.
When i test with 500.000 record, it work out, but only when 1 client access. More than 1 client, out of heap memory error generated by the system.
How can this happen? How can i detect memory leaks occured in the program?
And pls let me know if you see something is missing in the code above.
Thank you

I dont think you have a memory leak. I think the problem is the xml file is 1000000 records long and takes up too much memory. Even if you find a way to increase memory size, you are loading down the server too much for other people's applications to run. I suggest instead reading up on xml and learning how to read in only a few records at a time, processing it, and getting the next set of records to process. There are two methods to parse an xml file using an xml parser, one is to parse it all and put it in memory, the other is to process one record at a time (an xml book explains it better).
However, I question why you have reports that are 1000000 records long. end-users cannot effectively use such records (you cant scroll through 1000000 records). I suggest finding a way to greatly decrease the number of records in each file such as by providing just the records a particular user needs to do his job and not all records. For instance, put a textfield on his screen to let him only fetch records within a certain date range.
Lastly, I suggest putting your code in a try/catch/finally block where the finally block actually closes the objects. Example:
finally{
if(conn!=null)
conn.close();
}

Memory leak when running in database

I am somewhat new to java and very new to java in the db. I just ran into a problem with what appears to be a memory leak. I have a substantial java program used to parse XML files. I developed this app in jDeveloper and for testing purposes created a method that would connect to the database so that I could run the app from jDeveloper instead of having to deploy it everytime i needed to run it. When deployed the application uses the existing connection to connect to the db.
I am running Oracle 9i on a windows 2k machine.
When I run the application through jDeveloper the javaw.exe process takes up roughly 20mb of RAM and doesn't increase. I also watched the oracle.exe process and there was little to no increase in the RAM that it was using.
When deployed to a db and run through a java stored procedure the RAM used by the oracle.exe process sky rockets, jumping from 70mb to 139mb at about 2mb per second.
Hopefully this will make some sense to someone as posting code would be somewhat difficult considering the size of the project. Is there something I'm missing? I've tried calling the garbage collector explicity but it has had no effect. I have made sure that all my cursors, statements, resultsets are closing. I have a number of Vecotors which are all being de-allocated(as far as i can tell). Are there any known issues with the garbage collector in a 9i DB?
Thanks
Butch Wesley

The size of oracle.exe is not an indication of how the Java VM GC works; so you are not comparing apples to apples. It'll be too long to explain here but in my upcoming book (see hereafter), I gave a detailled explanation of the various memory areas the Java VM uses and how these are GCed and also how you can meausre their size (not all, though).
In short you want to use OracleRuntime methods such as
OracleRuntime.getSessionSize(); --> get he current size of Sessionspace
OracleRuntime.getNewspaceSize(); --> get he current size of Newspace
there are other memory areas described in the book
http://www.oracle.com/technology/pub/articles/mensah_dws.html
http://www.elsevier.com/wps/find/bookdescription.cws_home/706089/description#description
Sample chapter: http://www.oracle.com/technology/books/pdfs/mensah_ch1.pdf
Kuassi

I am experiencing a memory leak when I write to a file in a loop.

I am conducting a cycling test, each cycle represents about 48k of memory. I collect a selectable number of cycles into a shift register. When the chosen number of cycles is reached, I write the data to text files and then clear out the shift register. Unfortunately, I do not free up any memory space when this happens. I have been able to isolate the memory leak to the file writing function. I thought I was closing the reference when I closed the file, but apparently that is not happening. What space I free up by clearing the buffer, is cancelled by the memory required to make a reference to the file (I am guessing). This is all happening in a loop that must run as many as 500,000 times. Ideally, I
would like to write as many as 1500 records at a time. At this point the memory leak makes this almost impossible. I have ordered some more memory, but I would rather plug the leak. I have read that LabView leaves a reference open to the file even after the file is closed. What can I do to clear the memory used up by leaving the reference open? Any insights would be very appreciated.

The behaviour you describe is strange. Something to try: Open a refernce to the file one time before entering the loop, then inside the loop use that reference to do all the writing. Finally close the reference when the loop completes.If this doesn't work, post your code in 6.0 format and I'll be glad to look at it.Mike...
Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion
"... after all, He's not a tame lion..."
Be thinking ahead and mark your dance card for NI Week 2015 now: TS 6139 - Object Oriented First Steps

TestStand 2010 Memory Leak when calling sequence in New Thread or New Execution

Version: TestStand 4.5.0.310
OS: Windows XP
Steps to reproduce:
1) Unzip 2 attached sequences into this folder: C:\New Thread Memory Leak
2) Open "New Thread Memory Leak - Client" SEQ file in TestStand 2010
3) Open Task Manager, click Processes tab, sort A-Z (important), and highlight the "SeqEdit.exe" process. Note the memory useage.
4) Be ready to click Terminate All in TestStand after you see the memory start jumping.
5) Run the "New Thread Memory Leak - Client" sequence.
6) After seeing the memory consumption increase rapidly in Task Manager, press Terminate All in TestStand.
7) Right click the "While Loop - No Wait (New Thread)" step and set Run Mode » Skip
8) Right click the "While Loop - No Wait (New Execution)" step and set Run Mode » Normal
9) Repeat steps 3 through 6
I've removed all steps from the While Loop to isolate the problem. I've also tried the other methods you'll see in the ZIP file but all cause the memory leak (with the exception of the Message Popup).
I have not installed the f1 patch, but none of the bug fixes listed appear to address this issue. NI Applications Engineering has been able to reproduce the issue (with Windows 7) and is working on it in parallel. That said, are we missing something??
Any ideas?
Certified LabVIEW Architect
Wait for Flag / Set Flag
Separate Views from Implementation for Strict Type Defs
Solved!
Go to Solution.
Attachments:
New Thread Memory Leak.zip ‏14 KB

Good point Doug. In this case parallel sequences are being launched at the beginning of the sequential process model, but I'll keep that in mind for later. Take away: be intentional about when to wait at the end of the sequence for threads to complete.
Certified LabVIEW Architect
Wait for Flag / Set Flag
Separate Views from Implementation for Strict Type Defs

ADO memory leak when getting Recordset from an Oracle stored procedure?

I am programming in C++ (VC 6) and using ADO 2.7 to
access Oracle 9i database. My connection string looks
like this:
Provider=MSDAORA.1;Persist Security Info=True;User ID=scott;Password=tiger;Data Source=blahblah
I have Oracle stored procedure that returns data in a
REF CURSOR output parameter. Since the stored procedure
takes input parameters, I prepare a Command object with
Parameters initialized and attached to it. I use the
Recordset Open method to execute the call. This approach
works because I get correct data back from the call in
the Recordset, but the problem is when I do this in a
infinite loop and watch the process in Windows Taks
Manager, I see 4k or 8k memory delta all the time and
the Peak Memory Usage of the process keeping going up.
I hope someone knows something in this scenario and points
me to the right direction.
Thanks, please see the following code for specifics.
HRESULT CallSP3Params(VARIANT vp1, VARIANT vp2, int spretcode, LPDISPATCH ppRSet, char *pCmdLine)
     _RecordsetPtr     pRs;
     _CommandPtr     pCmd;
     _ParameterPtr     paramVProfiler[3];
     bstrt          strMissing(L"");
     *ppRSet = NULL;
     variantt          ErrConn;
     ErrConn.vt = VT_ERROR;
     ErrConn.scode = DISP_E_PARAMNOTFOUND;
     try {
     //Create instance of command object
     pCmd.CreateInstance(__uuidof(Command));
     pRs.CreateInstance(__uuidof(Recordset));
          if ( vp1.vt == VT_BSTR ) {
               paramVProfiler[0] = pCmd->CreateParameter("P1",adVarChar,adParamInput,SysStringLen(vp1.bstrVal) + 10,strMissing );
               paramVProfiler[0]->Value = vp1;
          else if ( vp1.vt == VT_I4 )
               paramVProfiler[0] = pCmd->CreateParameter("P1",adNumeric,adParamInput,15,vp1);
          else
               TESTHR( PARAMETER_OPERATION_ERROR );
          pCmd->Parameters->Append(paramVProfiler[0]);
          if ( vp2.vt == VT_BSTR ) {
               paramVProfiler[1] = pCmd->CreateParameter("P2",adVarChar,adParamInput,SysStringLen(vp2.bstrVal) + 10,strMissing );
               paramVProfiler[1]->Value = vp2;
          else if ( vp2.vt == VT_I4 )
               paramVProfiler[1] = pCmd->CreateParameter("P2",adNumeric,adParamInput,15,vp2);
          else
               TESTHR( PARAMETER_OPERATION_ERROR );
          pCmd->Parameters->Append(paramVProfiler[1]);
          paramVProfiler[2] = pCmd->CreateParameter("RETCODE",adNumeric,adParamOutput,10);
          pCmd->Parameters->Append(paramVProfiler[2]);
     //Catch COM errors
     catch( comerror &e) {
     try {
     // I manage my connection through this little C++ class of my own
     CCUsage myconnection( &Connectionkeeper[0] );
     //Set the active connection property of command object to open connection
     pCmd->ActiveConnection = myconnection.m_conn;
     //The command type is text
     pCmd->CommandType = adCmdText;
     //Set command text to call the stored procedure
     pCmd->CommandText = pCmdLine;
     //Open the Recordset to get result
     pRs->Open( variantt((IDispatch *)pCmd,true), ErrConn, adOpenStatic, adLockReadOnly, adOptionUnspecified );
     //Disconnect the command object
     pCmd->PutRefActiveConnection( NULL );
     if ( GetSPRetCode( pCmd, "RETCODE", spretcode ) != S_OK )
          TESTHR(DB_OBJECT_OPERATION_ERROR);
     // pRs->QueryInterface(IID_IDispatch, (void**) ppRSet);
     // I return the Recordset by calling QueryInterface, but even without that, closing the Recordset right here still shows memory leak.
     pRs->Close( );
     pRs = NULL;
     //Catch COM errors
catch (_com_error e) {
     return S_OK;
}

Whenever large numbers of BSTRs are allocated and freed quickly the process memory will continue to climb towards a stabalizing value. BSTRs are not freed until the system frees them. You can see this by making many calls allocating and freeing BSTRs, memory will climb, but when you stop for a while the gargage collection of the sys strings will take place. I've done much research to see that a server doing many queries very rapidly is not leaking memory, but out pacing the garbage collection, it will stabilize and when the process has some "rest time" the processes memory usage will decline.
In my research a suspected memory leak was not one.

Memory Leak when just launched and Idle.. fixes when being used ?? [HELP]

So I'm in the debugging and testing phase of my app and using this tool for tracking memory leaks ( https://github.com/mrdoob/Hi-ReS-Stats )
When I launch my app my numbers are
FPS: 61/60
MS: 17
MEM: 3.157
MAX: 3.157
Now immediately my memory starts increasing    from 3.157, 3.167, 3.177, 3.187, 3.197 and so on.
Now if I make any nav selection in my app
MEM changes back down to about 3.215
but then it starts its count again   3.215, 3.225, 3.235, 3.445, 3.455
I don't have any loops happening.
Has anyone run in to this ?
I'm almost tempted to force garbage collection every 60 seconds that the app is idle or something. Not the best way to handle this ..   I just dont know where the leak is happening.
Any support is appreciated!
Cheers!

Hi there - I just had the same query a couple of days ago (http://forums.adobe.com/thread/977174?tstart=30).
I saw the same symptoms on my app so I built a blank app with just the profiler on stage. I've been monitoring it for a few days now and notice that memory does creep up even when the app is left idle (apart from the profiler) - but ... and this is the important bit ... it does periodically get reduced back to the starting point (when the garbage collector kicks in and memory is released).
When I was monitoring my app the time through this cycle could be well over 5 mins.
If you actually use the monitor when putting your app through it's paces you'll see memory being gobbled up more rapidly and hopefully (if you've no leaks) the garbage collection kicking in more regularly and bringing the reported usage back down.

Makequeues memory leak when using Lexmark Z53

Behavior with printer switched off while connected to built-in USB port:
Problem 1: makequeues has a memory leak, starting up with between 3 and 5 MB of RAM. This is done by connecting the printer when logged in and watching via Activity Monitor.
Initially makequeues has sent 255 Mach messages. Every ~10.5 seconds, makequeues sends 59 more messages and gets 53 in reply. With each send/receive cycle, its RAM usage grows by 8 KB, a rate of 780 kiB/min.
Problem 2: The process is started each time the same printer is reconnected.
Symptoms: Disconnecting the printer doesn't let the process exit (any instance). If left alone, the memory usage cycle continues.
The memory leak caught my attention after taking up over a half-gigabyte of RAM when I left the Mac running over night.
Resolution:
(1) Disconnect USB cable
(2) Kill each instance of the process
Results:
(1) The process launches after reconnection of the printer with 996 KB of RAM, immediately having sent 60 Mach messages and received 56.
(2) During this run time, the process may use less and less RAM, down to a minimum of 912.
(3) After sending 64 more messages without replies, one every 4 seconds, the process exits after having sent a total of 120 messages.
(4) This behavior (1 through 3) is the same for each process launched as a result of printer reconnection.
This behavior isn't shown during Safe Mode boot - makequeues never starts up as a result of printer connection.
PowerMac G4 QuickSilver 2001 733Mhz

If this is meant to be a bug report, please file a bug report in the proper place. This is a user to user discussion forum.
As to the source of running 'makequeues' (/System/Library/SystemConfiguration/PrinterNotifications.bundle/Contents/MacOS /makequeues), I would look at the Lexmark software. I currently have two Epson printers connected via USB with CUPS running. I see no process 'makequeues' appearing.
Matt

Photoshop CS6 memory leak when idle and nothing open

Photoshop CS6 runs away with memory after being used and then going idle. If I open up PS and leave it, it will be ok but as soon as I open any file it will go up in memory usage (which is normal) but when I close all files and hide PS the memory will stay high never goes back down. When I close PS and re-open (no files open) again it idles at 300Mb memory but when I open a file then close it and then hide/idle PS it raises and stays around 1.25-1.5 GB if not more.
I have tried to Purge All, and even hide all menus to no avail. I have even tried to close Suitcase (eleminiate any font issues) and still same problem. I am running PS bone stock, no extra plug-ins.
Any ideas on why it would be doing this would be greatly appreciated!
My Computer:
Photoshop 13.0.1
MacBookPro
OS 10.6.8
CPU: 2.66 GHz Intel Core 2 Duo
Mem: 4 GB 1067 MHz DDR3
HD: 300GB (30GB Free)

Photoshop is not supposed to free memory when you close documents -- that's normal, because the memory gets reused.
Yes, opening a file makes the memory usage go up - because space is needed for the document and it's window.
None of what you said describes a leak, and sounds like perfectly normal behavior.

Huge memory leak when closing PDF from Hyperlink

I was wondering if anyone else has experienced this issue with Adobe Reader 11.0.10 on Windows 7 64bit:
1. I have a list of hyperlinks in an Access Table to certain PDF files on a local network folder.
2. Clicking the hyperlink opens the corresponding PDF.
The PDF file opens just fine, and renders normally. The issue is when I attempt to close the PDF. This results in an instant Memory leak that will grow to 4GB in under 10 seconds. System crashes completely. I can reproduce the crash in Safe Mode as well. I am able to open/close the PDF from its source location normally without incident. Clean Uninstall/Reinstall produces the same results.
Downgrade to Adobe 10 fixes the problem completely. I can reproduce the problem on all computers on my network (all running windows 7 32bit or 64bit) by upgrading to Reader 11.0.10.
I prefer to keep my software updated to prevent vulnerabilities, so any help would be appreciated.

That is very strange because it is a 32-bit program and cannot (according to popular wisdom) grow over 2 GB. Also, if it were to reach 2 GB it would simply crash, not break the system.
Do you have a screen shot showing the 4 GB? There might be clues there what is happening.

Memory leak when browsing through records

Similar Messages

Maybe you are looking for