Search 5,000,000+ questions and answers.

Frequently Asked Questions

What about memory leaks ?

LessTif Frequently Asked Questions
Obviously we don't like memory leaks in LessTif. A couple of tests have been done with commercial memory analysis tools, some of the apps in the tests/ tree help tracking some leaks as well. We believe we're not doing really bad. In fact we did run some simple comparisons with official Motif 1.2.
Related Questions

Spells - Frequently Asked Questions (FAQ) - The Hive Worksho...
Read this Tutorial to find out. Keep in mind that memory leaks occur even when you use GUI, not only in JASS. If you have a comment or suggestion for the FAQ, then please PM Daelin. If you have a question about the FAQ or spells in general, then please create a separate thread for it.
Related Questions

LessTif Frequently Asked Questions
Obviously we don't like memory leaks in LessTif. A couple of tests have been done with commercial memory analysis tools, some of the apps in the tests/ tree help tracking some leaks as well. We believe we're not doing really bad. In fact we did run some simple comparisons with official Motif 1.2.
Related Questions

Why does Bounds CheckerTM say that I have memory leaks?

SGI STL: Frequently Asked Questions
In the default STL allocator, memory allocated for blocks of small objects is not returned to malloc. It can only be reused by subsequent allocate requests of (approximately) the same size. Thus programs that use the default may appear to leak memory when monitored by certain kinds of simple leak detectors. This is intentional. Such "leaks" do not accumulate over time. Such "leaks" are not reported by garbage-collector-like leak detectors.
Related Questions

Why are there memory leaks in ThoughtTreasure?

ThoughtTreasure FAQ
attempt was made at first to free storage that is no longer being used. As the program became more complex, data structures were shared by more and more modules, making it difficult to determine exactly how and when to free storage. Programming time was saved by ignoring the problem and allowing some memory leaks for the time being. Some of the places in the code where storage might need to be freed are marked with the keyword todoFREE.
Related Questions

Are there any memory leaks in XINS?

XINS - Frequently Asked Questions
No. There were memory leaks in older versions of XINS, especially in XINS 1.0.0, but extensive memory profiling and testing on XINS 1.3.0 and later has shown there are no memory leaks left.
Related Questions

I find memory leaks in XML4C. How do I eliminate it?

Parsing with XML4C
The "leaks" that are reported through a leak-detector or heap-analysis tools aren't really leaks in most application, in that the memory usage does not grow over time as the XML parser is used and re-used. What you are seeing as leaks are actually lazily evaluated data allocated into static variables. This data gets released when the application ends. You can make a call to XMLPlatformUtil::terminate() to release all the lazily allocated variables before you exit your program.
Related Questions

How to test Memory Leaks?What tool is ussed for testing Memoy Leaks?

Testing Definitions - Page 8
Latest Answer: Please correct me if iam wrong.when ever we perform PERFORMANCE Testing we load the machine to the m...
Related Questions

APT14) How to avoid memory leaks?

Soar Frequently Asked Questions List
There are some known memory issues with Soar. The dominating one has a "fix" in Soar 8.4, but the fix is not completely stable. In general, Soar seems to purposely keep around a fair amount of information, just in case it will be needed later. Most of this information gets flushed away when a state is destroyed, but at the top state, information may just accumulate. Soar agents, that perform lots of reasoning on the top state, are likely to suffer the most from this memory issue.
Related Questions

How can I fix memory leaks?

NetBeans Master Developer FAQ
The first problem is to identify what is the root problem causing that memory cannot be used effectively. The usual approach for this is to analyze the complete contents of memory when the problem appears, using one of a number of appropriate tools, and ideally then find a solution. If the problem causes OutOfMemoryError, it is possible to customize JVM to provide a memory dump automatically whenever an OutOfMemoryError is thrown. user FAQ about OOME describes what options can be used for this.
Related Questions

How do I debug memory leaks?

ORBit2 Frequently Asked Questions - FAQs
OK - if you compile ORBit2 with --enable-debug (perhaps you did this already), then export ORBIT2_DEBUG=refs, then re-run - it should show you the type of object that is leaked - which may help. Probably you are missing a CORBA_Object_release (foo, NULL); somewhere. You might want to use memory debugger of some sort; I would recommend valgrind - google for it; you need to build ORBit2 with --enable-purify and run with --alignment=8 but it's an extremely powerful & useful tool.
Related Questions

I am seeing memory leaks in XML4C. Are they real?

Parsing with XML4C
The XML4C library allocates and caches some commonly reused items. The storage for these may be reported as memory leaks by some heap analysis tools; to avoid the problem, call the function XMLPlatformUtils::Terminate() before your application exits. This will free all memory that was being held by the library. For most applications, the use of Terminate() is optional. The system will recover all memory when the application process shuts down.
Related Questions

I find memory leaks in Xerces-C++. How do I eliminate it?

Programming/Parsing FAQs
The "leaks" that are reported through a leak-detector or heap-analysis tools aren't really leaks in most application, in that the memory usage does not grow over time as the XML parser is used and re-used. What you are seeing as leaks are actually lazily evaluated data allocated into static variables. This data gets released when the application ends. You can make a call to XMLPlatformUtil::terminate() to release all the lazily allocated variables before you exit your program.
Related Questions

Do I need to use the CRT for Memory Validator to detect memory leaks?

Software Verification FAQ Page
No. Memory Validator inspects all Win32 heaps (HeapCreate etc), the GlobalAlloc() heap, LocalAlloc() heap, CoTaskMemAlloc() heap, IMallocSpy, as well as the C runtime heap(CRT). If you are using any of these heaps Memory Validator is capable of monitoring the memory allocations and deallocations.
Related Questions

What About Leaks?

Weight Loss Surgery Center Frequently Asked Questions (FAQ):...
Question 1: Just had my RNY done 5 days ago. I don't seem to be able to eat pain free. Whenever I eat a little something (juice, jell-o, soup) it feels like it gets stuck in my throat which in turn makes me cough until I almost throw up.
Related Questions

Why does my memory debugging tool show memory leaks in glib?

Frequently Asked Questions
glib does not call malloc() every time it needs a new node in a data structure. If it did, building linked lists (for example) would be substantially slower. Instead, glib caches pools of equal-sized "memory chunks" for use in these data structures. Since the chunks are still available for recycling when your program exits, they are never free()d. (Of course, the operating system will reclaim the memory, but tools such as ccmalloc and Purify will report it as a memory leak.
Related Questions

Can I detect component memory leaks with AppMetrics?

AppMetrics - Most Frequently Asked Questions
Create a COM+ Server Application for each of the components currently residing in the COM+ Application exhibiting the leak. Next, move each component to a one of these separate COM+ Applications. In other words, each component lives in its own COM+ Server Application. Create a Production monitor in AppMetrics and configure it to monitor all of these new COM+ Applications. Important: Set the Production monitor to "Component" level detail, NOT "Component and Method" detail.
Related Questions

I am seeing memory leaks in Xerces-C++. Are they real?

Programming/Parsing FAQs
The Xerces-C++ library allocates and caches some commonly reused items. The storage for these may be reported as memory leaks by some heap analysis tools; to avoid the problem, call the function XMLPlatformUtils::Terminate() before your application exits. This will free all memory that was being held by the library. For most applications, the use of Terminate() is optional. The system will recover all memory when the application process shuts down.
Related Questions

Q6.2 My tool detect memory leaks in application with STLport. Is this leak from STLport?

STLport: Developers
In the default compile of STLport, the node allocator is used to allocate internal memory. The node allocator works by pre-allocating a large chunk of memory and handing out small memory blocks out. The memory chunk is not freed during running an application that uses STLport (i.e. it don't returned to system, There are tools like BoundsChecker, Purify or Valgrind that check for memorytml leaks, for memory that isn't freed when no longer used.
Related Questions

How much memory should I give it?

MT-NW Manual: Frequently Asked Questions
Important Note: Your humble authors got tired of writing dry formal technical prose in the rest of this document, and succumbed to the temptation to try to be funny in parts of this appendix. Sarcasm abounds here. Please do not take any of this personally! The humor-impaired should interpret my comments not as attacks on them, but as an attempt to make fun of myself for being impatient with you, my devoted and valued, if sometimes demanding, users.
Related Questions

How Much Memory Do I Have?

All of Memory FAQ
Consult your user/owner's manual for details about the original memory configuration and capacity. If you've misplaced the manual, you may be able to contact the retailer where you bought the PC from. If you have a hand-me-down PC or inherited a pre-owned PC, you probably may not have the user manual or know any detail of the original memory configuration or the memory configuration may have been changed.
Related Questions

Lokring, manufacturers of the patented no weld fitting conne...
Answer: Lokring’s patented design assures a significant reduction in leakage when compared to welded joints (virtually nil). However, if necessary, a Lokring fitting can be cut out and replaced. With our patented design, slip-fitting another fitting of longer length or installing a “T” is no problem. In addition, Lokring fittings can be back welded. Consult Lokring for specific back welding procedures.
Related Questions

Q.: If AQtime does not report memory leaks, are there any situations when this could be misleading?

AQtime 5 - Frequently Asked Questions, FAQ
The leak type is not supported by AQtime. Though AQtime searches for leaks of many types (memory blocks, resources, objects, etc.), there can be leaks that cannot be detected by AQtime. For example, if you are using a custom memory manager in C++ applications. A.: The Editor panel is updated when you select a routine in one of AQtime's panels. To view the source code for a leak, choose that leak in the Report panel and then switch to the Details panel, which will display the call stack data.
Related Questions

When I enable PMEMORY_CHECK, I see all sorts of memory leaks reported. How do I fix these?

Vox Gratia FAQ
There is a define called PMEMORY_CHECK that enabled all sorts of code in PWLib to check memory blocks allocated by the code. But this is turned off by default (even in debug mode) because the code it uses is pretty stupid. Not only does it slow down the entire stack by a significant amount, but it reports all sorts things as memory leaks when they really aren't.
Related Questions

Which FOX objects do I need to delete to avoid memory leaks?

Frequently Asked Questions
Most FOX Widgets are automatically deleted by their parent Widget. However there are some resources which are sharable, and these resources must be deleted explicitly by the program in order to avoid memory leaks or other problems. Cursors, Fonts, Images, Icons, Bitmaps, and Visuals are sharable resources which must be cleaned up explicitly.
Related Questions

Snazzipants - FAQ
Yes! You will no doubt get leaks while you adjust your system to suit you. The good thing about using cloth is that you can adjust your system to fix it. With disposables you'll get leaks too, but apart from trying different (more expensive) brands you'll probably have to put up with it!
Related Questions

TerraTherm | FAQ
The treatment zone is completely covered by a vapor barrier at the ground surface. Also, the last process unit in the vapor treatment facility is a vacuum blower that draws vapors through the rest of the system. Thus, the boundaries of the treatment system are maintained at sub-atmospheric pressures, and any leakage would be from the outside inward. Contaminated vapors thus cannot escape to the atmosphere before passing through the vapor treatment system.
Related Questions

My diaper leaks - what can I do?

Diaper Safari - Cloth Diaper Information : Diaper FAQs : Dia...
The first thing that you want to do when you have leaking diapers is to make sure the diaper fits around the legs snugly - refer to previous question. If you are using covers, make sure none of the cloth diaper is sticking out of the cover. If you still experience problems with wicking/leaking, start using a diaper insert - it could be that your baby needs more cloth to absorb the urine. This is very often a cause for nighttime leaks! Do not worry about the diaper becoming too bulky..
Related Questions

Got A Question? Ask Our Community!


More Questions >>

© Copyright 2007-2008 QueryCAT
About • Webmasters • Contact