Closed kchodorow closed 12 years ago
This has been handled, although I didn't try to force JavaScript garbage collection to run. I couldn't find a clean way to do that, and I'm not sure it's necessary for us to force it. Kaushal is running logl on a ~2000 frame set of logs, and the batch sending has seemed to make it scroll much more smoothly, and isn't causing any errors.
Great. I don't think you should have to manually call garbage collection. As long as the stuff's going out of scope, it should be cleaned up automatically.
For freakin huge log files, chrome can't handle getting all events at once.