Phil H�hn wrote:Retract my last statement! I backed-up, cleaned up my code and the problem reappeared. So extracted the previous file again and the problem is still there! So the problem - I thought was gone - hasn't, it still seems to be a race condition that is very flakey, and when I thought it was fixed must have just been the PC being nice to me.
Neil wrote:Yes.
Which component are you actually observing?
@mozilla.org/network/urichecker;1
(I think that's what you're asking.)
I may withdraw this question... I was getting some very strange behaviour because the second object was mistakenly altering some data still being referenced by the first object. I cannot understand or explain what was happening, it was a real race condition that was unpredictable, but after fixing, this problem seems to have gone away (or is at least far less obvious at this point).
OK, I just wanted to be sure you weren't trying to use the same uri checker to check two different URIs.
Yes, I'm using a different urichecker in each case (well at least it's within a class of which 2 differences are created).
_______________________________________________
Mozilla-xpcom mailing list
[EMAIL PROTECTED]
http://mail.mozilla.org/listinfo/mozilla-xpcom
