[Bug] SHORT DESCRIPTION

[XYgnnJ]

621

1.0.2

https://m.bilibili.com/video/BV1PUTFe2EPk

[GfEW]

Despite the blatant lack of specifics in this report, I've watched the video.

For one thing, it that does feature NeoStore.

For another, it's actually an excellent demonstration of the rapid, severe performance degradation in NeoStore 1.0.x (so far) that often ends up in a GUI deadlock or even ANR.

I've captured the problem in screencasts of my own before, but @XYgnnJ shows it with Android's "top"-like process list screen overlay enabled, which adds much more insight. As we can see, "frozen" NeoStore steadily consumes ca. 12.5% CPU on @XYgnnJ's phone, supposedly hogging one core out of eight.

At first glace, I found it difficult to understand which exact point(s) @XYgnnJ is trying to make. To make things easier for you, here's a timeline of the video, together with NeoStore's respective CPU% (rough average) in each step, in parentheses:

• 00:00 (23% CPU) The apps list is being populated.
• 00:05 (18%) A search string is entered, the apps list is filtered instantly.
• 00:11 (9%) The filtered apps list is scrolled back and forth, with no noticable lag or stutter.
• 00:21 (1%) The app "Easy Notes" is tapped, followed by 6 s waiting time.
• 00:27 (24%) The details of "Easy Notes" start showing up.
• 00:29 (29%) Back in the filtered apps list, it is scrolled again, still quick and smooth.
• 00:35 (6%) The app "Easy Notes" is tapped, instantly opened, and quickly left again.
• 00:39 (40%) The app "Standard Notes" is tapped, instantly opened, and quickly left.
• 00:40 (22%) Back in the filtered apps list, scrolling back and forth shows increasing lags and stuttering, while NeoStore's CPU usage declines from 40% to 15%.
• 00:48 (13%) NeoStore stops responding to further scroll attempts (note the tap indicator).
• 00:54 After some last jerks, NeoStore's GUI freezes for 18 seconds, while its CPU usage arrives at ca. 12.5% and stays there until the end of the video.
• 01:12 NeoStore briefly manages to update the screen again, causing another jerk - and the freeze continues.

According to the screen overlay, content is rendered between 56 and 61 fps throughout the entire screen capture.

To make this insight more accessible (which it IMHO deserves regardless of poor initial reporting quality), please rename this issue to sth like "Apps list scrolling freeze, CPU at 12.5%".