I wanted to report two separate issues I experienced while using the Wootility Web app in Chrome, which both appeared consistent with memory leak–like behavior. Sharing in case this is useful for investigation.
-
Memory leak without Valorant running
While using the Wootility website in Chrome (no games running), Chrome gradually became unresponsive and eventually stopped responding entirely. The UI froze and required the browser/tab to be force closed, which looked like progressive memory or resource exhaustion rather than an immediate crash. -
Suspected memory leak when launching Valorant
In a separate incident, I had the Wootility website open in Chrome while attempting to launch Valorant. During the Valorant boot process, the system froze, and I had to turn off my PC and turn it back on again to recover.
Since switching to the Wootility Desktop app, I have not encountered any further issues. I also make sure the app is closed while playing games, and Valorant now launches and runs normally.
Just wanted to flag this in case it’s helpful. Happy to provide more details if needed.