Here the error is spot on – you need to clear your cache for the kodekloud.com domains, because there’s something in your cache that’s too large. Do that and this error will go away.
Thank you so much. Its solved and working fine.
This is consistent with what several of us have recently seen on KodeKloud. Because the lab UI and playgrounds rely heavily on client-side state, strange failures such as questions not loading, laboratories that are stuck initializing, and random timeouts occur once the cache or indexeddb/localstorage becomes bloated.
Cleaning the cache just for kodekloud.com (as opposed to a whole browser nuke) typically resolves the issue right away. An incognito test is a simple sanity check since I’ve also seen service professionals get stuck. It is mostly usually stale cache + service worker trash if it functions there.
For those who see significant CPU and memory use on lab pages, it is probably the same problem. Your browser suffers while the frontend repeatedly tries to sync lab state and cranks the js loop. The loop ends when the cache is cleared.
It’s a browser-side buildup, not a Kubernetes or course problem. Reproducible, but unpleasant. delete the cache, reload, and finish.