Hey... I assume you're referring to 0xDB.org. That may be a bug in pan.do/ra (the application), rather than in OxJS itself. We fixed some memory leaks recently, but may have missed some.

If you care to provide a few more details (via e-mail, or using our bug tracker), we're definitely going to look into it.