Re: Gecko threads and parsing

[Boris Zbarsky]

Jiri Znamenacek wrote:
Ah, that's sad... I run 1.8a4 now and for some reason this is starting 
get me mad - open new document and wait several seconds till Mozilla is 
again accessible (and processor usage came back from 100% to 0%). 
Strange I can't remeber it was THAT bad before...

Since I'm no C programmer - what it woud take to implement it? Any 
chance for some more proper threading model in future geckos?
The problem is that one window can access the DOM of another window.  And it 
expects to be able to make blocking calls to the other DOM in a reasonable way 
(eg calling window.alert() on some other window).  So either all DOM access 
needs to be threadsafe, with locking and so forth (a performance issue), or we 
need some setup where we put window groups on different threads, or something.

The easier way to do this, I think, is to allow multiple concurrently running 
app instances (i.e. handle this the way IE does).

-Boris
_______________________________________________
mozilla-layout mailing list
[EMAIL PROTECTED]
http://mail.mozilla.org/listinfo/mozilla-layout