(In reply to comment #11)
> is it possible that i comes from the dns request? (maybe you can do that in the
> background???)
No, this is not a DNS request handling problem (though we still have a bit of
those elsewhere). This hang occurs after the connection is established but
before the page is properly rendered.
I have a suspision the "hang" occures if the internet connection is under
high-load (e.g. router out of connection space or bandwidth is full). Then the
rendering engine (gecko) hangs the whole application until new data is recieved.
I am not quite sure how to test that conclusivly though...
In any case: each Tag should run under its own thread/task so that the entire
application does not hang because one tag/window is hanging.
Cheers...
PS: Please remember to "Vote" for this bug to insure it gets fixed sometime!
(In reply to comment #11)
> is it possible that i comes from the dns request? (maybe you can do that in the
> background???)
No, this is not a DNS request handling problem (though we still have a bit of
those elsewhere). This hang occurs after the connection is established but
before the page is properly rendered.
I have a suspision the "hang" occures if the internet connection is under
high-load (e.g. router out of connection space or bandwidth is full). Then the
rendering engine (gecko) hangs the whole application until new data is recieved.
I am not quite sure how to test that conclusivly though...
In any case: each Tag should run under its own thread/task so that the entire
application does not hang because one tag/window is hanging.
Cheers...
PS: Please remember to "Vote" for this bug to insure it gets fixed sometime!