Mick wrote: > On Monday 26 Nov 2012 09:56:27 Florian Philipp wrote: >> Hi list! >> >> I have a suspicion that viewing certain PDFs in okular causes X server >> to leak memory. Currently it is using 1.8 GB after 3 days uptime. Has >> anyone else observed that? Is there a way to inspect X server's memory >> usage? > I have noticed that okular recently started breaking into a sweat when it > renders pdf files. Even a four page document with a bit of colour and > graphics seems to push the cpu: > > PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND > 16387 michael 23 3 466m 52m 30m S 102 1.3 0:36.88 /usr/bin/okular > <<< SNIP >>> > > Once rendered, the CPU goes down to normal levels. The problem does not seem > to occur when the pdf is just text, i.e. no photographs, or complex graphics > in it. > > Other than the various top apps, perhaps you can try lsof?
I have a local grocery store that I have to go to the website to get their sale ads. Anyway, it is generally 2 pages and even on this 4 core rig with more than plenty of ram, it takes a bit to open them. Funny thing is, I have some that is about sewing, lots of pictures in those since I need pics to get the idea, anyway, they load up in a flash. As soon as Okular loads, the pages are there. Since this is more like what Florian describes, I guess we see the same things. I'm not sure about ram itself but some files do open differently. By the way, the grocery ad is a much smaller file than the sewing files. Both in file size and number of pages. One would expect it to be the opposite. Looks like I have a problem that I didn't know I had. With 16Gbs of ram, I hadn't noticed anything with the ram, other than Seamonkey being its usual hoggy self. :/ I guess this is to sort of confirm that someone else sees a similar thing to Florian. Dale :-) :-) -- I am only responsible for what I said ... Not for what you understood or how you interpreted my words!
