Memory leakage / memory problems

Luis luis at anachreon.co.uk
Thu Sep 14 07:51:42 EDT 2006


In the Control Panel (if in XP switch to 'Classic View) and go into 
Administrative Tools. Once there double-click on Event Viewer: This will 
tell you what's happening with the system and applications - Select 
'Application' on the left hand side and the right hand side panel will 
show you the events the system logs in relation to the applications 
running. From there you can trace back the event by date or time.
If it doesn't appear there then select the 'System' option on the left 
hand side to view events that are reported by the system directly.

If it's only affecting one user make sure that this user is running the 
same version, by that I mean that the patch level is the same and all 
the same updates have been applied.

It could also be that there is a problem with the memory chip itself 
(happens!) or a faulty HD (this may show up as a bad block report in the 
Event Viewer.

Another option is to use the 'System Monitor' (it's called 'Performance' 
in the Administrative Tools section): In there you can add monitoring 
events to see what is going on with the system.

Hope that helps!

Cheers,

Luis.


Richard Miller wrote:
> Well, I'm not that knowledgeable about Windows either... Looking at the 
> Task Manager and the Performance area, which numbers are the critical 
> ones to monitor? Is it the "available" memory, and if so, when does that 
> number get so low that it becomes a problem? Do I watch CPU usage?... or 
> is the "commit charge" info a critical variable?
> 
> Thanks.
> Richard
> 
> 
> On Sep 14, 2006, at 6:23 AM, Ian Wood wrote:
> 
>> It might not be *your* program that's having problems. :-(
>>
>> I'm not that knowledgeable when it comes to Windows, but leaving the 
>> Task Manager open so that you can see what resources different apps 
>> are using would probably be a good start. Then leave it all running 
>> and wait until there are problems. Don't you just love intermittent bugs?
>>
>> Ian
>>
>> P.S. A notorious example of memory leaks on OS X is Safari - if you 
>> leave your computer up for long periods of time Safari can easily hit 
>> more than a GB of RAM after being open for a few days, even after you 
>> close most of the tabs and windows...
>>
>> On 14 Sep 2006, at 10:39, Richard Miller wrote:
>>
>>> Ian,
>>>
>>> This sounds like a possible culprit for the problem in our 
>>> application. Is there a way to find out what is causing this or to 
>>> verify it is occurring? Any code that can be written in? Any specific 
>>> places in the code to look for it?
>>>
>>> Again, what we are experiencing is the program bogging down or simply 
>>> freezing up at various points throughout a day, but never at the same 
>>> place. This is in runtime mode only.... not in the development 
>>> environment. No programming bugs show up there.
>>>
>>> Thanks.
>>> Richard
>>>
>>>
>>>
>>> On Sep 14, 2006, at 5:27 AM, Ian Wood wrote:
>>>
>>>> Memory leaks are where a program grabs memory when needed, but 
>>>> doesn't release all of it afterwards. If the machine is up for a 
>>>> long time, even a minor memory leak can tie up all available RAM, 
>>>> bogging down the whole machine.
>>>>
>>>> Ian
>>>>
>>>> On 14 Sep 2006, at 10:23, Richard Miller wrote:
>>>>
>>>>> Peter,
>>>>>
>>>>> Can you explain what you mean by a memory leak and how that effects 
>>>>> stability?
>>>>>
>>>>> Thanks.
>>>>> Richard
>>>>
>>>> _______________________________________________
>>>> use-revolution mailing list
>>>> use-revolution at lists.runrev.com
>>>> Please visit this url to subscribe, unsubscribe and manage your 
>>>> subscription preferences:
>>>> http://lists.runrev.com/mailman/listinfo/use-revolution
>>>
>>> _______________________________________________
>>> use-revolution mailing list
>>> use-revolution at lists.runrev.com
>>> Please visit this url to subscribe, unsubscribe and manage your 
>>> subscription preferences:
>>> http://lists.runrev.com/mailman/listinfo/use-revolution
>>
>> _______________________________________________
>> use-revolution mailing list
>> use-revolution at lists.runrev.com
>> Please visit this url to subscribe, unsubscribe and manage your 
>> subscription preferences:
>> http://lists.runrev.com/mailman/listinfo/use-revolution
> 
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your 
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-revolution
> 
> 



More information about the Use-livecode mailing list