[okular] [Bug 481831] New: When Memory Usage is Set Above Low, The Page Image Might Not Refresh Correctly

[Chris Miller]

https://bugs.kde.org/show_bug.cgi?id=481831

            Bug ID: 481831
           Summary: When Memory Usage is Set Above Low, The Page Image
                    Might Not Refresh Correctly
    Classification: Applications
           Product: okular
           Version: 23.08.5
          Platform: Fedora RPMs
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: general
          Assignee: okular-devel at kde.org
          Reporter: cbmiller2610 at live.com
  Target Milestone: ---

SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug
symbols.
See
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***


STEPS TO REPRODUCE
1. Set Memory Usage to Anything Above "Low"
2. Turn off continuous scroll
3. Change pages (sometimes it is ok for a while if just changing 1-2 pages,
scrolling rapidly through pages back and forth will immediately cause the
issue)
4. Page will eventually get stuck displaying a single page, although the page
numbers will change indicating that the image should be changing. 
5. Fullscreening or un-fullscreening the application unsticks the image.
6. Set memory usage to "Low", the problem goes away and pages can be scrolled
through at any speed and still update the page image correctly.



OBSERVED RESULT
Page image does not update, see video: https://youtu.be/lBQRTCoiEaE 

EXPECTED RESULT
Page image updates to reflect the current page no matter the speed of
scrolling, view settings, etc

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: Fedora 39 (Gnome+Wayland)
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Linux 6.7.5-200.fc39.x86_64 x86_64

PDF file that is being browsed is on a fuse filesystem using
google-drive-ocamlfuse

-- 
You are receiving this mail because:
You are the assignee for the bug.