Diaa wrote: > I found out what the problem is, it was memory corruption, I should > have known that because usually it's only memory corruption that can > does such sorts of magic, but what's strange is that the application > didn't crash.
Interesting, strange that memory corruption caused that problem... > is nsIRequest::Cancel() synchronous or asynchronous? if it's async, > how to notify the host that I've finished cleaning up? Asynchronous; you need to (asynchronously) call onStartRequest/onStopRequest on your stream listener, if they haven't been called yet. > Which values are allowed to be returned from nsIRequest::GetStatus()? Any valid nsresult. For a channel that loaded successfully it'd be NS_OK, for a cancelled channel generally the value that was passed to cancel, and otherwise a value that depends on the error. nsNetError.h has a list of some error codes, or you can define your own (see NS_GENERATE_FAILURE). -- All the world's a stage, And all the men and women merely players: They have their exits and their entrances; And one man in his time plays many parts, [...] --W. Shakespeare _______________________________________________ dev-tech-network mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-network
