Based on the fact that the developer schlawg deleted his account and the problem has not been solved for more than a week, I assume that Lichess has serious problems in the development team.
oh i just deleted my cookies and then it worked again. Maybe its a fix
check blindfold if all pieces have disappeared randomly, it happens a LOT
Dear Lichess Support Team,
I encountered a major issue during a recent bullet game that severely impacted my experience and ultimately affected the outcome of the match. While playing, my opponent's position suddenly became incomplete: only their king was visible on the chessboard, while all their other pieces disappeared. This bug lasted for about 30 seconds, during which I repeatedly refreshed the page in an attempt to fix the problem, but it didn't resolve.
During this time, I made several blunders because I could not see my opponent's full position, which was clearly detrimental to my gameplay. After approximately 30 seconds, the board corrected itself, but by then, I was in a terrible position. Fortunately, the game ended in a draw (stalemate), but I lost -1 rating points due to the situation.
While the rating points lost aren't the primary concern, this bug significantly disrupted my game experience. A bug of this magnitude makes it extremely difficult to enjoy the game, especially in a fast-paced format like bullet.
I have attached a screenshot of the bug for reference. Please investigate this issue to ensure it doesn't affect other players in the future.
Thank you for your attention to this matter.
Best regards,
Emrlhozdmr
Note:
- My ping between 50-120 ms and server 1 ms
- Google Chrome vers 140.0.7339.187 (64 bit)
- Windows 10 Pro
[Photo]
imgur.com/a/dSiScWv
[Game Link]
https://lichess.org/YuMC1PmcWzcT
Did a browser update cause the problem?
Has anyone tried software rendering, instead of hardware rendering?
If a browser no longer fills my needs, I normally try another supported browser.
https://github.com/lichess-org/lila?tab=readme-ov-file#supported-browsers
AI said ...
Network/Server Revalidation: CDN/Server Side Revalidation: Lichess (or its Content Delivery Network) might be configured to always ask the browser to check if the file is current (using an ETag or Last-Modified header), even if it's cached. If your connection is momentarily slow during this check (a 304 "Not Modified" response), the process of displaying the piece can still be delayed.
DNS/Connection Issues: If the initial HTML page fails to fully load the links for the piece images due to a brief connection hiccup, the browser may fail to properly register the images for caching, or subsequent requests for validation (see above) may be blocked.
Browser Bug: Specific Browser Glitches: Occasionally, browsers have specific, documented bugs where the rendering or caching engine fails to operate correctly for certain types of static assets until the page is hard-refreshed or the piece set is changed.
We will deploy a speculative change that could resolve this soon. But assuming it does not, we could use some info.
If you have witnessed this issue, please provide the following information in a short reply to this thread:
- your browser and version (Edge Version 140.0.3485.66 )
- your operating system (Windows 11)
- your desktop or laptop GPU (NVidia Quatro T2000)
I have not noticed this issue again since I posted #47, where by coincidence, I only posted the very last time I noticed. I have made no attempt to clear cache or cookies on any of the browsers/systems I listed, and have not changed any settings or updated them either.
I also have not experienced this issue again since you deployed the speculative change a week ago (no changes on my end).
This topic has been archived and can no longer be replied to.