Hi,
I just updated to 380.64_2 from 380.63_2 and found that when you go to the login page it sends Safari into a loop of CPU munching. Seems to work OK on Chrome.
If (big if) it manages to load it has spat a load of code out on the display per screenshot.
I've done all the obvious reboots of computer/router, always reproducible, the second you go to router.asus.com (or the IP directly) in Safari the CPU fan spools up and the Mac becomes a dog. See screenshot of high CPU usage.
I noticed some changes to httpd in the change log so not sure if they may be the culprit...?
I did this whilst logged into the router via Chrome and it's not seeing any CPU/RAM load, it's all on the client side. Let me know what other debugging info you might want?
Or let me know if you want me to try 64 or 64_1 as well?
Many Thanks!
I just updated to 380.64_2 from 380.63_2 and found that when you go to the login page it sends Safari into a loop of CPU munching. Seems to work OK on Chrome.
If (big if) it manages to load it has spat a load of code out on the display per screenshot.

I've done all the obvious reboots of computer/router, always reproducible, the second you go to router.asus.com (or the IP directly) in Safari the CPU fan spools up and the Mac becomes a dog. See screenshot of high CPU usage.

I noticed some changes to httpd in the change log so not sure if they may be the culprit...?
I did this whilst logged into the router via Chrome and it's not seeing any CPU/RAM load, it's all on the client side. Let me know what other debugging info you might want?
Or let me know if you want me to try 64 or 64_1 as well?
Many Thanks!