mirror of
https://github.com/mozilla/gecko-dev.git
synced 2024-10-16 23:05:42 +00:00
47a8d9cfd8
I noticed a bug where the following can happen. The parent sends a TrackCookiesLoad message followed by an HTTP OnStartRequest message. When these messages are received in the child, the TrackCookiesLoad message goes in the SystemGroup event queue and the OnStartRequest message goes in the event queue for the relevant tab. Unfortunately, this means that the OnStartRequest message could run first since the queues have no guaranteed ordering. We really should be putting the TrackCookiesLoad message in the same queue that the OnStartRequest message goes in. I worked on that a little bit, but it's hard to get right. For now, I would like to leave the cookie message unlabeled. Any unlabeled message/event is totally ordered with respect to all other messages/events, so this fixes the bug. MozReview-Commit-ID: KiLDAhlrbB8 |
||
---|---|---|
.. | ||
base | ||
build | ||
cache | ||
cache2 | ||
cookie | ||
dns | ||
ipc | ||
locales | ||
mime | ||
protocol | ||
sctp | ||
socket | ||
srtp | ||
streamconv | ||
system | ||
test | ||
wifi | ||
moz.build | ||
necko-config.h.in |