Here comes glxinfo | grep renderer OpenGL renderer string: Mesa DRI Intel(R) 945GME GEM 20090114 x86/MMX/SSE2
Here comes the /proc/$PID/status. What is the significant value that one needs to retain for the discussion? cat /proc/3851/status Name: notify-osd State: S (sleeping) Tgid: 3851 Pid: 3851 PPid: 1 TracerPid: 0 Uid: 1000 1000 1000 1000 Gid: 100 100 100 100 FDSize: 256 Groups: 4 20 21 24 26 29 30 44 46 100 104 106 108 114 123 124 126 VmPeak: 35376 kB VmSize: 35368 kB VmLck: 0 kB VmHWM: 24316 kB VmRSS: 23788 kB VmData: 16000 kB VmStk: 108 kB VmExe: 120 kB VmLib: 15816 kB VmPTE: 52 kB Threads: 1 SigQ: 2/16382 SigPnd: 0000000000000000 ShdPnd: 0000000000000000 SigBlk: 0000000000000000 SigIgn: 0000000020001000 SigCgt: 0000000180000000 CapInh: 0000000000000000 CapPrm: 0000000000000000 CapEff: 0000000000000000 CapBnd: ffffffffffffffff Cpus_allowed: 00000000,00000003 Cpus_allowed_list: 0-1 Mems_allowed: 1 Mems_allowed_list: 0 voluntary_ctxt_switches: 14643 nonvoluntary_ctxt_switches: 329 --------- Cody: for the memory foot print, my point is that the notify-osd should not range in the top consumers. As stated before, after recent update, the top reported a reduction from 29MB to 17MB, but it's still in the top list. On Thu, Mar 5, 2009 at 16:03, Cody Russell <[email protected]> wrote: > You can't really use top output as a remotely reliable source of memory > information. Even to get the numbers I posted above, I was pulling > those out of /proc/$PID/status and I don't think that's really a > completely accurate source of memory information. To get realistic > numbers you probably need to use something like valgrind. > > If you don't know what type of video card/driver you're using, you might be > able to give Mirco an estimate with the GLX renderer string. Try running: > glxinfo | grep renderer > > For example, on my Intel X3100 it says: > OpenGL renderer string: Mesa DRI Intel(R) 965GM GEM 20090114 x86/MMX/SSE2 > > Maybe there's a way to get a more accurate description of your video > hardware, I don't know. > > -- > notify-osd heavy memory usage > https://bugs.launchpad.net/bugs/334141 > You received this bug notification because you are a direct subscriber > of the bug. > -- notify-osd heavy memory usage https://bugs.launchpad.net/bugs/334141 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
