This bug is not resolved since 2004 year.
People stop chatting here and make it ALL OVER AGAIN FROM SCRATCH.
Apparently the source is a complete mess.
My proposal is to have a one thread tho handle DNS responses, and if there is proxy set then a second thread will be started to resolve the DNS through the proxy.
So the thread must work by sending the DNS request on 52 UDP/TCP ports as it is done is millions of software.
Then the thread waits for response. And the corresponding TAB in the Firefox is waiting for that response, ALL OTHER TABS ARE WORKING JUST FINE - so we can use them as nothing happend.
When the thread(s) receive a response from the DNS server they send a EVENT to the corresponding TAB with the responded information - i.e. the IP of the web server.
That is all.
There is no other matter to discuss.
There is a way to be done in the current Firefox - after all 2004 year is 7 (SEVEN) years old BUG.
Came on get in hands.
This bug is not resolved since 2004 year.
People stop chatting here and make it ALL OVER AGAIN FROM SCRATCH.
Apparently the source is a complete mess.
My proposal is to have a one thread tho handle DNS responses, and if there is proxy set then a second thread will be started to resolve the DNS through the proxy.
So the thread must work by sending the DNS request on 52 UDP/TCP ports as it is done is millions of software.
Then the thread waits for response. And the corresponding TAB in the Firefox is waiting for that response, ALL OTHER TABS ARE WORKING JUST FINE - so we can use them as nothing happend.
When the thread(s) receive a response from the DNS server they send a EVENT to the corresponding TAB with the responded information - i.e. the IP of the web server.
That is all.
There is no other matter to discuss.
There is a way to be done in the current Firefox - after all 2004 year is 7 (SEVEN) years old BUG.
Came on get in hands.