Re: OT: Possible memory leak in an exercise of a C handbook

2024-12-18 Thread Jeffrey Walton
On Wed, Dec 18, 2024 at 10:51 AM Franco Martelli wrote: > > On 17/12/24 at 22:09, Jeffrey Walton wrote: > > [...] > > There may be one logic error in the code -- if you insert one item, > > then you may double free the node because you free 'p' and then you > > free 'last'. > > > > I would rewrite

Re: OT: Possible memory leak in an exercise of a C handbook

2024-12-18 Thread Franco Martelli
On 17/12/24 at 22:09, Jeffrey Walton wrote: On Tue, Dec 17, 2024 at 2:39 PM Franco Martelli wrote: On 16/12/24 at 20:49, Jeffrey Walton wrote: Here's the problem: void dealloc() { for ( const DIGIT *p = first; p->next != NULL; p = p->next ) if ( p->prev != NULL )

Re: OT: Possible memory leak in an exercise of a C handbook

2024-12-18 Thread tomas
On Wed, Dec 18, 2024 at 10:45:43AM +, Kevin Chadwick wrote: > 18 Dec 2024 05:03:12 to...@tuxteam.de: > > > I'm all for concise code, but I usually revert some things in a second > > pass when they seem to hurt clarity. After all, you write your code for > > other people to read it. > > As you

Re: OT: Possible memory leak in an exercise of a C handbook

2024-12-18 Thread Kevin Chadwick
18 Dec 2024 05:03:12 to...@tuxteam.de: > I'm all for concise code, but I usually revert some things in a second > pass when they seem to hurt clarity. After all, you write your code for > other people to read it. As you wrote the code then uness that second pass is weeks or months later then cla

Re: OT: Possible memory leak in an exercise of a C handbook

2024-12-18 Thread Anssi Saari
Franco Martelli writes: > Peter A. Darnell, Philip E. Margolis - "C A Software Engineering Approach": > > https://www.google.it/books/edition/_/1nsS5q9aZOUC?hl=it&gbpv=0 > > Do you have it too? It's pretty old, with some typo, but it looks to > me good. Sorry, no, doesn't look familiar. I rememb

Re: OT: Possible memory leak in an exercise of a C handbook

2024-12-17 Thread tomas
On Tue, Dec 17, 2024 at 04:18:17PM -0500, Greg Wooledge wrote: > On Tue, Dec 17, 2024 at 16:09:09 -0500, Jeffrey Walton wrote: > > I would rewrite the cleanup code like so: > > > > void dealloc() > > { > > DIGIT *next, *p = head; > > while( p ) > > next = p->nex

Re: OT: Possible memory leak in an exercise of a C handbook

2024-12-17 Thread Jean-François Bachelet
Hello :) Le 17/12/2024 à 12:20, Anssi Saari a écrit : Franco Martelli writes: I'd prefer a mailing-list instead, once finished all the exercises, I'd like to looking for somebody that he has my same handbook and to ask him for exchange the exercises for comparison purpose. Just curious, whi

Re: OT: Possible memory leak in an exercise of a C handbook

2024-12-17 Thread Greg Wooledge
On Tue, Dec 17, 2024 at 16:09:09 -0500, Jeffrey Walton wrote: > I would rewrite the cleanup code like so: > > void dealloc() > { > DIGIT *next, *p = head; > while( p ) > next = p->next, free( p ), p = next; > } The logic looks good, but I'm not a fan of thi

Re: OT: Possible memory leak in an exercise of a C handbook

2024-12-17 Thread Jeffrey Walton
On Tue, Dec 17, 2024 at 2:39 PM Franco Martelli wrote: > > On 16/12/24 at 20:49, Jeffrey Walton wrote: > > Here's the problem: > > > > void dealloc() > > { > > for ( const DIGIT *p = first; p->next != NULL; p = p->next ) > > if ( p->prev != NULL ) > > free( p->prev ); >

Re: OT: Possible memory leak in an exercise of a C handbook

2024-12-17 Thread Franco Martelli
On 16/12/24 at 20:49, Jeffrey Walton wrote: Here's the problem: void dealloc() { for ( const DIGIT *p = first; p->next != NULL; p = p->next ) if ( p->prev != NULL ) free( p->prev ); free( last ); } You seem to be checking backwards (p->prev) but walking the list

Re: OT: Possible memory leak in an exercise of a C handbook

2024-12-17 Thread Franco Martelli
On 17/12/24 at 12:20, Anssi Saari wrote: Franco Martelli writes: I'd prefer a mailing-list instead, once finished all the exercises, I'd like to looking for somebody that he has my same handbook and to ask him for exchange the exercises for comparison purpose. Just curious, which handbook is

Re: OT: Possible memory leak in an exercise of a C handbook

2024-12-17 Thread Anssi Saari
Franco Martelli writes: > I'd prefer a mailing-list instead, once finished all the exercises, > I'd like to looking for somebody that he has my same handbook and to > ask him for exchange the exercises for comparison purpose. Just curious, which handbook is it?

Re: OT: Possible memory leak in an exercise of a C handbook

2024-12-16 Thread songbird
Franco Martelli wrote: ... > I'd prefer a mailing-list instead, once finished all the exercises, I'd > like to looking for somebody that he has my same handbook and to ask him > for exchange the exercises for comparison purpose. > Does anybody know a mailing-list for C language questions? comp

Re: OT: Possible memory leak in an exercise of a C handbook

2024-12-16 Thread Franco Martelli
On 16/12/24 at 20:49, Jeffrey Walton wrote: On Mon, Dec 16, 2024 at 2:22 PM Franco Martelli wrote: I'm doing the exercises of a C language handbook. I'm using Valgrind to check for memory leak since I use the malloc calls. In the past I was used to using "valkyrie" but s

Re: OT: Possible memory leak in an exercise of a C handbook

2024-12-16 Thread Franco Martelli
On 16/12/24 at 20:42, Michael Kjörling wrote: On 16 Dec 2024 17:21 +0100, from martelli...@gmail.com (Franco Martelli): Put in something to count the number of calls to malloc() and free() respectively. Don't forget calls outside of loops. There isn't calls to malloc() or free() outside loops.

Re: OT: Possible memory leak in an exercise of a C handbook

2024-12-16 Thread Franco Martelli
On 16/12/24 at 17:50, Greg Wooledge wrote: On Mon, Dec 16, 2024 at 17:34:36 +0100, Franco Martelli wrote: void dealloc() { for ( const DIGIT *p = head; p->next != NULL; p = p->next ) if ( p->prev != NULL ) free( p->prev ); free( last ); }

Re: OT: Possible memory leak in an exercise of a C handbook

2024-12-16 Thread Jeffrey Walton
On Mon, Dec 16, 2024 at 2:22 PM Franco Martelli wrote: > > I'm doing the exercises of a C language handbook. I'm using Valgrind to > check for memory leak since I use the malloc calls. In the past I was > used to using "valkyrie" but sadly isn't available anym

Re: OT: Possible memory leak in an exercise of a C handbook

2024-12-16 Thread Michael Kjörling
On 16 Dec 2024 17:21 +0100, from martelli...@gmail.com (Franco Martelli): >> Put in something to count the number of calls to malloc() and free() >> respectively. Don't forget calls outside of loops. > > There isn't calls to malloc() or free() outside loops. What do you mean? >From a quick re-gla

Re: OT: Possible memory leak in an exercise of a C handbook

2024-12-16 Thread Charles Curley
On Mon, 16 Dec 2024 16:05:26 +0100 Franco Martelli wrote: > I'm doing the exercises of a C language handbook. By all means do the exercises in your handbook as a learning experience. After that, I have found very useful Roger Sessions, Reusable Data Structures For C, Prentice Hall (1989). -- D

Re: OT: Possible memory leak in an exercise of a C handbook

2024-12-16 Thread Greg Wooledge
On Mon, Dec 16, 2024 at 17:34:36 +0100, Franco Martelli wrote: > > > void dealloc() > > > { > > > for ( const DIGIT *p = head; p->next != NULL; p = p->next ) > > > if ( p->prev != NULL ) > > > free( p->prev ); > > > free( last ); > > > } > > > > I think you might ha

Re: OT: Possible memory leak in an exercise of a C handbook

2024-12-16 Thread Franco Martelli
On 16/12/24 at 16:58, Greg Wooledge wrote: On Mon, Dec 16, 2024 at 16:05:26 +0100, Franco Martelli wrote: void add_element( unsigned int i ) { DIGIT *p; /* If the first element (the head) has not been * created, create it now. */ if ( head == NULL )

Re: OT: Possible memory leak in an exercise of a C handbook

2024-12-16 Thread Franco Martelli
On 16/12/24 at 16:43, Michael Kjörling wrote: On 16 Dec 2024 16:05 +0100, from martelli...@gmail.com (Franco Martelli): Is there a memory leak? What it sounds strange to me is that Valgrind reports: "total heap usage: 9 allocs, 8 frees, …" when for me the calls to "malloc"

Re: OT: Possible memory leak in an exercise of a C handbook

2024-12-16 Thread Greg Wooledge
On Mon, Dec 16, 2024 at 16:05:26 +0100, Franco Martelli wrote: > void add_element( unsigned int i ) > { > DIGIT *p; > /* If the first element (the head) has not been > * created, create it now. > */ > if ( head == NULL ) > { > head = last = (DIGIT *

Re: OT: Possible memory leak in an exercise of a C handbook

2024-12-16 Thread Michael Kjörling
On 16 Dec 2024 16:05 +0100, from martelli...@gmail.com (Franco Martelli): > Is there a memory leak? What it sounds strange to me is that Valgrind > reports: "total heap usage: 9 allocs, 8 frees, …" when for me the calls to > "malloc" should be 8, not 9. Put in som

OT: Possible memory leak in an exercise of a C handbook

2024-12-16 Thread Franco Martelli
Hi, I'm doing the exercises of a C language handbook. I'm using Valgrind to check for memory leak since I use the malloc calls. In the past I was used to using "valkyrie" but sadly isn't available anymore for Bookworm (does anybody know for a replacement?). I suppos

Kernel memory leak on bullseye-backports kernel

2023-01-28 Thread bgme
Hi all, After using the bullseye-backports kernel, my vps ran out of memory after a period of time. ![Memory Basic1](https://img.bgme.bid/media_attachments/files/109/765/807/240/058/094/original/4797799a06a1f6a0.png) ![Memory Detail1](https://img.bgme.bid/media_attachments/files/109/765/733/

Re: Memory leak

2022-02-14 Thread Celejar
On Sat, 12 Feb 2022 12:49:15 -0500 Stefan Monnier wrote: > > As I mentioned (briefly) in my original post, yes, I experience concrete > > problems: the system either grinds to a halt or becomes unresponsive, > > or hits swap and becomes intolerably slow. > > Sorry I missed that part. > I think t

Re: Memory leak

2022-02-13 Thread piorunz
On 12/02/2022 12:43, Curt wrote: On 2022-02-12, piorunz wrote: On 11/02/2022 22:16, Roy J. Tellason, Sr. wrote: Somewhere in their help or documentation they even say that you shouldn't leave it running for extended periods of time. Never heard such a thing. Do you have source? See my o

Re: Memory leak

2022-02-13 Thread rhkramer
On Sunday, February 13, 2022 02:58:46 PM Roy J. Tellason, Sr. wrote: > On Saturday 12 February 2022 09:21:00 am rhkra...@gmail.com wrote: > > The version of Firefox used in Jessie (and presumably later versions) > > creates (typically mutlitple) files named "Web Content". I don't know > > how Fire

Re: Memory leak

2022-02-13 Thread Roy J. Tellason, Sr.
On Saturday 12 February 2022 09:21:00 am rhkra...@gmail.com wrote: > The version of Firefox used in Jessie (and presumably later versions) creates > (typically mutlitple) files named "Web Content".  I don't know how Firefox > decides what to put in each of those (e.g., content from how many tabs)

Re: Memory leak

2022-02-13 Thread David Wright
On Fri 11 Feb 2022 at 20:04:35 (+0100), Linux-Fan wrote: > Stefan Monnier writes: > > > > I used to have 8 GB on the system, and it would start to thrash at > > > about 7+ GB usage. I recently ugrade to 16 GB; memory usage is > > > currently over 8 GB, and it seems to be slowly but steadily increa

Re: Memory leak

2022-02-13 Thread Andrew M.A. Cater
On Sun, Feb 13, 2022 at 10:05:27AM -0500, rhkra...@gmail.com wrote: > On Sunday, February 13, 2022 01:29:09 AM to...@tuxteam.de wrote: > > On Sat, Feb 12, 2022 at 09:21:00AM -0500, rhkra...@gmail.com wrote: > > > > I'm sure they are not one from each tab -- I often have 100 tabs open (in > Jessi

Re: Memory leak

2022-02-13 Thread Andrei POPESCU
gt; > > won´t preserved. > > > > You don't want to have them preserved. > > You may for the case in question, i.e. where you're only restarting > Firefox work around a memory leak, not because you're finished doing > the 'private browsing&#x

Re: Memory leak

2022-02-13 Thread tomas
On Sun, Feb 13, 2022 at 10:05:27AM -0500, rhkra...@gmail.com wrote: [Firefox Web Content processes] > > Those are, basically, one for each tab, yes. > > I'm sure they are not one from each tab -- I often have 100 tabs open (in > Jessie's Firfox, upto 3000 in Wheezy's Firefox), and typically se

Re: Memory leak

2022-02-13 Thread rhkramer
On Sunday, February 13, 2022 01:29:09 AM to...@tuxteam.de wrote: > On Sat, Feb 12, 2022 at 09:21:00AM -0500, rhkra...@gmail.com wrote: > > [...] > > > The version of Firefox used in Jessie (and presumably later versions) > > creates (typically mutlitple) files > > ...you mean "processes", not fi

Re: Memory leak

2022-02-13 Thread Tixy
for the case in question, i.e. where you're only restarting Firefox work around a memory leak, not because you're finished doing the 'private browsing' thing. Personally, I'm more paranoid about browser security and tab isolation. I have the 'always use private b

Re: Memory leak

2022-02-12 Thread tomas
On Sat, Feb 12, 2022 at 11:45:05PM +0100, Felmon Davis wrote: > On Sat, 12 Feb 2022, Curt wrote: > > > https://support.mozilla.org/en-US/kb/firefox-uses-too-much-memory-or-cpu-resources > > > > Firefox may use more system resources if it's left open for long periods > > of time [...] > what this

Re: Memory leak

2022-02-12 Thread tomas
On Sat, Feb 12, 2022 at 09:21:00AM -0500, rhkra...@gmail.com wrote: [...] > The version of Firefox used in Jessie (and presumably later versions) creates > (typically mutlitple) files ...you mean "processes", not files, right? > named "Web Content". I don't know ho

Re: Memory leak

2022-02-12 Thread Felmon Davis
On Sat, 12 Feb 2022, Curt wrote: https://support.mozilla.org/en-US/kb/firefox-uses-too-much-memory-or-cpu-resources Firefox may use more system resources if it's left open for long periods of time. A workaround for this is to periodically restart Firefox. You can configure Firefox to save your

Re: Memory leak

2022-02-12 Thread Felmon Davis
On Sat, 12 Feb 2022, rhkra...@gmail.com wrote: Maybe things would work better with more swap, but I haven/t (and probably won't try that) -- in the reasonably near future (maybe after tax season), I plan to set up a new system with Debian 1 (whatever that is "code named"). increasing swap here

Re: Memory leak

2022-02-12 Thread rhkramer
On Saturday, February 12, 2022 05:11:31 AM Curt wrote: > Firefox may use more system resources if it's left open for long periods > of time. A workaround for this is to periodically restart Firefox. You > can configure Firefox to save your tabs and windows so that when you > start it again, you

Re: Memory leak

2022-02-12 Thread Curt
On 2022-02-12, piorunz wrote: > On 11/02/2022 22:16, Roy J. Tellason, Sr. wrote: >> Somewhere in their help or documentation they even say that you shouldn't >> leave it running for extended periods of time. > > Never heard such a thing. Do you have source? > See my other post in this thread.

Re: Memory leak

2022-02-12 Thread Curt
On 2022-02-11, Roy J. Tellason, Sr. wrote: > On Friday 11 February 2022 11:06:01 am Celejar wrote: >> I seem to have a serious memory leak on my system (Lenovo W550s) - the >> memory usage seems to slowly but more or less steadily keep increasing. >> >> This is a m

Re: Memory leak

2022-02-12 Thread tomas
On Fri, Feb 11, 2022 at 06:22:48PM +, piorunz wrote: > On 11/02/2022 17:58, Charlie Gibbs wrote: > > > It seems to be the fashion nowadays to leave one's web browser up 24/7, > > with dozens of tabs open.  Personally I can't understand this - I seldom > > have more than two or three tabs open

Re: Memory leak

2022-02-12 Thread piorunz
On 11/02/2022 22:16, Roy J. Tellason, Sr. wrote: Somewhere in their help or documentation they even say that you shouldn't leave it running for extended periods of time. Never heard such a thing. Do you have source? -- With kindest regards, Piotr. ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal opera

Re: Memory leak

2022-02-11 Thread Roy J. Tellason, Sr.
On Friday 11 February 2022 11:06:01 am Celejar wrote: > I seem to have a serious memory leak on my system (Lenovo W550s) - the > memory usage seems to slowly but more or less steadily keep increasing. > > This is a more or less normal (I think) desktop installation of Sid, >

Re: Memory leak

2022-02-11 Thread Charles Curley
On Fri, 11 Feb 2022 15:00:39 -0500 Celejar wrote: > There are several reasons I'm not ready to do that: Fine, get another browser. -- Does anybody read signatures any more? https://charlescurley.com https://charlescurley.com/blog/

Re: Memory leak

2022-02-11 Thread Celejar
On Fri, 11 Feb 2022 15:57:58 -0500 Bijan Soleymani wrote: > On 2022-02-11 14:52, Celejar wrote: > > As I mentioned in another post, I do this occasionally, but I'm not > > sure how to interpret the results. I just killed firefox; I got back > > about 3.5 GB, but the system is still using about 4.

Re: Memory leak

2022-02-11 Thread Bijan Soleymani
On 2022-02-11 14:52, Celejar wrote: As I mentioned in another post, I do this occasionally, but I'm not sure how to interpret the results. I just killed firefox; I got back about 3.5 GB, but the system is still using about 4.8, and Xorg's usage hasn't changed: ~ 4436M / 3081M / 105M. Closing Fi

Re: Memory leak

2022-02-11 Thread piorunz
On 11/02/2022 18:40, Charles Curley wrote: My solution is simple: I switched to Vivaldi over a year ago, and haven't looked back. https://vivaldi.com. They have packages for Debian, and run a roughly two week release cycle. It's based on Chromium, but with better privacy settings for the default

Re: Memory leak

2022-02-11 Thread Celejar
On Fri, 11 Feb 2022 11:40:15 -0700 Charles Curley wrote: > On Fri, 11 Feb 2022 12:01:59 -0500 > Celejar wrote: > > > So I've heard. So is this something I just have to live with? Does > > everyone have this problem? > > It is widely rumored, backed by experiments I've done here. I've not > see

Re: Memory leak

2022-02-11 Thread Celejar
On Fri, 11 Feb 2022 09:58:40 -0800 Charlie Gibbs wrote: > On Fri Feb 11 09:43:03 2022 Celejar wrote: > > > On Fri, 11 Feb 2022 09:53:17 -0700 > > Charles Curley wrote: > > > >> On Fri, 11 Feb 2022 11:06:01 -0500 > >> Celejar wrote: > >>

Re: Memory leak

2022-02-11 Thread Celejar
On Fri, 11 Feb 2022 18:06:52 + piorunz wrote: > On 11/02/2022 17:01, Celejar wrote: > > So I've heard. So is this something I just have to live with? Does > > everyone have this problem? I actually did used to kill firefox when I > > was experiencing memory pressure - it certainly relieved th

Re: Memory leak

2022-02-11 Thread Celejar
On Fri, 11 Feb 2022 13:43:55 -0500 Stefan Monnier wrote: > > I used to have 8 GB on the system, and it would start to thrash at > > about 7+ GB usage. I recently ugrade to 16 GB; memory usage is > > currently over 8 GB, and it seems to be slowly but steadily increasing. > > Presumably you bought

Re: Memory leak

2022-02-11 Thread Linux-Fan
Stefan Monnier writes: > I used to have 8 GB on the system, and it would start to thrash at > about 7+ GB usage. I recently ugrade to 16 GB; memory usage is > currently over 8 GB, and it seems to be slowly but steadily increasing. Presumably you bought 16GB to make use of it, right? So it's onl

Re: Memory leak

2022-02-11 Thread Charles Curley
On Fri, 11 Feb 2022 12:01:59 -0500 Celejar wrote: > So I've heard. So is this something I just have to live with? Does > everyone have this problem? It is widely rumored, backed by experiments I've done here. I've not seen anything official from the Mozilla folks, but then I don't pay close atte

Re: Memory leak

2022-02-11 Thread piorunz
On 11/02/2022 17:58, Charlie Gibbs wrote: It seems to be the fashion nowadays to leave one's web browser up 24/7, with dozens of tabs open.  Personally I can't understand this - I seldom have more than two or three tabs open at once, and most of the time I have only one open, which is why I trea

Re: Memory leak

2022-02-11 Thread Charlie Gibbs
On Fri Feb 11 09:43:03 2022 Celejar wrote: > On Fri, 11 Feb 2022 09:53:17 -0700 > Charles Curley wrote: > >> On Fri, 11 Feb 2022 11:06:01 -0500 >> Celejar wrote: >> >>> I seem to have a serious memory leak on my system (Lenovo W550s) - >>> the

Re: Memory leak

2022-02-11 Thread piorunz
On 11/02/2022 17:01, Celejar wrote: So I've heard. So is this something I just have to live with? Does everyone have this problem? I actually did used to kill firefox when I was experiencing memory pressure - it certainly relieved the immediate problem, but I think I found that not all the memory

Re: Memory leak

2022-02-11 Thread Celejar
On Fri, 11 Feb 2022 09:53:17 -0700 Charles Curley wrote: > On Fri, 11 Feb 2022 11:06:01 -0500 > Celejar wrote: > > > I seem to have a serious memory leak on my system (Lenovo W550s) - the > > memory usage seems to slowly but more or less steadily keep > > increasing.

Re: Memory leak

2022-02-11 Thread Charles Curley
On Fri, 11 Feb 2022 11:06:01 -0500 Celejar wrote: > I seem to have a serious memory leak on my system (Lenovo W550s) - the > memory usage seems to slowly but more or less steadily keep > increasing. > > This is a more or less normal (I think) desktop installation of Sid,

Memory leak

2022-02-11 Thread Celejar
Hello, I seem to have a serious memory leak on my system (Lenovo W550s) - the memory usage seems to slowly but more or less steadily keep increasing. This is a more or less normal (I think) desktop installation of Sid, running Xfce4. Typical applications used are Firefox (currently with just one

Debian 8.4 sgtreamer plugin memory leak

2016-08-04 Thread arusev
Hello all. Debian 8.4 sgtreamer 1.4.4 plugin "rtmpvdepay" (gstreamer plugins-good packege) is leaking memory because. The particular fix is available in gstreamer git repository. May be an update for this package is needed for Debuian releases 8.4/8.5 ? Could one expect gstreamer update will

Re: Every time `tracker` has a memory leak....

2013-07-30 Thread Wayne Topa
On 07/29/2013 10:59 PM, Tyler MacDonald wrote: > This has happened at least a dozen times in the past few years. I've > removed tracker a few times, but it's been re-added due to > dependencies/recommends. A product that is this immature should not be > allowed to be part of the default installatio

Re: Every time `tracker` has a memory leak....

2013-07-30 Thread Wayne Topa
On 07/29/2013 10:59 PM, Tyler MacDonald wrote: > This has happened at least a dozen times in the past few years. I've > removed tracker a few times, but it's been re-added due to > dependencies/recommends. A product that is this immature should not be > allowed to be part of the default installatio

Every time `tracker` has a memory leak....

2013-07-29 Thread Tyler MacDonald
This has happened at least a dozen times in the past few years. I've removed tracker a few times, but it's been re-added due to dependencies/recommends. A product that is this immature should not be allowed to be part of the default installation. Again, tonight, I had to SSH in to my PC from anothe

lenny kernel memory leak?

2009-12-14 Thread Mikko Rapeli
fter a few days of uptime. I think the anonpages difference shows a memory leak in kernel, am I correct? -Mikko ps. please cc me in replies, thanks. --- meminfo_after_boot.txt 2009-12-14 14:28:25.0 +0200 +++ meminfo_slow.txt2009-12-14 14:24:01.0 +0200 @@ -1,28 +1,28 @@

Re: XFCE memory leak in Lenny

2007-07-23 Thread Owen Heisler
On Mon, Jul 23, 2007 at 03:59:34PM +0530, Masatran, R. Deepak wrote: > I was told that XFCE has a memory leak. I am currently using Lenny. Has it > been fixed in the Lenny packages? How can I know when it gets fixed? xfdesktop4 still leaks memory badly. Bugs: 376177 376372 373010 You can

XFCE memory leak in Lenny

2007-07-23 Thread Masatran, R. Deepak
I was told that XFCE has a memory leak. I am currently using Lenny. Has it been fixed in the Lenny packages? How can I know when it gets fixed? -- Masatran, R. Deepak <http://research.iiit.ac.in/~masatran/> pgpcCB6tOFXBl.pgp Description: PGP signature

Re: vesa display codes (Etch Xorg memory leak?)

2007-05-22 Thread Andrei Popescu
On Tue, May 22, 2007 at 06:28:50PM -0500, Owen Heisler wrote: > So I add "nvidiafb" to /etc/initramfs-tools/modules, run > "update-initramfs -u" (this is fun) and now "nvidia" is also listed. > > Now I reboot and try "video=nvidiafb:1280x960" and > "video=nvidiafb:1024x768" and get something sli

Re: vesa display codes (Etch Xorg memory leak?)

2007-05-22 Thread Owen Heisler
On Tue, 2007-05-22 at 18:56 +0300, Andrei Popescu wrote: > On Tue, May 22, 2007 at 07:24:40AM -0500, Owen Heisler wrote: > > > There doesn't seem to be a correct vga= parameter for 1280x960. > > I was suggesting 791 as it is still better then the default and you can > see something happening (

Re: vesa display codes (Etch Xorg memory leak?)

2007-05-22 Thread Andrei Popescu
On Tue, May 22, 2007 at 07:24:40AM -0500, Owen Heisler wrote: > There doesn't seem to be a correct vga= parameter for 1280x960. I was suggesting 791 as it is still better then the default and you can see something happening (I just hate it when I mess with options and I see no change :)) > I'

Re: vesa display codes (Etch Xorg memory leak?)

2007-05-22 Thread Owen Heisler
On Tue, 2007-05-22 at 09:33 +0300, Andrei Popescu wrote: > On Mon, May 21, 2007 at 07:44:14PM -0500, Owen Heisler wrote: > > Anyway, I tried some other video= lines and nothing makes any > > difference. I tried vesafb, rivafb, and nvidiafb for the driver and > > both 1024x768 (vga=791 works fine)

Re: vesa display codes (Etch Xorg memory leak?)

2007-05-21 Thread Andrei Popescu
On Mon, May 21, 2007 at 07:44:14PM -0500, Owen Heisler wrote: > Anyway, I tried some other video= lines and nothing makes any > difference. I tried vesafb, rivafb, and nvidiafb for the driver and > both 1024x768 (vga=791 works fine) and 1280x960 for the resolution (all > combinations for rivafb

Re: vesa display codes (Etch Xorg memory leak?)

2007-05-21 Thread Owen Heisler
On Mon, 2007-05-21 at 19:27 -0400, cga2000 wrote: > _Owen_, > > What do you get .. a kernel oops .. a black screen of death .. a vga > console with oversized fonts ..? With any video= parameter, I get the default resolution (640x480/80x25, I suppose), just like there was no vga= or video= para

Re: vesa display codes (Etch Xorg memory leak?)

2007-05-21 Thread cga2000
On Mon, May 21, 2007 at 12:35:57PM EDT, Andrei Popescu wrote: > On Mon, May 21, 2007 at 08:18:37AM -0400, cga2000 wrote: > > On Mon, May 21, 2007 at 02:44:29AM EDT, Andrei Popescu wrote: > > > On Sun, May 20, 2007 at 11:06:39PM -0400, cga2000 wrote: > > > > > > > > I tried: > > > > > video=rivafb

Re: vesa display codes (Etch Xorg memory leak?)

2007-05-21 Thread Andrei Popescu
On Mon, May 21, 2007 at 08:18:37AM -0400, cga2000 wrote: > On Mon, May 21, 2007 at 02:44:29AM EDT, Andrei Popescu wrote: > > On Sun, May 20, 2007 at 11:06:39PM -0400, cga2000 wrote: > > > > > > I tried: > > > > video=rivafb:1280x960 > > > > video=vesafb:1280x960 > > > > > > > > but neither worke

Re: vesa display codes (Etch Xorg memory leak?)

2007-05-21 Thread cga2000
On Mon, May 21, 2007 at 02:44:29AM EDT, Andrei Popescu wrote: > On Sun, May 20, 2007 at 11:06:39PM -0400, cga2000 wrote: > > > > I tried: > > > video=rivafb:1280x960 > > > video=vesafb:1280x960 > > > > > > but neither worked. > > > > You do realize that you may need to compile a custom kernel t

Re: vesa display codes (Etch Xorg memory leak?)

2007-05-20 Thread Andrei Popescu
On Sun, May 20, 2007 at 11:06:39PM -0400, cga2000 wrote: > > I tried: > > video=rivafb:1280x960 > > video=vesafb:1280x960 > > > > but neither worked. > > You do realize that you may need to compile a custom kernel to enable > support for a given video card..? Not necessarily. It should work i

Re: vesa display codes (Etch Xorg memory leak?)

2007-05-20 Thread cga2000
On Sun, May 20, 2007 at 07:25:41PM EDT, Owen Heisler wrote: [..] > A list of the available video drivers here (?): > http://linux-fbdev.sourceforge.net/driverlist.php > > I tried: > video=rivafb:1280x960 > video=vesafb:1280x960 > > but neither worked. You do realize that you may need to compil

Re: vesa display codes (Etch Xorg memory leak?)

2007-05-20 Thread Owen Heisler
On Sun, 2007-05-20 at 01:10 -0400, cga2000 wrote: > On Sat, May 19, 2007 at 07:33:51PM EDT, Owen Heisler wrote: > > On Sat, 2007-05-19 at 19:10 -0400, Greg Folkert wrote: > > > On Fri, 2007-05-18 at 00:10 -0400, Greg Folkert wrote: > > > > On Thu, 2007-05-17 at 18:34 -0500, Owen Heisler wrote: > >

Re: vesa display codes (Etch Xorg memory leak?)

2007-05-20 Thread Greg Folkert
On Sun, 2007-05-20 at 17:25 -0400, cga2000 wrote: > On Sun, May 20, 2007 at 12:01:18PM EDT, Greg Folkert wrote: > > Mind if I add snippets of you two posts to Owen to that Vesa Mode Page? > > Not in principle naturally. [snip] > Oh, if you do decide to add something to your web page, please let m

Re: vesa display codes (Etch Xorg memory leak?)

2007-05-20 Thread cga2000
On Sun, May 20, 2007 at 12:01:18PM EDT, Greg Folkert wrote: [..} > Mind if I add snippets of you two posts to Owen to that Vesa Mode Page? Not in principle naturally. Just that I'd be a little concerned about the contents of my posts possibly misleading others .. A clear case of I don't under

Re: vesa display codes (Etch Xorg memory leak?)

2007-05-20 Thread Greg Folkert
On Sun, 2007-05-20 at 01:10 -0400, cga2000 wrote: > On Sat, May 19, 2007 at 07:33:51PM EDT, Owen Heisler wrote: > > On Sat, 2007-05-19 at 19:10 -0400, Greg Folkert wrote: > > > On Fri, 2007-05-18 at 00:10 -0400, Greg Folkert wrote: > > > > On Thu, 2007-05-17 at 18:34 -0500, Owen Heisler wrote: > >

Re: vesa display codes (Etch Xorg memory leak?)

2007-05-19 Thread cga2000
On Sat, May 19, 2007 at 07:33:51PM EDT, Owen Heisler wrote: > On Sat, 2007-05-19 at 19:10 -0400, Greg Folkert wrote: > > On Fri, 2007-05-18 at 00:10 -0400, Greg Folkert wrote: > > > On Thu, 2007-05-17 at 18:34 -0500, Owen Heisler wrote: > > > > On Thu, 2007-05-17 at 16:02 -0400, Greg Folkert wrote:

Re: vesa display codes (Etch Xorg memory leak?)

2007-05-19 Thread cga2000
On Sat, May 19, 2007 at 07:33:51PM EDT, Owen Heisler wrote: > On Sat, 2007-05-19 at 19:10 -0400, Greg Folkert wrote: > > On Fri, 2007-05-18 at 00:10 -0400, Greg Folkert wrote: > > > On Thu, 2007-05-17 at 18:34 -0500, Owen Heisler wrote: > > > > On Thu, 2007-05-17 at 16:02 -0400, Greg Folkert wrote:

Re: vesa display codes (Etch Xorg memory leak?)

2007-05-19 Thread Greg Folkert
On Sat, 2007-05-19 at 18:33 -0500, Owen Heisler wrote: > video=<>:xres:<>,yres:<>,depth:<>,left:<>,right:<>,hslen:<>,upper:<>,lower:<>,vslen:<> > > It looks like I need something like this: > Modeline "1280x1024" DCF HR SH1 SH2 HFL VR SV1 SV2 VFL > > Is there some way to get that from xorg? > >

Re: vesa display codes (Etch Xorg memory leak?)

2007-05-19 Thread Owen Heisler
On Sat, 2007-05-19 at 19:10 -0400, Greg Folkert wrote: > On Fri, 2007-05-18 at 00:10 -0400, Greg Folkert wrote: > > On Thu, 2007-05-17 at 18:34 -0500, Owen Heisler wrote: > > > On Thu, 2007-05-17 at 16:02 -0400, Greg Folkert wrote: > > > > http://www.gregfolkert.net/info/vesa-display-codes.html > >

Re: vesa display codes (Etch Xorg memory leak?)

2007-05-19 Thread Greg Folkert
On Sat, 2007-05-19 at 17:09 -0500, Owen Heisler wrote: > On Fri, 2007-05-18 at 00:10 -0400, Greg Folkert wrote: > > On Thu, 2007-05-17 at 18:34 -0500, Owen Heisler wrote: > > > On Thu, 2007-05-17 at 16:02 -0400, Greg Folkert wrote: > > > > http://www.gregfolkert.net/info/vesa-display-codes.html > >

Re: vesa display codes (Etch Xorg memory leak?)

2007-05-19 Thread Owen Heisler
On Fri, 2007-05-18 at 00:10 -0400, Greg Folkert wrote: > On Thu, 2007-05-17 at 18:34 -0500, Owen Heisler wrote: > > On Thu, 2007-05-17 at 16:02 -0400, Greg Folkert wrote: > > > http://www.gregfolkert.net/info/vesa-display-codes.html > > > > Very helpful! Although no 1280x960 (grr) unfortunately.

Re: Etch Xorg memory leak?

2007-05-18 Thread Roberto C . Sánchez
On Fri, May 18, 2007 at 09:24:37PM -0400, Douglas Allan Tutty wrote: > On Fri, May 18, 2007 at 09:18:01PM -0400, Douglas Allan Tutty wrote: > > Package: xserver-xorg-core > > Sorry for the noise. I thought I'd turn my question into a bug report > but sent it here instead of bugs by accident. > D

Re: Etch Xorg memory leak?

2007-05-18 Thread Douglas Allan Tutty
On Fri, May 18, 2007 at 09:18:01PM -0400, Douglas Allan Tutty wrote: > Package: xserver-xorg-core Sorry for the noise. I thought I'd turn my question into a bug report but sent it here instead of bugs by accident. Doug. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubsc

Re: Etch Xorg memory leak?

2007-05-18 Thread Douglas Allan Tutty
Package: xserver-xorg-core Running up-to-date Etch. Over time, xorg takes up more and more memory. I have two computers: rocky: PII-233 with 64 MB ram running i386 titan: Athlon64 with 1 GB ram running amd64 On my i386, I only have 64 MB of ram so I can only run X for about 45 m

Re: Etch Xorg memory leak?

2007-05-18 Thread Douglas Allan Tutty
On Sun, May 13, 2007 at 07:51:18AM -0400, Douglas Allan Tutty wrote: > > Over time, xorg takes up more and more memory. On my i386, I only have > 64 MB of ram so I can only run X for about 45 minutes before the system > thrashes. Eventually, Xorg dies but doesn't release the screen. If I > let

Re: vesa display codes (Etch Xorg memory leak?)

2007-05-17 Thread Greg Folkert
On Thu, 2007-05-17 at 18:34 -0500, Owen Heisler wrote: > On Thu, 2007-05-17 at 16:02 -0400, Greg Folkert wrote: > > http://www.gregfolkert.net/info/vesa-display-codes.html > > Very helpful! Although no 1280x960 (grr) unfortunately. Is there any > way to get that? vbetool is supposed to do it.

Re: vesa display codes (Etch Xorg memory leak?)

2007-05-17 Thread Owen Heisler
On Thu, 2007-05-17 at 16:02 -0400, Greg Folkert wrote: > http://www.gregfolkert.net/info/vesa-display-codes.html Very helpful! Although no 1280x960 (grr) unfortunately. Is there any way to get that? signature.asc Description: This is a digitally signed message part

Re: Etch Xorg memory leak?

2007-05-17 Thread Greg Folkert
On Thu, 2007-05-17 at 12:58 -0400, Douglas Allan Tutty wrote: > On Thu, May 17, 2007 at 05:31:09PM +0100, Tom Furie wrote: > > On Thu, May 17, 2007 at 12:17:34PM -0400, Douglas Allan Tutty wrote: > > > On Sun, May 13, 2007 at 10:22:00AM -0500, Mumia W.. wrote: > > > > On 05/13/2007 06:51 AM, Dougla

Re: Etch Xorg memory leak?

2007-05-17 Thread Douglas Allan Tutty
On Thu, May 17, 2007 at 05:31:09PM +0100, Tom Furie wrote: > On Thu, May 17, 2007 at 12:17:34PM -0400, Douglas Allan Tutty wrote: > > On Sun, May 13, 2007 at 10:22:00AM -0500, Mumia W.. wrote: > > > On 05/13/2007 06:51 AM, Douglas Allan Tutty wrote: > > > > > > Try out the VESA driver and see if t

Re: Etch Xorg memory leak?

2007-05-17 Thread Tom Furie
On Thu, May 17, 2007 at 12:17:34PM -0400, Douglas Allan Tutty wrote: > On Sun, May 13, 2007 at 10:22:00AM -0500, Mumia W.. wrote: > > On 05/13/2007 06:51 AM, Douglas Allan Tutty wrote: > > > > Try out the VESA driver and see if the problem recurs. > Would if I could. On the i386, dpkg-reconfigur

Re: Etch Xorg memory leak?

2007-05-17 Thread Douglas Allan Tutty
On Sun, May 13, 2007 at 10:22:00AM -0500, Mumia W.. wrote: > On 05/13/2007 06:51 AM, Douglas Allan Tutty wrote: > >I'm having trouble with Xorg under Etch i386 and similar annoyance under > >amd64. > > > >Over time, xorg takes up more and more memory. [...] > > I also installed Etch on a computer

  1   2   >