Patrick Plattes <[EMAIL PROTECTED]> wrote: > > we have some trouble with the 2.6v kernel tree and CDRecord 2.01 (Debian > Sarge package). If we try to write an 150MB CD the memory fills up to > 150MB. The memory will not deallocate after closing cdrecord. Next if we > try to write an 200MB CD the memory will filled up to additional 50MB. > > We don't know which part of the software is steals our memory. This only > happens on 2.6, not on an 2.4 system and we can reproduce the bug only > on the asus notebook. > > We have tried to find the leak with top and slabtop, but inconclusively. I > put some information together. The informations are taken from the system > after burning a 154MB CD. Please have a look at: > http://cdrecord.sourcecode.cc . > I uploaded the files to this address, to avoid high traffic on the lkml.
That all looks perfectly normal. MemTotal: 516360 kB MemFree: 198648 kB Buffers: 8240 kB Cached: 263656 kB SwapCached: 0 kB Active: 209932 kB Inactive: 95960 kB HighTotal: 0 kB HighFree: 0 kB LowTotal: 516360 kB LowFree: 198648 kB SwapTotal: 995988 kB SwapFree: 995988 kB Dirty: 4 kB Writeback: 0 kB Mapped: 58472 kB Slab: 8540 kB Committed_AS: 97660 kB PageTables: 548 kB VmallocTotal: 516052 kB VmallocUsed: 18324 kB VmallocChunk: 497676 kB 200M free, 260M in pagecache, all of it (plus anonymous memory) on the LRU. That pagecache should be reclaimable on demand. What behaviour makes you believe that there is a leak? - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
