my guess is if no favicon is specified browsers request for the default favicon path after page load (possibly) in a non render thread. that's definitely an iss

my guess is if no favicon is specified browsers request for the default favicon path after page load (possibly) in a non render thread. that's definitely an issue, right? also, interesting discussion from wayback: https://bugzilla.mozilla.org/show_bug.cgi?id=260500 https://bugzilla.mozilla.org/show_bug.cgi?id=260500