Bug 251813 - Just keep scrolling
Summary: Just keep scrolling
Status: RESOLVED NOT A BUG
Alias: None
Product: okular
Classification: Applications
Component: general (show other bugs)
Version: 0.10.4
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Okular developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-09-20 12:22 UTC by Charlieb000
Modified: 2013-01-06 19:56 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 Charlieb000 2010-09-20 12:22:27 UTC
Application: okular (0.10.4)
KDE Platform Version: 4.4.4 (KDE 4.4.4) "release 2"
Qt Version: 4.6.3
Operating System: Linux 2.6.34.7-0.2-desktop i686
Distribution: "openSUSE 11.3 (i586)"

-- Information about the crash:
do note some ISPs may block the URL, but it is 100% safe.
the PDF file i download here is 31MB and is over 2000 pages. enough to put Okular through its paces....  all you have to do is scroll and it will stop showing text/images on the pages (blank sheets only) keep scrolling and it will crash. scroll up and you can see the pages it has drawn already. can be as few as 2 pages before crash, you may have to traverse 60 pages before they go blank. it may help the crashing if you click "contents" rather than "thumbnails".  i used mouse wheel and at another time sometimes page down.

site is (if you need to see it): http://www.free-energy-info.com/
PDF url is: http://www.free-energy-info.com/PJKbook.pdf
alternate url is http://www.megaupload.com/?d=2B6TXVN9  or http://www.filefactory.com/file/b31bfg8/n/PJKbook.pdf

enjoy!
Charlie.

not sure what "kde platform is compiled from sources" means.

The crash can be reproduced every time.

 -- Backtrace:
Application: Okular (okular), signal: Aborted
[KCrash Handler]
#6  0xffffe424 in __kernel_vsyscall ()
#7  0xb5e717ff in raise () from /lib/libc.so.6
#8  0xb5e73140 in abort () from /lib/libc.so.6
#9  0xb5e6a014 in __assert_fail () from /lib/libc.so.6
#10 0xb5acc8bd in _XAllocID (dpy=0x80898f0) at xcb_io.c:385
#11 0xb5aa0a2d in XCreateGC (dpy=0x80898f0, d=37748870, valuemask=0, values=0x0) at CrGC.c:93
#12 0xb63f3980 in ?? () from /usr/lib/libQtGui.so.4
#13 0xb633e264 in QPainter::begin(QPaintDevice*) () from /usr/lib/libQtGui.so.4
#14 0xb633ebeb in QPainter::QPainter(QPaintDevice*) () from /usr/lib/libQtGui.so.4
#15 0xb622e10b in QWidgetPrivate::drawWidget(QPaintDevice*, QRegion const&, QPoint const&, int, QPainter*, QWidgetBackingStore*) () from /usr/lib/libQtGui.so.4
#16 0xb640b9f7 in ?? () from /usr/lib/libQtGui.so.4
#17 0xb62236fb in QWidgetPrivate::syncBackingStore() () from /usr/lib/libQtGui.so.4
#18 0xb6233a16 in QWidget::event(QEvent*) () from /usr/lib/libQtGui.so.4
#19 0xb664920c in QMainWindow::event(QEvent*) () from /usr/lib/libQtGui.so.4
#20 0xb722f364 in KMainWindow::event(QEvent*) () from /usr/lib/libkdeui.so.5
#21 0xb722f602 in KXmlGuiWindow::event(QEvent*) () from /usr/lib/libkdeui.so.5
#22 0xb61d9c64 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#23 0xb61e1ca4 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#24 0xb719d9d1 in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5
#25 0xb6c84e0e in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4
#26 0xb6c889b4 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/libQtCore.so.4
#27 0xb6c88b9c in QCoreApplication::sendPostedEvents(QObject*, int) () from /usr/lib/libQtCore.so.4
#28 0xb6cb083d in ?? () from /usr/lib/libQtCore.so.4
#29 0xb581eb49 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#30 0xb581f350 in ?? () from /usr/lib/libglib-2.0.so.0
#31 0xb581f60e in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#32 0xb6cb0d4b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#33 0xb628a19a in ?? () from /usr/lib/libQtGui.so.4
#34 0xb6c8411d in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#35 0xb6c84319 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#36 0xb6c88c70 in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4
#37 0xb61d7164 in QApplication::exec() () from /usr/lib/libQtGui.so.4
#38 0x0804ef28 in _start ()

Reported using DrKonqi
Comment 1 Charlieb000 2010-09-20 12:24:25 UTC
thumbnails are still seen even though pages are blank.
Comment 2 Albert Astals Cid 2010-09-22 00:58:02 UTC
Works for me.
Can you please run
valgrind okular /path/to/the/file.pdf
and see if it crashes and paste the output?
Comment 3 Charlieb000 2010-09-22 12:49:11 UTC
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.....
Comment 4 Albert Astals Cid 2010-09-22 20:59:19 UTC
Did you get any crash when running it using valgrind?
Comment 5 Charlieb000 2010-09-23 22:27:27 UTC
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.)
Comment 6 jordonwii 2012-01-05 05:57:35 UTC
This could be a dup of bug 199250.
Comment 7 Albert Astals Cid 2012-08-20 22:42:04 UTC
Can you reproduce this crash in modern KDE software versions? e.g something newer than 4.8?
Comment 8 Albert Astals Cid 2013-01-06 19:56:59 UTC
4 months and no answer, closing as invalid.

If you can still reproduce please reopen the bug.