# Unpleasant scrolling behavior

**URL:** <https://community.bildhuus.com/t/unpleasant-scrolling-behavior/487>\
**Category:** Bug Reports\
**Tags:** resolved\
**Created:** [6 December 2024 16:34 UTC](https://community.bildhuus.com/t/unpleasant-scrolling-behavior/487 "2024-12-06T16:34:57Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![kuzmandi](https://community.bildhuus.com/user_avatar/community.bildhuus.com/kuzmandi/32/163_2.png) [@kuzmandi](https://community.bildhuus.com/u/kuzmandi)\
**Post date:** [6 December 2024 16:34 UTC](https://community.bildhuus.com/t/unpleasant-scrolling-behavior/487/1 "2024-12-06T16:34:57Z")

</div>

## Observed/expected behavior

Strange behaviour with scrolling up and down. It doesn’t feel smooth, but it hacks and jams a little, as if, for example, a content is not finished loading and therefore cannot yet be in the field of vision. This goes on all the time. (The images are stored on an SSD, so access should not be the cause. The library currently has about 450 photos with about 5GB in total.)

## Steps required to reproduce

Just open the photo stream and scroll up or down.

## System information

Software: aspect  
Software version: 1.0.0-rc.4  
Operating system: macos  
Hardware Information: 2,3 GHz 8-Core Intel Core i9, 16 GB 2667 MHz DDR4, Intel UHD Graphics 630 1536 MB

---

<div class="post-metadata">

**Author:** ![Soenke](https://community.bildhuus.com/user_avatar/community.bildhuus.com/soenke/32/59_2.png) [@Soenke](https://community.bildhuus.com/u/Soenke)\
**Post date:** [7 December 2024 13:48 UTC](https://community.bildhuus.com/t/unpleasant-scrolling-behavior/487/2 "2024-12-07T13:48:10Z")

</div>

We have an existing attempt to fix the hiccups during scrolling in a yet unpublished branch, which still needs a bit of work. The cause lies in the upload of image data from system memory to GPU memory, which is currently done in the UI thread. This isn’t usually a problem, but for event paragraphs, the images can actually become rather large, especially on high-DPI screens. I’m not sure whether the fix will still land in 1.0.0, but if not, then soon after.
