https://bugs.kde.org/show_bug.cgi?id=177213
Jekyll Wu changed:
What|Removed |Added
CC||adap...@gmail.com
--
You are receiving this mail b
https://bugs.kde.org/show_bug.cgi?id=177213
qxldd...@aon.at changed:
What|Removed |Added
CC||qxldd...@aon.at
--- Comment #51 from20
https://bugs.kde.org/show_bug.cgi?id=177213
Kevin Funk changed:
What|Removed |Added
CC||k...@electrostorm.net
--
Configure bugmail: h
https://bugs.kde.org/show_bug.cgi?id=177213
--- Comment #50 from Dominik Haumann 2011-07-05 21:39:28 ---
Using ctrl+esc > Detailed memory Information: Pixmap was max 50 MB. Private
goes up > 1 GB, (only) when scrolling too fast.
I'm able to reproduce it everytime. When running it in massif,
https://bugs.kde.org/show_bug.cgi?id=177213
--- Comment #49 from2011-07-05 18:24:54 ---
Regarding comment 47, it is easy to find pixmap use with Ctrl-Esc Detailed
memory information, or xrestop.
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
--- You are receiving
https://bugs.kde.org/show_bug.cgi?id=177213
aux...@yahoo.com changed:
What|Removed |Added
CC||aux...@yahoo.com
--- Comment #48 from
https://bugs.kde.org/show_bug.cgi?id=177213
--- Comment #47 from Benoît Jacob 2011-07-05
18:00:58 ---
May I suggest something that's working nicely for Firefox: we have a special
about:memory page reporting on memory usage; it used to be of little use, but
if you try current Nightly, it's b
https://bugs.kde.org/show_bug.cgi?id=177213
--- Comment #46 from Albert Astals Cid 2011-07-05 17:50:12
---
@Dominik: Should not be, so you are either seeing a bug in gs, in the
libspectre code or in the okular-spectre code
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
https://bugs.kde.org/show_bug.cgi?id=177213
Dominik Haumann changed:
What|Removed |Added
CC||dh...@gmx.de
--- Comment #45 from Dominik
https://bugs.kde.org/show_bug.cgi?id=177213
Zane Tu changed:
What|Removed |Added
CC||zan...@gmail.com
--
Configure bugmail: https://b
https://bugs.kde.org/show_bug.cgi?id=177213
--- Comment #44 from Waldo Cancino 2011-03-20 16:52:53 ---
For me, it is happens with proprietary drivers (nvidia and fglrx). For
instance,
in my notebook with Intel 945GM the memory usage is normal. The same
for xorg-ati drivers. Unfortunately,
https://bugs.kde.org/show_bug.cgi?id=177213
--- Comment #43 from2011-03-20 16:24:00 ---
any news about this bug? okular still obuses the xserver in kde 4.6.1 and fills
up the ram after some time of usage
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
--- You
https://bugs.kde.org/show_bug.cgi?id=177213
rauchwo...@gmx.net changed:
What|Removed |Added
CC||rauchwo...@gmx.net
--
Configure bugmai
https://bugs.kde.org/show_bug.cgi?id=177213
--- Comment #42 from Thomas 2010-11-13 15:46:29 ---
(In reply to comment #40)
> I'm in favor of blaming the drivers for that given comments from #37 and my
> own
> experience (works for me)
>
> Can those that have the problem see if running okula
https://bugs.kde.org/show_bug.cgi?id=177213
Thomas changed:
What|Removed |Added
CC||bargh...@gmx.com
--- Comment #41 from Thomas 201
https://bugs.kde.org/show_bug.cgi?id=177213
--- Comment #40 from Albert Astals Cid 2010-11-11 09:50:13
---
I'm in favor of blaming the drivers for that given comments from #37 and my own
experience (works for me)
Can those that have the problem see if running okular with "--graphicssystem
https://bugs.kde.org/show_bug.cgi?id=177213
Andrew M changed:
What|Removed |Added
CC||quantumpha...@gmail.com
--- Comment #39 from And
https://bugs.kde.org/show_bug.cgi?id=177213
--- Comment #38 from Pasi Rehtonen 2010-09-02 20:18:44 ---
Sorry forgot to mention my specs: Arch 64-bit, Qt 4.6.3, Xorg-server 1.81.902,
KDE 4.5.1, Nvidia binary blob 256.53
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
https://bugs.kde.org/show_bug.cgi?id=177213
Waldo Cancino changed:
What|Removed |Added
CC||wcanc...@gmail.com
--- Comment #37 from Wal
https://bugs.kde.org/show_bug.cgi?id=177213
--- Comment #36 from Pasi Rehtonen 2010-09-02 11:47:48 ---
I have been doing some digging and managed to get Firefox not to store pixmaps
in X11, and removed comic strip plasmoid because it seemed to store those
pixmaps in X11 too. So now when I op
https://bugs.kde.org/show_bug.cgi?id=177213
Pasi Rehtonen changed:
What|Removed |Added
CC||preht...@gmail.com
--- Comment #35 from Pas
https://bugs.kde.org/show_bug.cgi?id=177213
Kai Kasurinen changed:
What|Removed |Added
CC||kai.kasuri...@uninea.fi
--
Configure bugma
https://bugs.kde.org/show_bug.cgi?id=177213
--- Comment #34 from Fest 2010-03-30 18:01:12 ---
"MemoryLevel" option "Low" draining memory too.
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the
https://bugs.kde.org/show_bug.cgi?id=177213
Szymon Stefanek changed:
What|Removed |Added
CC||pra...@kvirc.net
--- Comment #33 from Szy
https://bugs.kde.org/show_bug.cgi?id=177213
--- Comment #32 from Pino Toscano 2010-03-17 20:53:27 ---
(In reply to comment #31)
> (In reply to comment #30)
> > (In reply to comment #29)
> > > As mentioned on the past too, I did some informal benchmarks and
> > > perceived no
> > > speed dif
https://bugs.kde.org/show_bug.cgi?id=177213
--- Comment #31 from Oscar Fuentes 2010-03-17 20:23:04 ---
(In reply to comment #30)
> (In reply to comment #29)
> > As mentioned on the past too, I did some informal benchmarks and perceived
> > no
> > speed difference on page rendering after cha
https://bugs.kde.org/show_bug.cgi?id=177213
--- Comment #30 from Pino Toscano 2010-03-17 19:52:54 ---
(In reply to comment #29)
> As mentioned on the past too, I did some informal benchmarks and perceived no
> speed difference on page rendering after changing Okular's memory usage
> setting,
https://bugs.kde.org/show_bug.cgi?id=177213
--- Comment #29 from Oscar Fuentes 2010-03-17 19:45:25 ---
(In reply to comment #26)
> #25 to me it's fairly obvious, each time you allocate a X pixmap in the server
> side you get a handle in your process, if you don't free the local handle
> the
https://bugs.kde.org/show_bug.cgi?id=177213
--- Comment #28 from Albert Astals Cid 2010-03-17 17:43:55
---
#27 Being sarcastic is not going to make people help you so spare ourselves
that comments everyone will be happier.
It being a bug i agree, but we still have to find whose fault it is
https://bugs.kde.org/show_bug.cgi?id=177213
--- Comment #27 from Fest 2010-03-17 16:53:39 ---
(In reply to comment #26)
> And well, if the bug is about okular allocating X memory we can close it
> altogether because that is not a bug at all.
Yeah. It's not bug, it's feature. Just need to ad
https://bugs.kde.org/show_bug.cgi?id=177213
--- Comment #26 from Albert Astals Cid 2010-03-17 16:33:00
---
#25 to me it's fairly obvious, each time you allocate a X pixmap in the server
side you get a handle in your process, if you don't free the local handle there
is a local leak, if you d
https://bugs.kde.org/show_bug.cgi?id=177213
--- Comment #25 from Oscar Fuentes 2010-03-17 13:13:34 ---
(In reply to comment #21)
> And the evidence that Okular is the one at fault is where? Because i've run
> valgrind over and over and never could find any memory leak.
How is valgrind relev
https://bugs.kde.org/show_bug.cgi?id=177213
--- Comment #24 from Fest 2010-03-17 13:09:34 ---
I didn't tell that "okular memory usage raises while doing nothing with it." I
told that okular used X for caching(?) 700 mb, and after closing okular memory
(700 mb) is not free. And xrestop shows
https://bugs.kde.org/show_bug.cgi?id=177213
--- Comment #23 from Albert Astals Cid 2010-03-17 12:45:36
---
xrestop will be of use if you can prove that okular memory usage raises while
doing nothing with it.
for valgrind it's easy, do
valgrind --leak-check=full okular
and then look at the
https://bugs.kde.org/show_bug.cgi?id=177213
--- Comment #22 from Fest 2010-03-17 12:19:49 ---
(In reply to comment #21)
> And the evidence that Okular is the one at fault is where? Because i've run
> valgrind over and over and never could find any memory leak.
Xrestop is good enough ? Befor
https://bugs.kde.org/show_bug.cgi?id=177213
--- Comment #21 from Albert Astals Cid 2010-03-17 12:05:05
---
And the evidence that Okular is the one at fault is where? Because i've run
valgrind over and over and never could find any memory leak.
--
Configure bugmail: https://bugs.kde.org/us
https://bugs.kde.org/show_bug.cgi?id=177213
Fest changed:
What|Removed |Added
CC||fest...@gmail.com
--- Comment #20 from Fest 2010-0
https://bugs.kde.org/show_bug.cgi?id=177213
Iago López Galeiras changed:
What|Removed |Added
CC||iag...@gmail.com
--
Configure bugmai
https://bugs.kde.org/show_bug.cgi?id=177213
Salvatore changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Ever Confirmed|0
https://bugs.kde.org/show_bug.cgi?id=177213
Pino Toscano changed:
What|Removed |Added
CC||jacob.benoi...@gmail.com
--- Comment #18 fro
https://bugs.kde.org/show_bug.cgi?id=177213
Albert Astals Cid changed:
What|Removed |Added
CC||mies...@zabrze.zigzag.pl
--- Comment #1
https://bugs.kde.org/show_bug.cgi?id=177213
Sergei Danilov changed:
What|Removed |Added
CC||sergeidani...@gmail.com
--- Comment #16 fr
https://bugs.kde.org/show_bug.cgi?id=177213
--- Comment #15 from Mark Whitis 2009-05-25 08:29:17 ---
I can certainly appreciate that X pixmap storage on the server could
significantly improve performance in many cases.Indeed, okular seemed a bit
faster than evince at first, which was lar
https://bugs.kde.org/show_bug.cgi?id=177213
Mark Whitis changed:
What|Removed |Added
CC||whi...@freelabs.com
--- Comment #14 from Mark
https://bugs.kde.org/show_bug.cgi?id=177213
--- Comment #13 from Albert Astals Cid 2009-05-25 01:22:37
---
Okular is not the most memory hungry document viewer out there, at least it's
at the same level of kpdf ;-)
It's fast for local viewing because to paint anything on X, it must be a X
https://bugs.kde.org/show_bug.cgi?id=177213
--- Comment #12 from Pino Toscano 2009-05-25 01:17:22 ---
(In reply to comment #11)
> (In reply to comment #10)
> We can say that okular is the most memory hungry document viewer
> out there (at least on Normal memory setting). The fact that the me
https://bugs.kde.org/show_bug.cgi?id=177213
--- Comment #11 from Oscar Fuentes 2009-05-25 00:49:53 ---
(In reply to comment #10)
> No arguing at all, if we free the pixmaps and that memory is not freed, it's
> not *our* bug, so put the strain on people causing the problem, not on us.
OSes,
https://bugs.kde.org/show_bug.cgi?id=177213
--- Comment #10 from Albert Astals Cid 2009-05-24 22:48:54
---
No arguing at all, if we free the pixmaps and that memory is not freed, it's
not *our* bug, so put the strain on people causing the problem, not on us.
Of course your experience of us
https://bugs.kde.org/show_bug.cgi?id=177213
--- Comment #9 from Oscar Fuentes 2009-05-24 22:11:38 ---
(In reply to comment #8)
> (In reply to comment #7)
> >- The X server memory is NOT consistently freed when okular exits.
>
> This is an Xorg bug.
It is a QoI (qualitiy of implementati
https://bugs.kde.org/show_bug.cgi?id=177213
--- Comment #8 from Pino Toscano 2009-05-24 19:48:05 ---
(In reply to comment #7)
>- The X server memory is NOT consistently freed when okular exits.
This is an Xorg bug.
> This appears to be related to okular sharing its pixmap cache among s
https://bugs.kde.org/show_bug.cgi?id=177213
--- Comment #7 from Mark Whitis 2009-05-24 19:36:06 ---
The situation is much worse than described in this bug report.
- X server resident usage climbs to 500MB and virtual memory usage to about
1.3MB on my system.
- The X server memory is NOT
https://bugs.kde.org/show_bug.cgi?id=177213
Rick W. Chen changed:
What|Removed |Added
CC||stuffcor...@archlinux.us
--
Configure bugma
http://bugs.kde.org/show_bug.cgi?id=177213
Franz Berger fr4nk is a geek gmail com changed:
What|Removed |Added
CC||fr4nk.is.a.g...@gmail.co
http://bugs.kde.org/show_bug.cgi?id=177213
Pino Toscano pino kde org changed:
What|Removed |Added
Severity|crash |normal
--
Configure bugmail: htt
http://bugs.kde.org/show_bug.cgi?id=177213
--- Comment #5 from Oscar Fuentes 2008-12-09 18:17:44 ---
Asking on the X.org mailing list [1] yield this information:
The X server does nothing fancy when resources such as pixmaps are deallocated.
Is up to the C library function free() to return
http://bugs.kde.org/show_bug.cgi?id=177213
Pino Toscano pino kde org changed:
What|Removed |Added
Component|DjVu backend|general
--
Configure bugmail: ht
http://bugs.kde.org/show_bug.cgi?id=177213
--- Comment #4 from Albert Astals Cid 2008-12-08 21:50:25
---
We cache the pixmaps but we should never reach level of eating all the memory.
Which platform are you using?
--
Configure bugmail: http://bugs.kde.org/userprefs.cgi?tab=email
---
http://bugs.kde.org/show_bug.cgi?id=177213
--- Comment #3 from Pino Toscano 2008-12-08 21:42:16 ---
> The memory consumption was evident: starting at 23MB when Okular is executed,
> it reaches 200 MB after scrolling 70 pages.
Okular keeps a cache of the browser pages, so it is quite obvious
http://bugs.kde.org/show_bug.cgi?id=177213
--- Comment #2 from Oscar Fuentes 2008-12-08 21:18:50 ---
The problem, as it seems, is not restricted to the djvu backend. A large pdf
shows it too:
Open a large pdf document, such as
http://open-std.org/JTC1/SC22/WG21/docs/papers/2008/n2588.pdf
http://bugs.kde.org/show_bug.cgi?id=177213
--- Comment #1 from Albert Astals Cid 2008-12-08 19:52:05
---
Can you attach or send me "a large document" where you were able to reproduce
this problem?
--
Configure bugmail: http://bugs.kde.org/userprefs.cgi?tab=email
--- You are receivin
60 matches
Mail list logo
