Bugfix: ProfileExport.JSON - correctly identify frame start when there's 0 or 1 callstack depth at the start of recording This is a standalone-specific issue Tests: built standalone, did a perfsnapshot there