lichess-org
Slow piece rendering in Puzzle Races
Exact URL of where the bug happened
(This is one example of a single server but it happens in every single game in some past time - I don't believe this is connected to the specific server) https://lichess.org/racer/KmGwA
Steps to reproduce the bug
- start a puzzle racer game
- do a couple of puzzles, eventually you'll see slow render
What did you expect to happen?
fast consistently rendering pieces in puzzles
What happened instead?
If you solve a couple of puzzles in the puzzle races, you'll eventually end up with piece rendering which takes up to 2-3s for some pieces, whilst being completely normal for all others. It might seem ridicolous to complain about different rendering of some pieces, but I often started solving puzzles, only for 4 pieces to appear after 2s when I was moving a piece - making it a completely different (and more sensible) puzzle altogether
Operating system
MacOS
Browser and version (or alternate access method)
Brave browser
Additional information
I believe this issue arose relatively lately, although I have not been playing many puzzle racers before. If'd to guess, it would be connected to the overhaul of the racer section (new cars,...)
Does not seem to be an issue on Safari. Should I try to recreate it on any other major browser?
Any additional info you can provide is helpful, but I haven't been able to reproduce this in Chrome or Firefox on fedora or mac.
Yeah, from what I have tried, I'd say it seems to be Brave related issue, I'll try if I can reporduce it on different device or browser on my device and will let you know
It appears to me that the bug is extended way beyond puzzle racer itself. Even things that have to appear fast on the board (red underline of check for example during a game) also has a notable delay on the Brave Browser, haven't noticed it anywhere else
I just successfully reproduced both of the bugs in newest Google Chrome, do you think it could be connected to just my device then? If so why would that be a case?
I just successfully reproduced both of the bugs in newest Google Chrome, do you think it could be connected to just my device then? If so why would that be a case?
i imagine there's some combination of software factors (site data, HTTP cache, other tabs, extensions) that triggers it. anything you can eliminate would help. a few others have experienced it as well.