npub1uz…kfree on Nostr: These are some images of debugger/profilter data from iris.to while I just have it ...

These are some images of debugger/profilter data from iris.to while I just have it sitting on the main page, doing nothing.First is a memory graph. It looks almost exactly like the memory graph of a pleroma frontend except for that huge chunk of just "strings" at the end. What the fuck is it doing with 128 megabytes of strings?Second is a call tree, sorted by the amount of time spent inside of each function. Almost 98% of its time is spent in a recurring (setInterval) operation that only does these aforementioned mathematical operations. In service of displaying a page and periodically checking in the background for notifications/updates?It also pins the CPU at 100% the entire time you have the page open.Does this look to anyone else like they're mining crypto on the client side? What else should I look for to figure it out?