Brad Fitzpatrick 191cdf023c
StrictMode: check max-offenses-per-loop earlier, before allocations ...
Previously a tight loop of StrictMode violations would still allocate
Exception objects and populate their stack frames, just to orphan them
later when checking the max-10-violations-per-loop constraint.
With this patch, we do that check _before_ allocating any memory.
Change-Id: Iae96aba33f8fcc6a8ec5838a231aecc08e95122d
2010-10-11 11:31:15 -07:00
2010-02-17 16:46:42 -08:00
2010-08-06 18:55:05 -07:00
2009-12-14 17:52:20 -08:00
2010-10-08 15:34:08 -07:00
2010-06-23 17:44:30 -07:00
2010-10-06 19:23:38 +02:00
2010-10-07 18:48:22 -07:00
2010-10-01 12:54:10 -07:00
2010-01-29 13:29:51 -08:00
2009-03-03 19:31:44 -08:00
2009-03-18 17:39:46 -07:00
2010-02-17 10:04:39 -08:00
2010-10-07 19:41:23 +08:00
2010-10-08 18:23:49 -07:00
2010-09-30 18:27:22 -07:00
2010-10-04 17:56:23 -07:00
2010-10-11 11:31:15 -07:00
2010-10-04 07:59:34 -07:00
2010-09-03 11:18:28 -07:00
2010-09-29 17:34:40 -07:00
2009-03-03 19:31:44 -08:00
2010-09-30 15:43:34 -07:00
2010-09-08 16:32:27 -07:00
2010-07-26 16:11:58 -07:00
2010-02-25 13:46:50 -08:00
2010-09-26 22:20:12 -07:00
2010-10-01 11:01:01 -07:00
2010-10-10 14:45:51 -07:00
2010-10-05 15:22:07 -07:00
2010-10-10 14:01:10 -07:00
2009-03-03 19:31:44 -08:00
191cdf023c