I noticed the message list card pegging the FPS rate and cpu when I tried to open my localdrafts folder. CPU usage was very high, and if I tried to pull down the scroll region where the search bar was hiding, it would jerkily return to the top. This suggests that we have some kind of very broken logic relating to scrolling / infinite scroll on the message list card.
I jumped the gun on filing this; there was a bug in the localdrafts implementation that caused a tight infinite loop.
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → INVALID
Well, not tight. It was a 'grow' loop, but it was bad.
You need to log in before you can comment on or make changes to this bug.