[Okular-devel] [Bug 177213] High X server memory consumption
https://bugs.kde.org/show_bug.cgi?id=177213 Fest changed: What|Removed |Added CC||fest...@gmail.com --- Comment #20 from Fest 2010-03-17 11:30:24 --- Gentoo amd64, KDE 4.4.1, Xorg-server 1.7.5. Left yesterday Okular open. For a night X memory consumption grown from 50 to 800 Mb. Closing Okular freed 50 Mb from X, so something like 700 Mb of leaked memory. Nice. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Okular-devel mailing list Okular-devel@kde.org https://mail.kde.org/mailman/listinfo/okular-devel
[Okular-devel] [Bug 177213] High X server memory consumption
https://bugs.kde.org/show_bug.cgi?id=177213 --- Comment #21 from Albert Astals Cid 2010-03-17 12:05:05 --- And the evidence that Okular is the one at fault is where? Because i've run valgrind over and over and never could find any memory leak. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Okular-devel mailing list Okular-devel@kde.org https://mail.kde.org/mailman/listinfo/okular-devel
[Okular-devel] [Bug 177213] High X server memory consumption
https://bugs.kde.org/show_bug.cgi?id=177213 --- Comment #22 from Fest 2010-03-17 12:19:49 --- (In reply to comment #21) > And the evidence that Okular is the one at fault is where? Because i've run > valgrind over and over and never could find any memory leak. Xrestop is good enough ? Before closing okular, it showed that most memory amount was used by okular. Can you tell me what to do with valgrind, and i'll give output. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Okular-devel mailing list Okular-devel@kde.org https://mail.kde.org/mailman/listinfo/okular-devel
[Okular-devel] [Bug 177213] High X server memory consumption
https://bugs.kde.org/show_bug.cgi?id=177213 --- Comment #23 from Albert Astals Cid 2010-03-17 12:45:36 --- xrestop will be of use if you can prove that okular memory usage raises while doing nothing with it. for valgrind it's easy, do valgrind --leak-check=full okular and then look at the figures it gives at the end. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Okular-devel mailing list Okular-devel@kde.org https://mail.kde.org/mailman/listinfo/okular-devel
[Okular-devel] [Bug 177213] High X server memory consumption
https://bugs.kde.org/show_bug.cgi?id=177213 --- Comment #24 from Fest 2010-03-17 13:09:34 --- I didn't tell that "okular memory usage raises while doing nothing with it." I told that okular used X for caching(?) 700 mb, and after closing okular memory (700 mb) is not free. And xrestop shows that X already not storing okular pixmaps. Ok. I'm installing valgrind. I'll post here if it show something. Although as i understood from discussion above, it's problem with X freeing pixmaps. I'm not programmer, i have no idea who's mistake is that: bug in X or wrong usage of X cache by okular. All i know okular usage is draining memory. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Okular-devel mailing list Okular-devel@kde.org https://mail.kde.org/mailman/listinfo/okular-devel
[Okular-devel] [Bug 177213] High X server memory consumption
https://bugs.kde.org/show_bug.cgi?id=177213 --- Comment #25 from Oscar Fuentes 2010-03-17 13:13:34 --- (In reply to comment #21) > And the evidence that Okular is the one at fault is where? Because i've run > valgrind over and over and never could find any memory leak. How is valgrind relevant here? This bug is not about a memory leak in okular, but about okular allocating hundreds of MBs of pixmaps on the X server. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Okular-devel mailing list Okular-devel@kde.org https://mail.kde.org/mailman/listinfo/okular-devel
[Okular-devel] [Bug 231097] New: okular crashed on exiting
https://bugs.kde.org/show_bug.cgi?id=231097 Summary: okular crashed on exiting Product: okular Version: unspecified Platform: Unlisted Binaries OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: okular-devel@kde.org ReportedBy: stefanbel...@googlemail.com Application that crashed: okular Version of the application: 0.9.4 KDE Version: 4.3.4 (KDE 4.3.4) Qt Version: 4.5.3 Operating System: Linux 2.6.30-2-686 i686 What I was doing when the application crashed: i had opened a pdf which was generated with dvipdf on exiting okular, okular crashed Okular Version 0.9.4 Using KDE 4.3.4 (KDE 4.3.4) -- Backtrace: Application: Okular (okular), signal: Segmentation fault [KCrash Handler] #6 0xb4924ded in Okular::Document::closeDocument (this=0x920c030) at ../../okular/core/document.cpp:1760 #7 0xb49b129d in Okular::Part::closeUrl (this=0x9202168) at ../../okular/part.cpp:1099 #8 0xb80136d6 in KParts::ReadOnlyPart::openUrl (this=0x9202168, url=...) at ../../kparts/part.cpp:537 #9 0xb49bdf2f in Okular::Part::slotDoFileDirty (this=0x9202168) at ../../okular/part.cpp:1195 #10 0xb49be614 in Okular::Part::qt_metacall (this=0x9202168, _c=QMetaObject::InvokeMetaMethod, _id=40, _a=0xbff929fc) at ./part.moc:216 #11 0xb764a303 in QMetaObject::activate (sender=0x93d7870, from_signal_index=5, to_signal_index=6, argv=0xbff929fc) at kernel/qobject.cpp:3112 #12 0xb764a720 in QMetaObject::activate (sender=0x93d7870, m=0xb74cd1c8, from_local_signal_index=1, to_local_signal_index=2, argv=0xbff929fc) at kernel/qobject.cpp:3206 #13 0xb6c6e591 in QAction::triggered (this=0x93d7870, _t1=false) at .moc/release-shared/moc_qaction.cpp:236 #14 0xb6c6fadf in QAction::activate (this=0x93d7870, event=QAction::Trigger) at kernel/qaction.cpp:1167 #15 0xb6c72513 in QAction::event (this=0x93d7870, e=0xbff92e54) at kernel/qaction.cpp:1086 #16 0xb7ad3b73 in KAction::event (this=0x93d7870, event=0xbff92e54) at ../../kdeui/actions/kaction.cpp:88 #17 0xb6c74a94 in QApplicationPrivate::notify_helper (this=0x9163790, receiver=0x93d7870, e=0xbff92e54) at kernel/qapplication.cpp:4065 #18 0xb6c7cbee in QApplication::notify (this=0xbff9e698, receiver=0x93d7870, e=0xbff92e54) at kernel/qapplication.cpp:3605 #19 0xb7bb9e2a in KApplication::notify (this=0xbff9e698, receiver=0x93d7870, event=0xbff92e54) at ../../kdeui/kernel/kapplication.cpp:302 #20 0xb76351eb in QCoreApplication::notifyInternal (this=0xbff9e698, receiver=0x93d7870, event=0xbff92e54) at kernel/qcoreapplication.cpp:610 #21 0xb6cad758 in QCoreApplication::sendEvent (this=0x9163830, e=0xbff931fc) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213 #22 QShortcutMap::dispatchEvent (this=0x9163830, e=0xbff931fc) at kernel/qshortcutmap.cpp:884 #23 0xb6caf5ef in QShortcutMap::tryShortcutEvent (this=0x9163830, o=0x9389700, e=0xbff931fc) at kernel/qshortcutmap.cpp:369 #24 0xb6c7de70 in QApplication::notify (this=0xbff9e698, receiver=0x9389700, e=0xbff931fc) at kernel/qapplication.cpp:3647 #25 0xb7bb9e2a in KApplication::notify (this=0xbff9e698, receiver=0x9389700, event=0xbff931fc) at ../../kdeui/kernel/kapplication.cpp:302 #26 0xb76351eb in QCoreApplication::notifyInternal (this=0xbff9e698, receiver=0x9389700, event=0xbff931fc) at kernel/qcoreapplication.cpp:610 #27 0xb6c7591e in QCoreApplication::sendSpontaneousEvent (receiver=0x9389700, event=0x8) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:216 #28 qt_sendSpontaneousEvent (receiver=0x9389700, event=0x8) at kernel/qapplication.cpp:4975 #29 0xb6d11170 in QKeyMapper::sendKeyEvent (keyWidget=0x9389700, grab=false, type=QEvent::KeyPress, code=16777268, modifiers=..., text=..., autorepeat=, count=, nativeScanCode=71, nativeVirtualKey=65474, nativeModifiers=0) at kernel/qkeymapper_x11.cpp:1861 #30 0xb6d13244 in QKeyMapperPrivate::translateKeyEvent (this=0x918be90, keyWidget=0x9389700, event=0xbff949fc, grab=40) at kernel/qkeymapper_x11.cpp:1831 #31 0xb6ce9649 in QApplication::x11ProcessEvent (this=0xbff9e698, event=0xbff949fc) at kernel/qapplication_x11.cpp:3445 #32 0xb6d14bc2 in x11EventSourceDispatch (s=0x91669b0, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146 #33 0xb63ddb38 in g_main_context_dispatch () from /lib/libglib-2.0.so.0 #34 0xb63e13d0 in ?? () from /lib/libglib-2.0.so.0 #35 0xb63e1503 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #36 0xb7660041 in QEventDispatcherGlib::processEvents (this=0x914dd28, flags=...) at kernel/qeventdispatcher_glib.cpp:407 #37 0xb6d14305 in QGuiEventDispatcherGlib::processEvents (this=0x914dd28, flags=...) at kernel/qguieventdispatcher_glib.cpp:202 #38 0xb763383a in QEventLoop::processEvents (this=0xbff94d0c, flags=...) at kernel/qeventloop.cpp:149 #39 0xb7633c82 in QEventLoop::exec (this=0xbff94d0c, flags=...) at kernel/qeventloop.cpp:201 #40 0xb4924dea in Okular::Document::close
[Okular-devel] [Bug 225758] Crashed just after closing
https://bugs.kde.org/show_bug.cgi?id=225758 Nicolas Lécureuil changed: What|Removed |Added CC||stefanbel...@googlemail.com --- Comment #2 from Nicolas Lécureuil 2010-03-17 15:14:14 --- *** Bug 231097 has been marked as a duplicate of this bug. *** -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Okular-devel mailing list Okular-devel@kde.org https://mail.kde.org/mailman/listinfo/okular-devel
[Okular-devel] [Bug 231097] okular crashed on exiting
https://bugs.kde.org/show_bug.cgi?id=231097 Nicolas Lécureuil changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||nlecure...@mandriva.com Resolution||DUPLICATE --- Comment #1 from Nicolas Lécureuil 2010-03-17 15:14:14 --- *** This bug has been marked as a duplicate of bug 225758 *** -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Okular-devel mailing list Okular-devel@kde.org https://mail.kde.org/mailman/listinfo/okular-devel
[Okular-devel] [Bug 231113] New: printing multiple pages on one page does not work
https://bugs.kde.org/show_bug.cgi?id=231113 Summary: printing multiple pages on one page does not work Product: okular Version: 0.10.1 Platform: unspecified OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general AssignedTo: okular-devel@kde.org ReportedBy: w.rich...@gmx.net Version: 0.10.1 (using 4.4.1 (KDE 4.4.1), Kubuntu packages) Compiler: cc OS:Linux (x86_64) release 2.6.31-20-generic Printing multiple latex-beamer pages on one page does not work. It always prints 1 on 1. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Okular-devel mailing list Okular-devel@kde.org https://mail.kde.org/mailman/listinfo/okular-devel
[Okular-devel] [Bug 177213] High X server memory consumption
https://bugs.kde.org/show_bug.cgi?id=177213 --- Comment #26 from Albert Astals Cid 2010-03-17 16:33:00 --- #25 to me it's fairly obvious, each time you allocate a X pixmap in the server side you get a handle in your process, if you don't free the local handle there is a local leak, if you do not leak it, it means you freed the X pixmap too. But as it seems you have a better idea i'm open to your suggestions. And well, if the bug is about okular allocating X memory we can close it altogether because that is not a bug at all. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Okular-devel mailing list Okular-devel@kde.org https://mail.kde.org/mailman/listinfo/okular-devel
[Okular-devel] [Bug 177213] High X server memory consumption
https://bugs.kde.org/show_bug.cgi?id=177213 --- Comment #27 from Fest 2010-03-17 16:53:39 --- (In reply to comment #26) > And well, if the bug is about okular allocating X memory we can close it > altogether because that is not a bug at all. Yeah. It's not bug, it's feature. Just need to add to changelog: now okular not only open pdf, but also help you to get rid out of your memory. Seriously, even if okular doing everything right, at the end we have memory leak. It's bug. If guys from X don't want to patch, so okular team need to create workaround . Cause right now after using okular people have to restart. If it's not bug for you guys, i don't know what can be. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Okular-devel mailing list Okular-devel@kde.org https://mail.kde.org/mailman/listinfo/okular-devel
[Okular-devel] [Bug 231123] New: okular crashes after closing print preview and then pressing F6
https://bugs.kde.org/show_bug.cgi?id=231123 Summary: okular crashes after closing print preview and then pressing F6 Product: okular Version: 0.10.1 Platform: Ubuntu Packages OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: okular-devel@kde.org ReportedBy: ste...@endrullis.de Application: okular (0.10.1) KDE Platform Version: 4.4.1 (KDE 4.4.1) Qt Version: 4.6.2 Operating System: Linux 2.6.32-16-generic x86_64 Distribution: Ubuntu lucid (development branch) -- Information about the crash: It's a reproducable crash of okular. All you have to do is: - open print preview - close print preview - press F6 -> crash -- Backtrace: Application: Okular (okular), signal: Segmentation fault [Current thread is 1 (Thread 0x7f827f744800 (LWP 17779))] Thread 2 (Thread 0x7f826c7ea710 (LWP 17805)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162 #1 0x7f827dce372b in QWaitConditionPrivate::wait (this=, mutex=0x2a09dc0, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:87 #2 QWaitCondition::wait (this=, mutex=0x2a09dc0, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:159 #3 0x7f827dcdf680 in QSemaphore::acquire (this=0x2f8bcb0, n=1) at thread/qsemaphore.cpp:142 #4 0x7f8268ceee2f in GSRendererThread::run (this=0x2f8bca0) at ../../../../okular/generators/spectre/rendererthread.cpp:50 #5 0x7f827dce2775 in QThreadPrivate::start (arg=0x2f8bca0) at thread/qthread_unix.cpp:248 #6 0x7f827aee29ca in start_thread (arg=) at pthread_create.c:300 #7 0x7f827ca2338d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #8 0x in ?? () Thread 1 (Thread 0x7f827f744800 (LWP 17779)): [KCrash Handler] #5 0x7f827e9f9017 in QString (this=0x188, group=0, state=0) at /usr/include/qt4/QtCore/qstring.h:714 #6 KIconEffect::fingerprint (this=0x188, group=0, state=0) at ../../kdeui/icons/kiconeffect.cpp:158 #7 0x7f827ea04d88 in KIconLoader::loadIcon (this=0x2f86fd0, _name=..., group=, size=32, state=, overlays=..., path_store=0x0, canReturnNull=false) at ../../kdeui/icons/kiconloader.cpp:1085 #8 0x7f827e9fd5ad in KIconEngine::pixmap (this=, size=..., mode=, state=) at ../../kdeui/icons/kiconengine.cpp:119 #9 0x7f827d2424c5 in QIcon::pixmap (this=, size=..., mode=QIcon::Normal, state=7274607) at image/qicon.cpp:669 #10 0x7f827d4a232f in QCommonStyle::drawControl (this=0x26917e0, element=, opt=0x7fff62c21040, p=0x7fff62c21620, widget=0x262e1a0) at styles/qcommonstyle.cpp:1597 #11 0x7f827ea4e4e2 in KStyle::drawControl (this=0x26917e0, element=QStyle::CE_ToolButtonLabel, option=0x7fff62c21040, p=, widget=0x262e1a0) at ../../kdeui/kernel/kstyle.cpp:2508 #12 0x7f8273be811d in OxygenStyle::drawControl (this=0x26917e0, element=, option=0x7fff62c21040, p=0x7fff62c21620, widget=0x262e1a0) at ../../../kstyles/oxygen/oxygen.cpp:607 #13 0x7f827ea4bddc in KStyle::drawComplexControl (this=0x26917e0, cc=, opt=0x7fff62c215a0, p=, w=0x262e1a0) at ../../kdeui/kernel/kstyle.cpp:3473 #14 0x7f8273bdf3fa in OxygenStyle::drawComplexControl (this=0x26917e0, control=QStyle::CC_ToolButton, option=0x7fff62c215a0, painter=0x7fff62c21620, widget=0x2d006c006f006f) at ../../../kstyles/oxygen/oxygen.cpp:299 #15 0x7f827d614fb8 in QStylePainter::drawComplexControl (this=0x262e1a0) at ../../include/QtGui/../../src/gui/painting/qstylepainter.h:94 #16 QToolButton::paintEvent (this=0x262e1a0) at widgets/qtoolbutton.cpp:556 #17 0x7f827d1e6172 in QWidget::event (this=0x262e1a0, event=0x7fff62c21e30) at kernel/qwidget.cpp:8144 #18 0x7f827d19022c in QApplicationPrivate::notify_helper (this=0x25ec610, receiver=0x262e1a0, e=0x7fff62c21e30) at kernel/qapplication.cpp:4300 #19 0x7f827d1966fb in QApplication::notify (this=0x7fff62c257d0, receiver=0x262e1a0, e=0x7fff62c21e30) at kernel/qapplication.cpp:4183 #20 0x7f827ea3d506 in KApplication::notify (this=0x7fff62c257d0, receiver=0x262e1a0, event=0x7fff62c21e30) at ../../kdeui/kernel/kapplication.cpp:302 #21 0x7f827ddd6ffc in QCoreApplication::notifyInternal (this=0x7fff62c257d0, receiver=0x262e1a0, event=0x7fff62c21e30) at kernel/qcoreapplication.cpp:704 #22 0x7f827d1ee7ed in QCoreApplication::sendSpontaneousEvent (this=0x29012f0, pdev=, rgn=..., offset=, flags=, sharedPainter=0x0, backingStore=0x2952c20) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:218 #23 QWidgetPrivate::drawWidget (this=0x29012f0, pdev=, rgn=..., offset=, flags=, sharedPainter=0x0, backingStore=0x2952c20) at kernel/qwidget.cpp:5339 #24 0x7f827d1ef488 in QWidgetPrivate::paintSiblingsRecursive (this=, pdev=, siblings=..., index=1, rgn=, offset=, flags=4, sharedPainter=0x0, backingStore=0x2952c20) at kernel/qwidget.cpp:5452 #25 0x7f827d1ef2b9 in Q
[Okular-devel] [Bug 177213] High X server memory consumption
https://bugs.kde.org/show_bug.cgi?id=177213 --- Comment #28 from Albert Astals Cid 2010-03-17 17:43:55 --- #27 Being sarcastic is not going to make people help you so spare ourselves that comments everyone will be happier. It being a bug i agree, but we still have to find whose fault it is before we can fix it. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Okular-devel mailing list Okular-devel@kde.org https://mail.kde.org/mailman/listinfo/okular-devel
[Okular-devel] [Bug 177213] High X server memory consumption
https://bugs.kde.org/show_bug.cgi?id=177213 --- Comment #29 from Oscar Fuentes 2010-03-17 19:45:25 --- (In reply to comment #26) > #25 to me it's fairly obvious, each time you allocate a X pixmap in the server > side you get a handle in your process, if you don't free the local handle > there > is a local leak, if you do not leak it, it means you freed the X pixmap too. > > But as it seems you have a better idea i'm open to your suggestions. > > And well, if the bug is about okular allocating X memory we can close it > altogether because that is not a bug at all. This was discussed on the past. The X server (all X servers I know) are not so smart managing resources that they can cope with the usage pattern okular does. Even if okular frees all handles, the X server sometimes does not give back to the OS all the allocated memory, and then fragmentation can prevent reusing that memory on another okular session. This is not a problem with most X applications, because the amount of allocated X resources is low (compared with okular). As mentioned on the past too, I did some informal benchmarks and perceived no speed difference on page rendering after changing Okular's memory usage setting, nor I perceive differences with other pdf viewers (xpdf, for instance). What I observe is performance degradation when X ends having gigabytes of allocated memory after heavy use of okular with the "normal" memory usage setting. This is a critical issue when the X server is a machine wiht 1 GB of RAM and the X client has 8 GB: after browsing a few hundred pages the X server starts paginating and finally crashes due to lack of memory. So, it is not a bug on okular itself, but a QoI (quality of implementation) issue. The X server is not as smart is we would like it to be; okular is abusing the X server when it allocates hundreds of MBs of pixmaps; sometimes this usage pattern ends on serious performance degradation or crashes. So, why don't you set the default setting to "low memory usage"? You claimed on the past that the current setting was chosen due to the performance improvement that it provides. My experience shows that there is no such improvement. Perhaps you can show a case that justifies the huge memory usage? -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Okular-devel mailing list Okular-devel@kde.org https://mail.kde.org/mailman/listinfo/okular-devel
[Okular-devel] [Bug 177213] High X server memory consumption
https://bugs.kde.org/show_bug.cgi?id=177213 --- Comment #30 from Pino Toscano 2010-03-17 19:52:54 --- (In reply to comment #29) > As mentioned on the past too, I did some informal benchmarks and perceived no > speed difference on page rendering after changing Okular's memory usage > setting, nor I perceive differences with other pdf viewers (xpdf, for > instance). Your personal benchmarks are not our personal benchmarks nor other people's benchmarks. > This is a critical issue when the X server is a machine > wiht 1 GB of RAM and the X client has 8 GB: after browsing a few hundred pages > the X server starts paginating and finally crashes due to lack of memory. This is another issue, unrelated to this one. Please keep it separate. > So, why don't you set the default setting to "low memory usage"? You claimed > on > the past that the current setting was chosen due to the performance > improvement > that it provides. My experience shows that there is no such improvement. See first phrase above. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Okular-devel mailing list Okular-devel@kde.org https://mail.kde.org/mailman/listinfo/okular-devel
[Okular-devel] [Bug 231135] New: on page turn the text is blurred despite setting background processing off
https://bugs.kde.org/show_bug.cgi?id=231135 Summary: on page turn the text is blurred despite setting background processing off Product: okular Version: unspecified Platform: openSUSE RPMs OS/Version: unspecified Status: UNCONFIRMED Severity: normal Priority: NOR Component: PDF backend AssignedTo: okular-devel@kde.org ReportedBy: bluedz...@wp.pl Version:(using KDE 4.4.0) Installed from:SuSE RPMs I recently updated okular to okular-4.4.1-153.9 and in this version there no matter if I set background off/on, on page turn the text is initially blurred. So it is a regression -- in previous versions okular was working according to background/foreground processing setting. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Okular-devel mailing list Okular-devel@kde.org https://mail.kde.org/mailman/listinfo/okular-devel
[Okular-devel] [Bug 231123] okular crashes after closing print preview and then pressing F6
https://bugs.kde.org/show_bug.cgi?id=231123 Albert Astals Cid changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution||FIXED --- Comment #1 from Albert Astals Cid 2010-03-17 20:37:59 --- SVN commit 1104494 by aacid: make the iconloader in GuiUtils a stack Fixes problems when the same program uses more than one okular part at once BUGS: 231123 M +2 -1 part.cpp M +9 -5 ui/guiutils.cpp M +2 -1 ui/guiutils.h WebSVN link: http://websvn.kde.org/?view=rev&revision=1104494 -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Okular-devel mailing list Okular-devel@kde.org https://mail.kde.org/mailman/listinfo/okular-devel
[Okular-devel] [Bug 231123] okular crashes after closing print preview and then pressing F6
https://bugs.kde.org/show_bug.cgi?id=231123 --- Comment #2 from Albert Astals Cid 2010-03-17 20:40:54 --- SVN commit 1104495 by aacid: Backport r1104494 | aacid | 2010-03-17 19:37:52 + (Wed, 17 Mar 2010) | 4 lines make the iconloader in GuiUtils a stack Fixes problems when the same program uses more than one okular part at once BUGS: 231123 M +2 -1 part.cpp M +9 -5 ui/guiutils.cpp M +2 -1 ui/guiutils.h WebSVN link: http://websvn.kde.org/?view=rev&revision=1104495 -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Okular-devel mailing list Okular-devel@kde.org https://mail.kde.org/mailman/listinfo/okular-devel
[Okular-devel] [Bug 208990] Please add "print current page" option
https://bugs.kde.org/show_bug.cgi?id=208990 Mat changed: What|Removed |Added CC||jackdac...@gmail.com --- Comment #3 from Mat 2010-03-17 20:17:16 --- What a bummer ! Thanks for the info ! -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Okular-devel mailing list Okular-devel@kde.org https://mail.kde.org/mailman/listinfo/okular-devel
[Okular-devel] [Bug 177213] High X server memory consumption
https://bugs.kde.org/show_bug.cgi?id=177213 --- Comment #31 from Oscar Fuentes 2010-03-17 20:23:04 --- (In reply to comment #30) > (In reply to comment #29) > > As mentioned on the past too, I did some informal benchmarks and perceived > > no > > speed difference on page rendering after changing Okular's memory usage > > setting, nor I perceive differences with other pdf viewers (xpdf, for > > instance). > > Your personal benchmarks are not our personal benchmarks nor other people's > benchmarks. Thanks for making this a constructive discussion. :-/ > > This is a critical issue when the X server is a machine > > wiht 1 GB of RAM and the X client has 8 GB: after browsing a few hundred > > pages > > the X server starts paginating and finally crashes due to lack of memory. > > This is another issue, unrelated to this one. Please keep it separate. Well, if you don't see the relation, I give up. It is obvious that you are too proud of the "genial" idea of using the X server as a cache for Okular and are not willing to admit that it has some serious drawbacks. As far as I'm concerned, do with this bug report whatever you please. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Okular-devel mailing list Okular-devel@kde.org https://mail.kde.org/mailman/listinfo/okular-devel
[Okular-devel] [Bug 208990] Please add "print current page" option
https://bugs.kde.org/show_bug.cgi?id=208990 --- Comment #4 from Mat 2010-03-17 20:23:37 --- great news ! from what I can tell 4.7.0 should include the requested / needed feature: http://bugreports.qt.nokia.com/browse/QTBUG-4214 :) -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Okular-devel mailing list Okular-devel@kde.org https://mail.kde.org/mailman/listinfo/okular-devel
[Okular-devel] [Bug 177213] High X server memory consumption
https://bugs.kde.org/show_bug.cgi?id=177213 --- Comment #32 from Pino Toscano 2010-03-17 20:53:27 --- (In reply to comment #31) > (In reply to comment #30) > > (In reply to comment #29) > > > As mentioned on the past too, I did some informal benchmarks and > > > perceived no > > > speed difference on page rendering after changing Okular's memory usage > > > setting, nor I perceive differences with other pdf viewers (xpdf, for > > > instance). > > > > Your personal benchmarks are not our personal benchmarks nor other people's > > benchmarks. > > Thanks for making this a constructive discussion. :-/ Right, because claiming "I did some generic benchmarks so change the behaviour" is constructive? > > > This is a critical issue when the X server is a machine > > > wiht 1 GB of RAM and the X client has 8 GB: after browsing a few hundred > > > pages > > > the X server starts paginating and finally crashes due to lack of memory. > > > > This is another issue, unrelated to this one. Please keep it separate. > > Well, if you don't see the relation, I give up. Right, I don't see the relation. The issue you mentioned could be fixed even still with Okular using X. > It is obvious that you are too > proud of the "genial" idea of using the X server as a cache for Okular and are > not willing to admit that it has some serious drawbacks. Don't be ridicolous and put words in our mouths or ideas in our minds which are *not* ours. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Okular-devel mailing list Okular-devel@kde.org https://mail.kde.org/mailman/listinfo/okular-devel
