> A test string of about 11,000 bytes brings my 3.2GHz P4 to it's knees,There was an n**2 problem with the regexp. The latest version of
> for longer than I'm prepared to wait (> 5mins).
> After a bit of investigation, the problem seems to rest solely with
> the RegExp check; if this is removed, and the function sublty rejigged
> accordingly, the parse phase executes instantly and the resultant
> object is exactly what I would expect.
json.js should be much happier with large texts.