| Commit-Queue | +1 |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Code-Review | +1 |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Commit-Queue | +2 |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
[heap] Do not recompute limits in NotifyLoadingEnded
We recently started resetting limits on incremental marking start
to avoid finalizing incremental marking prematurely in some scenarios.
For loading we had a similar issue, in order to fix this we
recompute limits in NotifyLoadingEnded(). But resetting allocation
limits on incremental marking start also incidentally addresses the
issue Omer discovered with loading. So in this CL we simply stop
updating allocation limits at all in NotifyLoadingEnded().
Initially I wasn't sure whether a change like this should go through
finch. But according to Omer recomputing the limit on
NotifyLoadingEnded did not have impact, so going back to baseline
should not regress anything either.
In addition this CL also starts resetting allocation limits
unconditionally on incremental marking start. Previously we only
did this when the loading phase was entered but not exited yet.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |