posted 08-13-2002 12:29 AM
Not neccessarily. What if you have a server application that leaked memory ? Running it over an extended period would grow the leak footprint and eventually slow down, but not neccessarily crash the application.
Depends totally on the context and type of application you are referring to.
------------------ -Suresh Nageswaran punekar@yahoo.com Cognizant Technology Solutions, Pune, India.
quote:Originally posted by aelana: Since we don't do this kind of test often, it won't be wise for the company to buy expensive softwares. I would have to agree though that having one is the best way to test. So I'm soliciting any idea on how to test for memory leaks without purchasing any software... freeware should be great!
That depends on how the product is to be used. If it is running 24hrs/day....very critical. A typical senario is running it for 8 hrs without crashing (8hr shift ?).
If the application is only used every so often then it is less critical, but any bugs crashes makes your product look bad.
------------------ Robert Tehve rtehve@bigpond.com
posted 11-28-2002 02:28 AM
Issues caused by memory leaks are essentially based on two variable for a standalone windows application : 1. Frequency of usage 2. size of memory leak
If either one or both ar every high it could cause the computer to come to a point when no memory is available for other applications causing it to crash.
If it is a network based application then you will also have to consider network traffic . If each network transaction causes a memory leak , then a high volume of network transactions could also prove dangerous.
hope this helps !
------------------ To put it in the box first think out of the box
posted 08-12-2002 12:42 PM
