FurtadoPires

Did some more tests, and found out that the "Injection Script" (Kaspersky Standard) to be the responsible for this problem @Flood and Flood's wife I did another report in the link you've shared, including the browser inspector logs for comparison. Unless the default configuration are different between users, I can guess that anyone who tries to access sso.crunchyroll . com/login with Injection Script on will mostly being affected by this. About not being able to replicate, the only thing I can think is if the page send a different library depending on the region that the user's accessing. In that case, I would try to test using an address from Brazil (by vpn or asking someone). Other than this, I can't think about anything else that might be different from my access to the support team.

Thank you for answering 1 - May I request this topic to be moved to the correct section? I personally find it a little confusing to where should I open it since I'm not even sure which exactly component is responsible for the problem. 2 - I already gave a feedback following @Berny instructions, and others might have done the same because it's a problem affecting everyone judging by the other topic. My goal opening this topic wasn't to resolve my personal case, since as I've mentioned before I can work around it by exiting Kaspersky before I log in (which isn't the best solution), but to give a feedback about this problem that might been affecting other users that are unaware of the cause. While affecting just a specific page (despite being a popular one) isn't much of a problem, causing browsers to consume too much resources is, so I believe this should either be looked by the support team (maybe contacting Crunchyroll if it's necessary), or if it's really a dangerous component, inform users about it like it does to other pages. Whatever is the case, expecting users to opt-in the solution shouldn't be the best course to follow.

1 - Yes it's exactly the same problem, his print also shows the javascript lib being blocked constantly (causing the memory overflow). 2 - I'm currently using 21.16.6.467 and I suspect this might be a regression from this version, since I don't remember having this problem before the upgrade (but I also use to always being logged in Crunchyroll, so I can't be sure it didn't affected older versions).

Thank you for answering I've checked the page and request a reanalysis of the url https:// c . evidon . com/ dg / dg.js which is the address of the lib being blocked in this case. I've also linked this topic in the analysis, so I hope someone can check it.

I'm creating this topic since I haven't found any information about it. For some time I'm having problems to login in my Crunchyroll account using my Windows 11 machine with Kaspersky Antivirus installed. I've noticed that every time I access the login page, my browser goes unresponsive until I finished it using the task manager. Investigating further, I saw that when I access the page https:// sso.crunchyroll . com/login kaspersky blocks a javascript lib called dg.js, then the page tries to send it again (and blocked again). This behavior generates a loop which make browsers (both chromium based and firefox) to memory overflow to the point where's necessary to finish it by using windows task manager The only workaround I've found is to exit Kaspersky and access the login page (which possibilities the download of the lib) then activate again after login. So it is a case of false positive or there's something wrong about this specific lib? I think this case should be investigate, since causing browsers to memory overflow is problematic and this page is accessed by many users. To reproduce the problem, you only need to access Crunchyroll's login page (it isn't necessary to have an account) and the blocking behavior can be observed by opening the browser's inspector.