http://bugzilla.novell.com/show_bug.cgi?id=547889 Andreas Jaeger changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.pr |garloff@novell.com |ovo.novell.com | Summary|LibVNCServer-0.9.7-1.13: |JJ: |small memory leak |LibVNCServer-0.9.7-1.13: | |small memory leak -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=547889 https://bugzilla.novell.com/show_bug.cgi?id=547889#c2 Agron Selimaj changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |linuxmaster@verizon.net --- Comment #2 from Agron Selimaj 2011-02-15 16:21:22 UTC --- People please disregard Richards comments about being fine to have resource leaks. He is belittling the seriousness of the problem. We should try to make Linux reboot once in 20 years. Not every Tuesday like some other OSes. If I can rephrase Richards comment I would say, if you can't release the allocated resources, the OS will release the for you but only and only if you terminate your process. Also, put comments that you are deliberately doing this. But, because of the nature of the open source development, every code that has been published serves as tutorial, sample and skeleton to the next open source developer, it is of the utmost importance to release all allocated resources. The other major problem is that the way code is moved within a project or copied to another project, what once was an exit path, it may end up being a part of some other execution path and cause catastrophic problems on life support equipment, elevators, SCADA, etc. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.