Bug 208865 - Reading large PDF files freezes a thin client
Summary: Reading large PDF files freezes a thin client
Status: RESOLVED WORKSFORME
Alias: None
Product: okular
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Debian testing Unspecified
: NOR normal
Target Milestone: ---
Assignee: Okular developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-09-29 13:11 UTC by Roland Wolters
Modified: 2014-05-21 08:35 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Roland Wolters 2009-09-29 13:11:44 UTC
Version:            (using KDE 4.2.4)
Installed from:    Debian testing/unstable Packages

We have a Terminal-Server/Thin-Client setup. Running Okular on a Thin Client and opening a large PDF freezes the machine shortly after we scrolled down. The machine must be restarted!

We tested Evince as well, the problem wasn't present there.

Please let me know how we can generate further helpful log or other data.
Comment 1 Albert Astals Cid 2009-09-30 22:28:38 UTC
The tyipical problem is that we use X memory as cache and use some functions to see how much memory we use, the problem is the functions that calculate the free memory obviously execute on the server and not on the thin client so probably we killed the available free memory on the thin client. Try setting the performance -> memory usage to low in the options and see if that helps.
Comment 2 Roland Wolters 2009-10-09 12:25:36 UTC
Thanks for the answer. And indeed, when we deactivate the transparency effects and background generation and set the memory usage to "Low", the clients didn't freeze any more. But the scrolling was still bumpy.

Also, this is only true for single page view. The facing pages view froze the client again.

Any ideas or other information we could provide?
Comment 3 Albert Astals Cid 2009-10-22 20:49:01 UTC
Can you please run kdebugdialog, enable okular debug output (4700 should be enough but enable all others too) run okular and paste here the shell output?
Comment 4 dc 2010-03-31 15:17:04 UTC
Okular make the system freeze. This occurs on medium size documents and seems triggered by fast scrolling (but only seems). I can't get a dump since the system is totaly frozen....

A good example documet can be obtained at :

http://h20000.www2.hp.com/bizsupport/TechSupport/CoreRedirect.jsp?redirectReason=DocIndexPDF&prodSeriesId=3884343&targetPage=http%3A%2F%2Fbizsupport2.austin.hp.com%2Fbc%2Fdocs%2Fsupport%2FSupportManual%2Fc01728029%2Fc01728029.pdf

Daniel Cordey
Comment 5 Albert Astals Cid 2014-05-08 14:42:58 UTC
Hi sorry for the late reply, can you guys still reproduce this issue in newer versions of okular?

Also you need to understand i don't have a thin client setup so it's hard for me to test. Is there any way we could get access to your setup to see it live (which would probably increase the changes of this geting fixed from 0% to something like 5%)?

Thanks for caring about Okular :-)
Comment 6 dc 2014-05-08 14:56:25 UTC
On 08/05/2014 16:42, Albert Astals Cid wrote:
> https://bugs.kde.org/show_bug.cgi?id=208865

> Hi sorry for the late reply, can you guys still reproduce this issue in 
> newer
> versions of okular?
> 
> Also you need to understand i don't have a thin client setup so it's 
> hard for
> me to test. Is there any way we could get access to your setup to see 
> it live
> (which would probably increase the changes of this geting fixed from 0% 
> to
> something like 5%)?
> 
> Thanks for caring about Okular :-)

Well, the url/link I mentioned is outdated now. It doesn't point to a 
PDF anymore end we get redirected to an html page...

I haven't experienced problem with okular, except a few years ago (when 
I filled the bug). It seems to work fine now... I can't point to 
something that makes it fails, since it works weel for me now :-)

Thanks for caring.

dc
Comment 7 Roland Wolters 2014-05-21 08:35:18 UTC
After testing okular with some huge PDFs and experiencing no further issues I close this bug as WorksForMe.