One question, certainly tricky case here...
red_zones_.Reset();Why not clear them anymore here?
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
This looks like it was just wrong, previously and I'm a bit confused why it didn't trigger in Chrome. It's deleting the red zone after mapping the builtins, which would seem to allow allocation in that area. There is a release-mode assert that InstructionStream objects are not allocated in the area that aliases the read-only space (in Factory::CodeBuilder::AllocateUninitializedInstructionStream) and my understanding was that Chromium runs with contiguous read-only space.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
This looks like it was just wrong, previously and I'm a bit confused why it didn't trigger in Chrome. It's deleting the red zone after mapping the builtins, which would seem to allow allocation in that area. There is a release-mode assert that InstructionStream objects are not allocated in the area that aliases the read-only space (in Factory::CodeBuilder::AllocateUninitializedInstructionStream) and my understanding was that Chromium runs with contiguous read-only space.
The red zone object maps in reservations and manages those. Clearing them here means that these reservations are lost and can never be reused. This prevents reusing the memory areas for any subsequent allocations. I think this was working as intended, no?
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |