Name: Anonymous 2009-06-30 3:02
no tl;dr here, if ur a programmer then you know how to fucking read you jackass.
i don't know much about this problem except that i've only ever seen it in MSIE and Firefox on Windows systems. i've never seen it on any unix-like or posix systems. and i've never programmed anything using winapi or any windows framework so i know nothing of them.
basically, always when firefox goes to resolve a dead hostname, it completely locks up, the interface becomes white if i try to do stuff at the same time and i have to wait for what i assume is a dns lookup timeout period before i can even USE the browser again.
why is it doing this? is windows so single threaded that it can't even run a dns resolution in a seperate thread?
i've always wondered about this but never asked anyone online about it and i can't find anything about it on google either. but it is kinda hard searching for something like that.
it's not an issue i care about because i only use windows at work but it has always interested me because it seems to be a huge limitation in either windows or in these browsers.
for example, right now a web hosting service i use for some websites is moving locations and the name servers are down for a while. i used to work at the very same company a few years back so i know a lot about their name servers. regular bind, freebsd. i even helped set them up and made the control panel for their interface.
if i try to visit one of the pages they host now, firefox completely locks up for 30-50 seconds before i can use it again.
and this is of course not the first time, sometimes when my customers give me e-mail addresses and i'm not sure if i heard them right i go to look it up, easiest way at work is in firefox. if i heard the wrong domain, firefox locks up for half a minut almost before i can use it again.
i've asked around at work and several people have noticed this behaviour but i'm the only one who never uses windows privately so i guess i'm not used to it.
i don't know much about this problem except that i've only ever seen it in MSIE and Firefox on Windows systems. i've never seen it on any unix-like or posix systems. and i've never programmed anything using winapi or any windows framework so i know nothing of them.
basically, always when firefox goes to resolve a dead hostname, it completely locks up, the interface becomes white if i try to do stuff at the same time and i have to wait for what i assume is a dns lookup timeout period before i can even USE the browser again.
why is it doing this? is windows so single threaded that it can't even run a dns resolution in a seperate thread?
i've always wondered about this but never asked anyone online about it and i can't find anything about it on google either. but it is kinda hard searching for something like that.
it's not an issue i care about because i only use windows at work but it has always interested me because it seems to be a huge limitation in either windows or in these browsers.
for example, right now a web hosting service i use for some websites is moving locations and the name servers are down for a while. i used to work at the very same company a few years back so i know a lot about their name servers. regular bind, freebsd. i even helped set them up and made the control panel for their interface.
if i try to visit one of the pages they host now, firefox completely locks up for 30-50 seconds before i can use it again.
and this is of course not the first time, sometimes when my customers give me e-mail addresses and i'm not sure if i heard them right i go to look it up, easiest way at work is in firefox. if i heard the wrong domain, firefox locks up for half a minut almost before i can use it again.
i've asked around at work and several people have noticed this behaviour but i'm the only one who never uses windows privately so i guess i'm not used to it.