Re: memory leak
Hi, So you think is the application, In this case the perl/tk library it's true that perl/tk ( due to is structure ) is comsuming always more memory but if I restart application the memory was normally released (xfree 3.3.6) now if I restart application memory is still busy. there is some tools to analize the xfree memory usage ? to know who is requesting resource and which resorce ? thanks Pierfrancesco Tateo On Tuesday 06 January 2004 04:26 pm, tateopfr wrote: Hi, Xfree86 4.3.0 i use more and more memory ... until 200MB and more my system : Slackware 9.1 - kernel 2.4.22 - 512MB RAM DUAL ATHLON 2200+ - THUNDER 2468 TYAN 2 HD SCSI VIDEO CARD : ATI RAGE XL WITH 8 MB RAM ( ONBOARD ) TOUCH SCREEN ELOTOUCH SERIAL Application developed in perl and perl/tk running 24/24 hour. with : top command I can see the X memory ( RSS ) became always great I download and install the last binary version from : xfree.org/~alanh/drivers/x86 but the problem still exists !! thanks Pierfrancesco Tateo ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
memory leak
Hi, Xfree86 4.3.0 i use more and more memory ... until 200MB and more my system : Slackware 9.1 - kernel 2.4.22 - 512MB RAM DUAL ATHLON 2200+ - THUNDER 2468 TYAN 2 HD SCSI VIDEO CARD : ATI RAGE XL WITH 8 MB RAM ( ONBOARD ) TOUCH SCREEN ELOTOUCH SERIAL Application developed in perl and perl/tk running 24/24 hour. with : top command I can see the X memory ( RSS ) became always great I download and install the last binary version from : xfree.org/~alanh/drivers/x86 but the problem still exists !! thanks Pierfrancesco Tateo ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: memory leak
Am Di, den 06.01.2004 schrieb tateopfr um 16:26: Hi, Xfree86 4.3.0 i use more and more memory ... until 200MB and more my system : Slackware 9.1 - kernel 2.4.22 - 512MB RAM DUAL ATHLON 2200+ - THUNDER 2468 TYAN 2 HD SCSI VIDEO CARD : ATI RAGE XL WITH 8 MB RAM ( ONBOARD ) TOUCH SCREEN ELOTOUCH SERIAL Application developed in perl and perl/tk running 24/24 hour. with : top command I can see the X memory ( RSS ) became always great I download and install the last binary version from : xfree.org/~alanh/drivers/x86 but the problem still exists !! This is not necessarily a problem of the X server in terms of a classic memory leak. Applications can register data structures within the X server, for their own and other use. It is the responsibility of the applications to free those structures again after use. If they don't the memory usage of the server increases and the server can be falsely guessed to be guilty. Please check your applications and see which one is causing the memory usage to increase! Common problems are allocated but not freed pixmaps... thanks Pierfrancesco Tateo CU nils faerber -- kernel concepts Tel: +49-271-771091-12 Dreisbachstr. 24 Fax: +49-271-771091-19 D-57250 Netphen D1 : +49-170-2729106 -- ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: memory leak
On Tue, 6 Jan 2004, Nils Faerber wrote: Am Di, den 06.01.2004 schrieb tateopfr um 16:26: Hi, Xfree86 4.3.0 i use more and more memory ... until 200MB and more my system : Slackware 9.1 - kernel 2.4.22 - 512MB RAM DUAL ATHLON 2200+ - THUNDER 2468 TYAN 2 HD SCSI VIDEO CARD : ATI RAGE XL WITH 8 MB RAM ( ONBOARD ) TOUCH SCREEN ELOTOUCH SERIAL Application developed in perl and perl/tk running 24/24 hour. with : top command I can see the X memory ( RSS ) became always great I download and install the last binary version from : xfree.org/~alanh/drivers/x86 but the problem still exists !! This is not necessarily a problem of the X server in terms of a classic memory leak. Applications can register data structures within the X server, for their own and other use. It is the responsibility of the applications to free those structures again after use. If they don't the memory usage of the server increases and the server can be falsely guessed to be guilty. Please check your applications and see which one is causing the memory usage to increase! Common problems are allocated but not freed pixmaps... I'll also add that while many people have accused XFree86 of leaking memory in the past, I can't think of any cases where substantial memory leaks have been uncovered. When I see these sort of requests I usually feel pretty comfortable dismissing them as application resource leaks. Mark. ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: memory leak
[Mark Vojkovich] When I see these sort of requests I usually feel pretty comfortable dismissing them as application resource leaks. Is it possible for dead applications to use resources in the X server? I mean, if a web browser allocate several resources in the X server (shared memory, pixmaps, fonts, I do not know what types of resources are available for allication), and they die, is all these resources released in the server? The reason I ask, is that I suspect that buggy applications can use up a lot of resources in the X server, making the X process so big that I have to restart the X server after a while to get back my systems performance. At least it seem to be that way to me. If this is the case, would some kind of garbage collection be posible? I mean, locate orphaned resources, and release them. ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: memory leak
On Tue, 6 Jan 2004, Petter Reinholdtsen wrote: [Mark Vojkovich] When I see these sort of requests I usually feel pretty comfortable dismissing them as application resource leaks. Is it possible for dead applications to use resources in the X server? I mean, if a web browser allocate several resources in the X server (shared memory, pixmaps, fonts, I do not know what types of resources are available for allication), and they die, is all these resources released in the server? Server-side resources are released when the connection between the server and client is severed. Only apps that stick around an leak cause problems. You can check the resource usage with: http://www.xfree86.org/~mvojkovi/restest.c Be careful running it though. It grabs the server and dumps data to stdout, which means there's a deadlock situation if you run it from within X without redirecting the output. So either run it remotely or redirect to a file restest resout. Mark. ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: memory leak
There is a new utility called xrestop available in the freedesktop.org CVS that is very useful in identifying clients that hog server memory. This utility is patterned somewhat after the top utility; written by Mathew Allum, using Mark's fine Xres extension. - Jim On Tue, 2004-01-06 at 19:50, Mark Vojkovich wrote: On Tue, 6 Jan 2004, Petter Reinholdtsen wrote: [Mark Vojkovich] When I see these sort of requests I usually feel pretty comfortable dismissing them as application resource leaks. Is it possible for dead applications to use resources in the X server? I mean, if a web browser allocate several resources in the X server (shared memory, pixmaps, fonts, I do not know what types of resources are available for allication), and they die, is all these resources released in the server? Server-side resources are released when the connection between the server and client is severed. Only apps that stick around an leak cause problems. You can check the resource usage with: http://www.xfree86.org/~mvojkovi/restest.c Be careful running it though. It grabs the server and dumps data to stdout, which means there's a deadlock situation if you run it from within X without redirecting the output. So either run it remotely or redirect to a file restest resout. Mark. ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel -- Jim Gettys [EMAIL PROTECTED] HP Labs, Cambridge Research Laboratory ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
