On 2013/08/21 19:44:56, felix8a wrote:
I'd be ok with a more exhaustive scanner that's run separately on
demand. We
could setup a farm of browsers somewhere that run nothing but the
scanner. Up to
1day-ish of scanning per browser seems plausible to me, since that
would mesh ok
with daily build cycles. Under an hour is friendlier, but for what the
scanner
is guarding against, several hours seems ok.
That would be nice to have, but:
1. We would still need to maintain the short list in addition to the
long list.
2. From experience, there's a significant chance that a sufficiently
large scan will hang/crash the browser/tab, or simply run into slowdowns
(i.e. performance is worse than O(n)), and the scan cannot be simply
split across multiple browser runs, because it is traversing a highly
cyclic graph without reliable unique node labels.
(Given the ability to provoke crashes, I've even been giving some
thought to repurposing it for stress testing browsers.)
https://codereview.appspot.com/13024043/
--
---
You received this message because you are subscribed to the Google Groups "Google Caja Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
