Summary: | Just keep scrolling | ||
---|---|---|---|
Product: | [Applications] okular | Reporter: | Charlieb000 <nothereforever> |
Component: | general | Assignee: | Okular developers <okular-devel> |
Status: | RESOLVED NOT A BUG | ||
Severity: | crash | CC: | aacid, jordonwii |
Priority: | NOR | ||
Version: | 0.10.4 | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Charlieb000
2010-09-20 12:22:27 UTC
thumbnails are still seen even though pages are blank. Works for me. Can you please run valgrind okular /path/to/the/file.pdf and see if it crashes and paste the output? it went real slow! i made sure it loaded every page and it did nothing from 184 to 400 what a bore had to scroll it and wait - and linux dont even support center mouse button scrolling like all the Winny programs do (press the button then move the mouse away from that place and the distance you move it from there determines the speed and direction).... i closed it and opened it normally (without valgrind) and used PageDown to scroll fast. after 90 pages it started showing white sheets. if your memory scanning program can work very fast then we can catch it. i noticed it never used both of my cores - if you can put the memory scanner on one core and the interface on the other then it might be found. if you want to confirm it then i might be able to video tape it. maybe putting the file on another drive could fix the problem, it could be an IO speed thing though it normally shows the logo till the page loads..... Did you get any crash when running it using valgrind? i said in the last message no. it was way too slow. if the program worked fast then it may have happened. charlie. (for some reason KDE.org was going to change it to "fixed" so i changed it to "waiting for info" as no other option fit.) This could be a dup of bug 199250. Can you reproduce this crash in modern KDE software versions? e.g something newer than 4.8? 4 months and no answer, closing as invalid. If you can still reproduce please reopen the bug. |