It is apparent from bug 1139831 and bug 1141370 that there is a race in nsHttpTransaction. Under certain conditions it seems that the *start timestamp is set, but not the *end timestamp. It is possible to mitigate the issue for resource timing, but we should still fix the underlying problem.
Closing in favor of bug 1213699. It's the last racy timings bug left.