Eating memory while reloading profile after having signed Mastodon proof

After signing proof of a mastodon account using the GUI on Linux, while reloading my profile for the proof the keybase process started to use 5GB RAM and swapping, didn't stop, had to kill it.

my log id: 997b048becf8e319dc88521c

Start by examining log ID 997b048becf8e319dc88521c and reproducing the Linux GUI flow: sign a Mastodon proof, then reload the profile. Trace the profile reload until the memory growth is explained; done means the process no longer grows to gigabytes or swaps indefinitely.

Written by the indexing model from the issue text.