Re: contest proposal

"exit without calling free() so that paged out memory doesn't get paged in before exit"
Memory in use will not be paged out and if it is freed immediately after use, there is no paging 
problem.

There are also ways to reuse memory efficiently. The varies approaches are language dependent. They 
were not taught in any of the programming classes I attended outside of those I ran. Perhaps there 
could be training for people who help with open source code but may not have the experience to pick 
up that type of problem.

On one Linux, I found the Bluetooth icon on the tool bar used 15 MB. Switching off Bluetooth using 
the icon did not free up memory. I deleted the whole of Bluetooth as it was not needed. There must 
be a way to have the on/off option use less than a megabyte and only load all the settings windows 
etc if the option is on.

On 5/1/24 21:50, Russell Coker wrote:
> On Friday, 5 January 2024 15:35:41 AEDT Info via linux-aus wrote:
>> I use valgrind for C. I do not know if there is an equivalent for other
>> languages.
> 
> Valgrind is good for finding bugs in memory usage, but isn't designed to find
> inefficiencies.  Allocate one byte less than needed and Valgrind can tell you,
> allocate 1M more than needed and it won't.  It will tell you about memory that
> was still allocated when the program exited, this can be memory that was
> leaked but also could be a case of "exit without calling free() so that paged
> out memory doesn't get paged in before exit".
> 

_______________________________________________
linux-aus mailing list
[email protected]
http://lists.linux.org.au/mailman/listinfo/linux-aus

To unsubscribe from this list, send a blank email to
linux-aus-unsubscribe-cunTk1MwBs8iFSDQTTA3OBCuuivNXqWP@public.gmane.org