Version: (using Devel) OS: Linux Installed from: Compiled sources KDE 4.3.80/Qt 4.6.0 as shipped by Mandriva Konqueror is set to open links in new tab instead of new window. I was viewing http://www.vor.at/tickets/wochenkarten/ and clicked on the last link on this page (Tarifzonenplan - http://www.vor.at/fileadmin/user_upload/downloads/News/11.2009/TZP_20_10_09_lr.pdf). It opened in new tab. I clicked several times on + to enlarge content. After that I got empty window. I think I already hit this several times in the past.
Can you attach a screenshot? I'm not sure i understand your problem.
Created attachment 39073 [details] Okular with too large zoom Sure; here you are. If I try to zoom too much I get no content at all. I have waited couple of minutes; I do not believe it is *that* slow. It does not apparently depend on being embedded. I get the same effect if I just view document (PDF) with okular directly and zoom too much. When I decrease zoom at some point content appears again.
Do you have Desktop Effects enabled? Does disabling them help?
I did the test with current trunk (svn rev 1063065). Disabling desktop effects did not help. messages from okular: konqueror(29441)/okular (app) Okular::Document::requestPixmaps: request id=3 4878x4927@0 konqueror(29441)/okular (app) Okular::DocumentPrivate::sendGeneratorRequest: Running out of memory on page 0 (4878x4927 px); konqueror(29441)/okular (app) Okular::DocumentPrivate::sendGeneratorRequest: this message will be reported only once. konqueror(29441)/okular (app) Okular::Document::requestPixmaps: request id=3 4878x4927@0
Yeah, this has been annoying me since ages, however this is the first time i paid attention to the output and did some research. Example output: okular(1391)/okular (app) Okular::DocumentPrivate::sendGeneratorRequest: Running out of memory on page 0 (7168x10096 px); It seems okular is trying to reserve a full sized image for each zoomlevel.. zooming in and out, memory size grows and shrinks again, but it is sometimes peaking out and subsequent zooming in will return that message. Guess the render logic would have to be altered quite a bit to solve this problem by rendering and allocating only parts of the document or so?
Are you willing to work on a patch?
Got me ^^ Sorry to say: No, nO0o way. Way beyond my abilities, and far down on my priorities. If i was the coding wiz that i am not, probably. Pardon me ;)
Possibly a duplicate of bug #185676.
Agree with #8. Is this bug a dup of 173681? They both appear to be stemming from the memory issue.
*** This bug has been marked as a duplicate of bug 185676 ***