A couple issues with the 'Profile' option have now been resolved.
The first issue was that this feature would crash on some platforms (notably windows) upon attempting to read the profile report html file. This has been resolved by explicitly setting the encoding to "utf-8".
A second issue was that if a profile report had already been generated, the new tab would sometimes just sit and spin. I'm not entirely sure why, but I've fixed this by having it immediately redirect to `/node/view-profile-report/{data_id}/` if a profile report already exists