4 ms·
I am not getting this behaviour in Firefox 120. Tried it, logged out as well. > setTimeout(function() { c(); a.resolve(1) }, 5E3); The code looks like a silly
by bad_user 3y ago
I am not getting this behaviour in Firefox 120. Tried it, logged out as well.
> setTimeout(function() { c(); a.resolve(1) }, 5E3);
The code looks like a silly concurrency bug fix, i.e., a lazy way to force ordering.
- gwd 3y agoOr potentially a concurrency bug trigger? "One in 1000 times X takes a bit too long and causes problem Y; I'll make X take minimum 5 seconds so I can trigger Y reliably." Then fixes Y but forgets to remove the delay.
- seydor 3y agoI can't believe billion dollar companies 'solve' bugs the same way as i do
- _fizz_buzz_ 3y agoThe people working there are also just people like you.
- mewpmewp2 3y agoThey just practice leetcode a lot, doesn't mean they know how to deal with those issues in the UI.
- petargyurov 3y agoA 5 SECOND timeout for a concurrency issue? I doubt it.
- eli 3y agoIt's timeout that's part of loading ads. That code isn't blocking anything. The headline here is wrong.
- lifthrasiir 3y agoSuch fix won't sleep for 5000 ms though. In my reading it looks like a part of the adblocker detection code. (EDIT: Relocated the actual analysis to https://news.ycombinator.com/item?id=38346602 https://news.ycombinator.com/item?id=38346602 for more visibility.)