We could conceivably apply a band-aid here by clamping `prev` to be non-negative, but perhaps we should do something even more useful for this case. This `mStartTable` stuff is kind-of ancient, added back in bug 867758, and it's not clear to me (without further digging) what the right behavior for it is in this case. tnikkel, could I kick this to you to sort out what the right behavior is for this case where `data->mStartTime` gets emplaced in a nested event loop? (producing a negative `prev` value in the outer event loop)
Bug 1747277 Comment 6 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
We could conceivably apply a band-aid here by clamping `prev` to be non-negative, to avoid the undefined behavior; but perhaps we should do something even more useful for this case. This `mStartTable` stuff is kind-of ancient, added back in bug 867758, and it's not clear to me (without further digging) what the right behavior for it is in this case. tnikkel, could I kick this to you to sort out what the right behavior is for this case where `data->mStartTime` gets emplaced in a nested event loop? (producing a negative `prev` value in the outer event loop)