This isn't an answer as much as a proposed temporary workaround. Make the call synchronous with async:false and see if things work again.
This isn't an answer as much as a proposed temporary workaround. Make the call synchronous with async:false and see if things work again. I've been tearing my hair out over a similar-sounding bug recently.
I need to do more testing before I want to put it up on S.O. , but for anyone interested: It happens with jQuery 1.3.2 and Firefox. One common factor seems to be that I am making one AJAX call, and the additional calls are all launched by the on-success method after that. Only the first (parent) AJAX call and the final one of the child-calls appear to ever complete, although FireBug shows them all happening and the server gets them all.It's not a pure race condition, since stepping through it with a debugger still causes the problem.
Making the child-calls synchronous "fixes" it. – Darien May 25 '10 at 23:35 The worst part of this problem is that it is difficult reproduce, it happens every hour or so, but even so I would not want any of these calls to be async as a solution. – Adrian Adkison May 25 '10 at 23:53.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.