Consider preserving max-request-id-used-so-far (instead of initializing request id to a random number) |
|
Issue descriptionr559629 made renderer use random initial RequestID (instead of 0). This fixed/avoids [Renderer kill 108] content::ResourceDispatcherHostImpl::BeginRequest (RDH_INVALID_REQUEST_ID) - issue 614281. This bug tracks a follow-up to 1) quit using a random initial RequestID and instead 2) have the browser preserve max-request-id-used-so-far and restore/reuse the max request id when respawning a crashed renderer. |
|
►
Sign in to add a comment |
|
