Yesterday I got a notification in dashboard that i can migrate to the new platform. I have accepted that invitation and faced some minor bugs and I have submitted them via Feedback button:
Automatic lesson completion doesn’t work for me.
When Lab is finished it can’t be marked as complete and lab starts again and again. I was recording a video on this via Feedback button but I think it was not submitted because page got refreshed
Sudden logout from account. I was watching a lesson about Git in DevOps prerequisite course and I was logged out from account.
Hi.
For a few weeks now, I’ve noticed an overconsumption of resources on pages with videos (vimeo) and lab pages. There’s a high CPU consumption and use of Heap Memory and therefore the garbage collector. Maybe it’s related with the issue. In any case, it’s not normal. There must be a loop in the code that quickly generates useless objects. This disrupts the proper functioning of the site and harms the performance of the device. Has anyone else noticed this problem besides me?
Hi,
I’m able to access the labs. the labs are not functioning as it keep looping and not initializing the lab instance. I faced this in kubernetes-troubleshooting-for-application-developers
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.
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.
