Effective tool for GDI memory leaks detection

Hello!
Would you advice me some effective tool for GDI memory leaks and run-time errors detection in VC++?
Thanks!

926007 wrote:
This forum is about Java.No, this forum is about C++.
Please notice the name of the forum: "Solaris Studio *C++*", under the category "Application Development in C, C++, and Fortran".
There are other forums for Java, listed here:
https://forums.oracle.com/forums/category.jspa?categoryID=285

Similar Messages

Oracle 9.2 and memory leak detection

Hi All.
I have found the following error in trace file
after shutdown database.
=================================================================
/.../udump/cpaw_ora_4427.trc
Oracle9i Enterprise Edition Release 9.2.0.1.0 - Production
With the Partitioning, Oracle Label Security, OLAP and Oracle Data Mining options
JServer Release 9.2.0.1.0 - Production
ORACLE_HOME = /.../product/9.2.0
System name: Linux
Node name: host.com
Release: 2.4.18-10bigmem
Version: #1 SMP Wed Aug 7 10:26:52 EDT 2002
Machine: i686
Instance name: orcl
Redo thread mounted by this instance: 0 <none>
Oracle process number: 10
Unix process pid: 4427, image: [email protected] (TNS V1-V3)
*** SESSION ID:(9.3) 2002-10-10 14:17:14.265
Archiving is disabled
Archiving is disabled
******** ERROR: SGA memory leak detected 16 ********
KGH Latch Directory Information
ldir state: 2 next slot: 39
Slot [ 1] Latch: 0x50005be8 Index: 1 Flags: 3 State: 2 next: (nil)
<...>
=====================================================================
Linux RedHat 7.3 (db works in archivelog mode).
How can I correct this?
Thanks in advance.
Best regards,
Andrey Demchenko.

Thanks for the answers. The oci8.dll is uncommented naturally. Otherwise it would start up just fine, but I couldn't use the database functions.
I got it working by installing 5.1.6, but replacing the oci8.dll with the one from the 5.1.0 -version. It's a very... desperate... solution, but at least it works.
I'm gonna have to try to sell the idea of using the 10g client to our DBA. I don't think though, that he'll be very enthusiastic to set it up on our production servers. We'll see.

PGA memory leak detected

Hi all,
I using Database version 9.0.2.1 on Windows.
In Udump\.....trace file have a message:
*** 2004-04-11 13:28:58.000
*** SESSION ID:(4.1) 2004-04-11 13:28:57.000
******** ERROR: PGA memory leak detected 10340 > 6004 ********
HEAP DUMP heap name="pga heap" desc=001CDF10 ....
and then about 1-2 hours, my database is down (not connect) (error: ORA=3113: end of file communicational...)
I think, cause is PGA memory too large, may be ? I set value of PGA = 80-100 MB.
My server has 1.5GB RAM, (SGA = 900, Shared Mem=500, Buffer mem= 150..). It's correct ?
Please help me to resolve this problem.!!!!!
Thanks
[email protected]

Hi ER,
It seems that you need to Update Patch - 9.2.0.6 which will solve this PGA Memory Leak!
Check this Doc ID: Note:283897.1 in Metalink!
Ravi Prakash

IFS ALERT NOTICE FOR JDBC MEMORY LEAK FIX

IFS ALERT NOTICE FOR JDBC MEMORY LEAK FIX
Product and Version Affected:
Product: Oracle Internet File System
Product ID: 7
Version: 1.0
Description: There is a memory leak when retrieving or saving BLOBs through JDBC. IFS will appear to continue to increase in its memory consumption until the user runs out of swap space, and the machine stops functioning.
Platform Affected: Sun SPARC Solaris, Windows NT
Likelihood of Occurrence: Most iFS customers will notice this problem, since most will retrieve and store enough document content that they will notice the memory leak.
Symptoms:
- Performance becomes unacceptable on a minimally configured machine when doing significant retrievals and storage of documents.
- Significant swapping of the operating system.
- The user sees real memory and total memory continue to increase without bound when using any iFS protocols to retrieve and store document content.
- The memory usage goes back to normal when the iFS protocols are stopped.
Solution: Get the JDBC 8.1.6.0.1 patch for Solaris or NT (the OCI component, for JDK 1.1). Install it on all machines where the iFS protocols are running. The patch may be obtained on http://technet.oracle.com/software/tech/java/sqlj_jdbc/software_index.htm (you have to be logged into technet).
Be sure to get the OCI component of JDBC 8.1.6.0.1 for JDK 1.1.
null

Moving to Top

UGA memory leak detected 1488

Hi all,
I am getting the following error in the database alert log.
ORA-00600: internal error code, arguments: [729], [2216], [space leak], [], [], [], [], []
when checked the trace file in which the details are dumped. The error line says
*** 2004-01-07 18:09:00.002
*** SESSION ID:(123.21632) 2004-01-07 18:08:59.981
******** ERROR: UGA memory leak detected 2216 ********
HEAP DUMP heap name="session heap" desc=0x80000001000b10f0
extent sz=0x10a8 alt=32767 het=32767 rec=0 flg=3 opc=3
parent=8000000100007450 owner=c00000003785c750 nex=0 xsz=0x4098
EXTENT 0
Can anyone help me in this issue.
Thanks in advance.
Regards
Shoyeb

Generally error ORA-00600 is very complex to understand and in almost all cases that error is tried with Oracle Support. http://metalink.oracle.com . You have to have an account to open an iTAR and so on.
Joel P�rez

Memory leak detecting tools for Solaris 10 X86

Hi All,
Greetings!
We are experiencing a crash defect while porting our application from Sol4 to Sol10.
Stack trace :
(dbx) where
=>[1] realfree(0x81b7d60), at 0xfeac3237
[2] freeunlocked(), at 0xfeac37e9
[3] free(0x831f1a8), at 0xfeac376f
[4] tLList_Done(0x831f1a8), at 0x8074255
[5] tKeyFile_Free(0x8306c60), at 0x8075af5
[6] tKeyFile_Done(0x8306c60), at 0x8075c6c
[7] tBGA_Var_Adj_LD(0x81b5eb0, 0x8302b48, 0x0), at 0x807a5f7
[8] tGen_Var_GenLead(0x81b5eb0, 0x8302b48, 0x0, 0x1), at 0x807b6e7
[9] tBGA_Var_GenLead(0x81b5eb0, 0x8302b48, 0x0, 0x1), at 0x807a7f8
[10] tCPD_DevProc_Init_Lead(0x825e6e8, 0x8302b48, 0x0, 0x1), at 0x809b363
[11] tCPD_DevProc_Init_Data(0x825e6e8, 0x8302b48, 0x0, 0x0, 0x0, 0x0, 0x1), at 0x809b970
[12] TrayRep_Execute(0x81b1cb4), at 0x80aab45
[13] TrayRep_RunFrom(0x0, 0x0), at 0x80a997a
[14] main(0x0, 0x804770c, 0x8047710), at 0x80a946a
We suspect it to be a memory leak issue. Are there memory leak debugging tools for sol10.
we were unable to use dbx as we got the following error.
(dbx) check -memuse
dbx: Incompatible libthread.so/libthread_db.so found. Error checking disabled
See `help rtc mt' for details.
Also dbx's 'check -access' option is not supported for X86.
Waiting eagerly for any support/guidance.
Thanks in advance.
Deepak

I had the same problem on Solaris 10 sparc. The problem seems to relate to symbolic links with
long names not being extracted correctly from the tar file (resulting in @LongLink files popping
up around the place). If you use the .zip source file then the build goes fine.
Philip.

Tool to check memory leak

One of tmy applications has memory leak sometimes, not always. I find most tools to check the memory leak needs to reproduce the leak, but now I can not reproduce this issue, is there any tool to analyze the source code to find the memory leak?

Don't know about source code analyzer, but dbx, the Sun Studio debugger, is capable of detecting memory leaks at run time. You can use bcheck script on your application or start dbx, issue "check -leaks" and then run your app under dbx.

Best Practices for EJB--memory leak avoidance

I an researching a memory leak. From what I can tell, we do not want to put any instance variables at the class level. This would incur a memory leak when the ejb containers creates the ejb.
I am wondering if there are any more 'best practices' with EJBs that prevent memory leaks. A good site would help me too
Russ

Thank for your reply.
You are right. I was referring to stateless session
beans.
What I was thinking was the following:
1. Making parameters final unless the parameter
r state is changed inside a method.Won't help with memory leaks. There are benefits for an object being immutable, but I don't think that it eliminates the possibility of the object being leaked.
2. All instance variables in stateless session beans
s should be set to null upon ejbPassivate and
ejbRemove operations. The variables should be
populated on ejbCreate and ejbActivate.Optimizing compilers don't need the hint of setting the reference to null. I don't think that helps, but I'm not 100% certain.
3. Before throwing an exception at the session bean
level, clear up all the instance variables by setting
them to null.Shouldn't scope make it clear to the GC that the objects aren't needed? If they're all primitives, how does this help memory leaks?
I am using a profiler to identify the objects still
being held onto once GC, but I was hoping others with
more experience than I would share some of their tips
on how they avoid memory leaks.I don't know where you're getting these tips, but I don't think they're helpful.
Collections and Singletons would be the places where I'd look. If you add a reference to an object that holds onto it in a collection and never lets go, the GC won't reclaim it.
Singletons aren't cleaned up, because their instance is static. Anything the Singleton refers to won't be cleaned up unless the Singleton relinquishes the reference.
Look for things like that. I think they matter more.
%

ThreadLocalObject memory leak detected (Weblogic 8 SP6)

It seems that our application server (which heavily uses Entity and Stateless session beans) constantly creates weblogic.ejb20.internal.BaseEJBObject,ThreadLocalObject's in memory. These objects keep increasing and never go down.
In a typical 90 hr run we create upto 22,000,000 instances of these objects. Could someone explain what these are used for and how to fix this issue.

Before you assume you have a memory leak, go to the "Monitoring"->"Performance" page of your server config. Set the page to auto-refresh (I think you can do that in 8.1). While your application is doing its work continuously, every 30 seconds or so, push the "garbage collect" button and watch the "percent free" amount immediately after the GC completes. Keep track of that number. If that number (the one after the GC completes) is continuously going down, and eventually causes an OutOfMemory error, then you have a memory leak. If not, then you probably don't.

AVConversionConvertFromPDFWithHandler for jpeg memory leak?

Hi,
I'm trying to utilize this AVConversionConvertFromPDFWithHandler call in my plugin to convert single page PDF into JPEG file. I've added available memory trace before and after this call and I have this data (in bytes here):
2010.10.12 23:24:07:515 pid: 5612, tid: 7080: Memory before AVConversionConvertFromPDFWithHandler: 1038352384
2010.10.12 23:24:12:546 pid: 5612, tid: 7080: Memory after AVConversionConvertFromPDFWithHandler: 1028227072
So, you could see that AVConversionConvertFromPDFWithHandler ate about 10 MB of memory.
My test PDF is 22 KB in size and generated JPEG is 387 KB. Why do we have such huge memory consumption? Do I need to call some special cleanup after that call is done?
The version of Adobe ImageConversion.api plugin, which is involved in that conversion is 9.3.3.177. I'm running that on Windows XP.

Memory grows each time with that call. Look at this:
2010.10.13 00:13:51:109 pid: 6352, tid: 6596: Memory before AVConversionConvertFromPDFWithHandler: 1035579392
2010.10.13 00:13:56:468 pid: 6352, tid: 6596: Memory after AVConversionConvertFromPDFWithHandler: 1025404928
2010.10.13 00:14:45:968 pid: 6352, tid: 6596: Memory before AVConversionConvertFromPDFWithHandler: 990334976
2010.10.13 00:14:51:515 pid: 6352, tid: 6596: Memory after AVConversionConvertFromPDFWithHandler: 988655616
2010.10.13 00:15:45:374 pid: 6352, tid: 6596: Memory before AVConversionConvertFromPDFWithHandler: 966565888
2010.10.13 00:15:49:812 pid: 6352, tid: 6596: Memory after AVConversionConvertFromPDFWithHandler: 964751360
2010.10.13 00:16:48:421 pid: 6352, tid: 6596: Memory before AVConversionConvertFromPDFWithHandler: 941375488
2010.10.13 00:16:53:062 pid: 6352, tid: 6596: Memory after AVConversionConvertFromPDFWithHandler: 939618304
Well, while it doesn't grow each time by 10 MB as with initial call, it still grows by about 2 MB on each call after that.
So, if called in that way for let say 101 PDFs - then I'll loose about 210 MB of memory and if I want to process even more files without Acrobat restart - probably it will crash at some point.

CS3: Leaks.txt - How can I find the reason for the memory leaks?

Hi I get the following messages in Leaks.txt, created from the memory tracker (Windows): ------------------------------------------------------------------------ Leaks! 13 leaks, 845468 bytes 65036 bytes at: 5B42FE0 4172627C MemoryPool::GetNonPoolSizePeak cannot be found in any module! 44D8D23B K2Internals::K2VectorBase<Schemas::SchemaInfo,K2Allocator<Schemas::Sc hemaInfo> >::erase cannot be found in any module! 0039C74F cannot find address in any module! 00396DEC BIBGetVersion cannot be found in any module! 00396E60 BIBGetVersion cannot be found in any module! 003979E4 cannot find address in any module! 451D3A61 K2Internals::K2VectorBase<Schemas::SchemaInfo,K2Allocator<Schemas::Sc hemaInfo> >::erase cannot be found in any module! 451D3A14 K2Internals::K2VectorBase<Schemas::SchemaInfo,K2Allocator<Schemas::Sc hemaInfo> >::erase cannot be found in any module! 44D8CCEE K2Internals::K2VectorBase<Schemas::SchemaInfo,K2Allocator<Schemas::Sc hemaInfo> >::erase cannot be found in any module! 44D8D02E K2Internals::K2VectorBase<Schemas::SchemaInfo,K2Allocator<Schemas::Sc hemaInfo> >::erase cannot be found in any module! 44D8D5C8 K2Internals::K2VectorBase<Schemas::SchemaInfo,K2Allocator<Schemas::Sc hemaInfo> >::erase cannot be found in any module! 1002C26E cannot find address in any module! 1002BFB9 cannot find address in any module! 00401644 cannot find address in any module! 00405146 cannot find address in any module! 00404EBD cannot find address in any module! 7C816FD7 RegisterWaitForInputIdle cannot be found in any module! 65036 bytes at: 5B52E30 4172627C MemoryPool::GetNonPoolSizePeak cannot be found in any module! 44D8D23B K2Internals::K2VectorBase<Schemas::SchemaInfo,K2Allocator<Schemas::Sc hemaInfo> >::erase cannot be found in any module! 0039C74F cannot find address in any module! 00396DEC BIBGetVersion cannot be found in any module! 4FEC149B cannot find address in any module! 4FEC4C63 cannot find address in any module! 44D8CD53 K2Internals::K2VectorBase<Schemas::SchemaInfo,K2Allocator<Schemas::Sc hemaInfo> >::erase cannot be found in any module! 44D8D02E K2Internals::K2VectorBase<Schemas::SchemaInfo,K2Allocator<Schemas::Sc hemaInfo> >::erase cannot be found in any module! 44D8D5C8 K2Internals::K2VectorBase<Schemas::SchemaInfo,K2Allocator<Schemas::Sc hemaInfo> >::erase cannot be found in any module! 1002C26E cannot find address in any module! 1002BFB9 cannot find address in any module! 00401644 cannot find address in any module! 00405146 cannot find address in any module! 00404EBD cannot find address in any module! 7C816FD7 RegisterWaitForInputIdle cannot be found in any module! 65036 bytes at: 5B72D20 4172627C MemoryPool::GetNonPoolSizePeak cannot be found in any module! 44D8D23B K2Internals::K2VectorBase<Schemas::SchemaInfo,K2Allocator<Schemas::Sc hemaInfo> >::erase cannot be found in any module! 0039C74F cannot find address in any module! 00396DEC BIBGetVersion cannot be found in any module! 4E1D1A7A cannot find address in any module! 4E212081 cannot find address in any module! 44D8CD8D K2Internals::K2VectorBase<Schemas::SchemaInfo,K2Allocator<Schemas::Sc hemaInfo> >::erase cannot be found in any module! 44D8D02E K2Internals::K2VectorBase<Schemas::SchemaInfo,K2Allocator<Schemas::Sc hemaInfo> >::erase cannot be found in any module! 44D8D5C8 K2Internals::K2VectorBase<Schemas::SchemaInfo,K2Allocator<Schemas::Sc hemaInfo> >::erase cannot be found in any module! 1002C26E cannot find address in any module! 1002BFB9 cannot find address in any module! 00401644 cannot find address in any module! 00405146 cannot find address in any module! 00404EBD cannot find address in any module! 7C816FD7 RegisterWaitForInputIdle cannot be found in any module! 65036 bytes at: 5CD1478 4172627C MemoryPool::GetNonPoolSizePeak cannot be found in any module! 44D8D23B K2Internals::K2VectorBase<Schemas::SchemaInfo,K2Allocator<Schemas::Sc hemaInfo> >::erase ca

Hi I get the following messages in Leaks.txt, created from the memory tracker (Windows): ------------------------------------------------------------------------ Leaks! 13 leaks, 845468 bytes 65036 bytes at: 5B42FE0 4172627C MemoryPool::GetNonPoolSizePeak cannot be found in any module! 44D8D23B K2Internals::K2VectorBase<Schemas::SchemaInfo,K2Allocator<Schemas::Sc hemaInfo> >::erase cannot be found in any module! 0039C74F cannot find address in any module! 00396DEC BIBGetVersion cannot be found in any module! 00396E60 BIBGetVersion cannot be found in any module! 003979E4 cannot find address in any module! 451D3A61 K2Internals::K2VectorBase<Schemas::SchemaInfo,K2Allocator<Schemas::Sc hemaInfo> >::erase cannot be found in any module! 451D3A14 K2Internals::K2VectorBase<Schemas::SchemaInfo,K2Allocator<Schemas::Sc hemaInfo> >::erase cannot be found in any module! 44D8CCEE K2Internals::K2VectorBase<Schemas::SchemaInfo,K2Allocator<Schemas::Sc hemaInfo> >::erase cannot be found in any module! 44D8D02E K2Internals::K2VectorBase<Schemas::SchemaInfo,K2Allocator<Schemas::Sc hemaInfo> >::erase cannot be found in any module! 44D8D5C8 K2Internals::K2VectorBase<Schemas::SchemaInfo,K2Allocator<Schemas::Sc hemaInfo> >::erase cannot be found in any module! 1002C26E cannot find address in any module! 1002BFB9 cannot find address in any module! 00401644 cannot find address in any module! 00405146 cannot find address in any module! 00404EBD cannot find address in any module! 7C816FD7 RegisterWaitForInputIdle cannot be found in any module! 65036 bytes at: 5B52E30 4172627C MemoryPool::GetNonPoolSizePeak cannot be found in any module! 44D8D23B K2Internals::K2VectorBase<Schemas::SchemaInfo,K2Allocator<Schemas::Sc hemaInfo> >::erase cannot be found in any module! 0039C74F cannot find address in any module! 00396DEC BIBGetVersion cannot be found in any module! 4FEC149B cannot find address in any module! 4FEC4C63 cannot find address in any module! 44D8CD53 K2Internals::K2VectorBase<Schemas::SchemaInfo,K2Allocator<Schemas::Sc hemaInfo> >::erase cannot be found in any module! 44D8D02E K2Internals::K2VectorBase<Schemas::SchemaInfo,K2Allocator<Schemas::Sc hemaInfo> >::erase cannot be found in any module! 44D8D5C8 K2Internals::K2VectorBase<Schemas::SchemaInfo,K2Allocator<Schemas::Sc hemaInfo> >::erase cannot be found in any module! 1002C26E cannot find address in any module! 1002BFB9 cannot find address in any module! 00401644 cannot find address in any module! 00405146 cannot find address in any module! 00404EBD cannot find address in any module! 7C816FD7 RegisterWaitForInputIdle cannot be found in any module! 65036 bytes at: 5B72D20 4172627C MemoryPool::GetNonPoolSizePeak cannot be found in any module! 44D8D23B K2Internals::K2VectorBase<Schemas::SchemaInfo,K2Allocator<Schemas::Sc hemaInfo> >::erase cannot be found in any module! 0039C74F cannot find address in any module! 00396DEC BIBGetVersion cannot be found in any module! 4E1D1A7A cannot find address in any module! 4E212081 cannot find address in any module! 44D8CD8D K2Internals::K2VectorBase<Schemas::SchemaInfo,K2Allocator<Schemas::Sc hemaInfo> >::erase cannot be found in any module! 44D8D02E K2Internals::K2VectorBase<Schemas::SchemaInfo,K2Allocator<Schemas::Sc hemaInfo> >::erase cannot be found in any module! 44D8D5C8 K2Internals::K2VectorBase<Schemas::SchemaInfo,K2Allocator<Schemas::Sc hemaInfo> >::erase cannot be found in any module! 1002C26E cannot find address in any module! 1002BFB9 cannot find address in any module! 00401644 cannot find address in any module! 00405146 cannot find address in any module! 00404EBD cannot find address in any module! 7C816FD7 RegisterWaitForInputIdle cannot be found in any module! 65036 bytes at: 5CD1478 4172627C MemoryPool::GetNonPoolSizePeak cannot be found in any module! 44D8D23B K2Internals::K2VectorBase<Schemas::SchemaInfo,K2Allocator<Schemas::Sc hemaInfo> >::erase ca

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.

Detecting memory leaks in Managed C++

In my managed C++ application creating multiple variables dynamically using 'gcnew' and also some of the pointers being used.
Is there is any tool/mechanism to detect and avoid the memory leaks in Managed C++.
saikalyan

Hi saikalyan,
Is there is any tool/mechanism to detect and avoid the memory leaks in Managed C++.
You can use WinDbg tool to detect and avoid the memory leaks in Managed C++.
Please check this article:
http://www.codeproject.com/Articles/19490/Memory-Leak-Detection-in-NET
Best regards,
Shu Hu
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

How to configure JProfiler6 to monitor tomcat6.0 for memory leak

Hello,
Can anyone help. I am tring to work out the memory leak of my Web Application running on the local server. I have been told that jprofiler is a good tool for monitoring memory. I have dowloaded jprofiler6, but I dont know how to config the setting.
what i have done is:
1.from the Quickstart window->An application server, locally or remotely
2.follow the wizard step by step
1)choose application server Apache Tomcat 6.x
2)application is located "on this computer"
3) Chose JVM vendor
4) wait for a connection from the JProfiler GUI
5) Locate the start script :C:\Program Files\Apache Software Foundation\apache-tomcat-6.0.20\bin\startup.bat
6) port:8849
7)finished
After i done these, a error message came out said:
"Could not connect ot 127.0.0.1:8849.Please make sure that the remote address is correct, the remote program is started properly and the netword route allows socket connections."

Hi,
The recommended solution is to download Oracle JRockit Mission Control (available here: http://www.oracle.com/technology/software/products/jrockit/index.html) and install on your server. The installers include Oracle JRockit JVM as well as Mission Control, and are free of license checks.
If that solution for some reason is unfeasible you can download legacy development license files from here (http://download2.bea.com/pub/license/All%20Products/BEA_WebLogic.zip).
The license you are looking for is named “LIC-WLRT20.txt”. Rename it to license.bea, and follow the instructions at http://edocs.bea.com/jrockit/geninfo/diagnos/conf_run.html#wp1077371

KeyboardFocusManager reason for memory leak?

Hi all,
with a memory leak detector we found that our application has massive memory leaks after opening and closing a JDialog and the reason we found was the following:
The KeyboardFocusManager has a private static HashMap in which the actual focus in each window is stored. This is done by storing key/value-pairs in the HashMap with window as a key and the Component having the focus on this window as the value. Now you can throw the reference to the component away by using e.g. theComponent.setEnabled(false) - the KeyboardFocusManager then stores the pair window/null in the HashMap - but we didn't find any callable method to remove a key/value-pair from the HashMap and so the reference to the JDialog (as the key!!) stays resident and we have the reason for the memory leak. Now I have a few questions to this problem:
1. Is it right in your opinion, that there is no method to delete the entry from this Hashtable?
2. If this is the case - we have the opinion that there must be a good time to delete this entry (e.g. when disposing the dialog). Do you see if there is an obvious reason that this opinion is false?
3. If no do you think this problem can be accepted as a bug by sun
Thanks in advance and greetings from
Holger

I have been seeing similar behavior; I too have not found all the
leaks. I think I have slowed the allocation by replacing some of my
'build array' functions with the combination of 'initialize array'
followed by 'replace array subset'. The drawback to doing it this way
is that you have a fixed maximum number of elements allocated just once
rather than allowing an array to grow incrementally. Please let me know
if you try removing build arrays and if that helps.
By the way, there is a checkbox under the options menu to deallocate
memory as soon as possible - if you don't mind that your program runs
more slowly, this may help to avoid the problem, at least temporarily.
-vinny
ciossek wrote:
> dear all,
> my labview program needs an increasing amount of memo
ry when running
> (at the time about 12k/s) which leads to swapping memory on my hdd.
> i have found out that calling cluster references like Controls[] or
> decos[] leads to this kind of memory leak and made a work around for
> that (simply calling it only once at runtime) but there are more
> memory leak(s)which i cannot find. The bugs that i have found
> searching the labview resources does not answer my problem.
>
> does anybody already found out more memory leak problems ?
>
> thanks

Effective tool for GDI memory leaks detection

Similar Messages

Maybe you are looking for