https://codereview.chromium.org/1269583002/diff/1/src/heap/gc-idle-time-handler.cc
File src/heap/gc-idle-time-handler.cc (right):
https://codereview.chromium.org/1269583002/diff/1/src/heap/gc-idle-time-handler.cc#newcode205
src/heap/gc-idle-time-handler.cc:205:
idle_times_which_made_no_progress_++;
On 2015/07/29 18:21:30, ulan wrote:
On 2015/07/29 18:11:04, rmcilroy (OOO until 10th Aug) wrote:
> Could this cause wrapping of idle_times_which_made_no_progress_?
Maybe clap
> idle_times_which_made_no_progress_ to be less than or equal to
> kMaxNoProgressIdleTimes?
Thanks, rewrote to clap the counter.
Interval between background idle notifications is at least 1 second,
so wrapping
can happen in 60 years. :)
Better safe than sorry ;). Thanks.
https://codereview.chromium.org/1269583002/
--
--
v8-dev mailing list
v8-dev@googlegroups.com
http://groups.google.com/group/v8-dev
---
You received this message because you are subscribed to the Google Groups "v8-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to v8-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
