By now, there is no deocument discusses the queue mechanism of richfaces, it maybe a weak design in asynchronize. Perhaps, we can use the global queue component to debug this issue and find the point occurs the crach during the request period.
Addition to the code, I think the below code should be improved to check the element. If necessary, please indicate where the code from.
throw new Error("jsf.request: source must be object or string")
Others ,do you know this kind of queue issue and if it's really a bug, does richfaces4.2.x have fixed this issue?
I just changed packed.js by myself, like below, I don't know is richfaces now fixed it?
N.debug("richfaces.queue: will submit request NOW");
//modify by zhifu for "element is null" bug on 09 May, 2012
+ if(T.source && document.getElementById(T.source))
+ T = null;