Trying to edit information about a disabled user skyrockets memory usage and triggers the Death of the Universe

[Kistras]

It has been fairly reproduceable for me so far.

Steps I took:

1. Log into account on a separate browser
2. Disable it through the service menu (I assume that's the disabling button based on source code, interface isn't super intuitive :c)
3. Try to edit profile details

As a result databag skyrockets in both memory and cpu usage. Closing browser tabs did not avert this

After about a minute, at which point the entire server froze and I had to reboot it:

[Kistras]

More info

• It seems to be possible to reproduce even by logging into a disabled account, not just disabling it while you're in it
• I used this command to install databag: docker run --name databag -d -p 7000:7000 docker.io/balzack/databag:0.1.18
• Running docker logs doesn't seem to show any errors, only /internal/api_getProfile.go:12 account is inactive