https://bugs.kde.org/show_bug.cgi?id=388854
--- Comment #22 from Rooty ---
(In reply to Brennan Kinney from comment #21)
> (In reply to Nate Graham from comment #20)
> > Thanks for the additional information, Brennan. However, as previously
> > noted, high memory usage of the sort described by yo
https://bugs.kde.org/show_bug.cgi?id=388854
--- Comment #23 from Rooty ---
(In reply to Brennan Kinney from comment #21)
> (In reply to Nate Graham from comment #20)
> > Thanks for the additional information, Brennan. However, as previously
> > noted, high memory usage of the sort described by yo
https://bugs.kde.org/show_bug.cgi?id=388854
Oliver Sander changed:
What|Removed |Added
CC||oliver.san...@tu-dresden.de
--- Comment #24 fro
https://bugs.kde.org/show_bug.cgi?id=388854
--- Comment #25 from Rooty ---
(In reply to Oliver Sander from comment #24)
> I don't think that this would help. The argument would then be that the
> "use little memory"-option has its price, which is slower loading times.
>
> What is needed is more
https://bugs.kde.org/show_bug.cgi?id=396087
Bug ID: 396087
Summary: Okular stops rendering some pages, locks up at 25% CPU
usage and won't die
Product: okular
Version: unspecified
Platform: Other
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=396087
--- Comment #1 from Filip ---
BTW the performance profile used was Normal.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.kde.org/show_bug.cgi?id=396087
Rooty changed:
What|Removed |Added
CC||zy...@gmx.us
--- Comment #2 from Rooty ---
yeah the sa
https://bugs.kde.org/show_bug.cgi?id=396094
Bug ID: 396094
Summary: Empty Map Plots in PDF
Product: okular
Version: 1.1.2
Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
Severity: normal
Pr
https://bugs.kde.org/show_bug.cgi?id=396094
Yuri Chornoivan changed:
What|Removed |Added
CC||yurc...@ukr.net
--- Comment #1 from Yuri Chor
https://bugs.kde.org/show_bug.cgi?id=388854
--- Comment #26 from Oliver Sander ---
I am not saying that speed/memory consumption of Okular are great and cannot be
improved. However, the path from to the rather vague "Okular uses lots of
memory" to specific improvements to the code is long and win
https://bugs.kde.org/show_bug.cgi?id=396094
Oliver Sander changed:
What|Removed |Added
Ever confirmed|0 |1
CC|
https://bugs.kde.org/show_bug.cgi?id=388854
--- Comment #27 from Rooty ---
(In reply to Oliver Sander from comment #26)
> I am not saying that speed/memory consumption of Okular are great and cannot
> be improved. However, the path from to the rather vague "Okular uses lots of
> memory" to specif
aacid added a comment.
Is this on a High dpi setup? or a regular screen?
REPOSITORY
R223 Okular
REVISION DETAIL
https://phabricator.kde.org/D13766
To: gassaf, #okular
Cc: ngraham, aacid, okular-devel
https://bugs.kde.org/show_bug.cgi?id=388854
--- Comment #28 from Albert Astals Cid ---
I'm not going to answer further in this bug because i don't feel compelled to
have a discussion with people that saying things like "no way a 90kb PDF can
take XX Mb of memory" as if they knew anything about th
https://bugs.kde.org/show_bug.cgi?id=388854
Tobias Deiminger changed:
What|Removed |Added
CC||haxti...@posteo.de
--- Comment #29 from Tobi
https://bugs.kde.org/show_bug.cgi?id=396029
Albert Astals Cid changed:
What|Removed |Added
CC||aa...@kde.org
Status|UNCONFIRME
https://bugs.kde.org/show_bug.cgi?id=388854
--- Comment #30 from Tobias Deiminger ---
(In reply to Albert Astals Cid from comment #28)
> *BUT* this may actually be a manifestation of "glibc is useless and doesn't
> actually free memory when you tell it to" that i workarounded at
> https://cgit.kd
https://bugs.kde.org/show_bug.cgi?id=388854
--- Comment #31 from Rooty ---
(In reply to Albert Astals Cid from comment #28)
> I'm not going to answer further in this bug because i don't feel compelled
> to have a discussion with people that saying things like "no way a 90kb PDF
> can take XX Mb o
https://bugs.kde.org/show_bug.cgi?id=388854
--- Comment #32 from Christoph Feck ---
> Following this theory, I shouldn't be able to find bitmaps in heap.
Your theory is wrong. Read QPixmap source.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.kde.org/show_bug.cgi?id=388854
--- Comment #33 from Tobias Deiminger ---
(In reply to Christoph Feck from comment #32)
> > Following this theory, I shouldn't be able to find bitmaps in heap.
>
> Your theory is wrong. Read QPixmap source.
I did and found
http://code.qt.io/cgit/qt/qt
20 matches
Mail list logo
