Vscode: File extension cpuprofile not recognized by javascript profiler when filename changed using Mac's finder

[refs]

• VSCode Version: 1.46.0-insider (Commit: e1d8f5155c0db5ffdc130c9aa0f14efac02dfdfb)
• OS Version: MacOS Catalina, 10.15.4

Loading a cpuprofile results on the javascript profiler does not recognize the .cpuprofile extension.

Steps to Reproduce:

1. Follow the instructions in profile the running extensions
2. end up with the following cpuprofile file: CPU-20200514T083510.480Z.cpuprofile.txt
3. Remove the .txt suffix from step 2
4. Load the file on the javascript profiler
5. Can't load file:

Does this issue occur when all extensions are disabled?: Yes

[vscodebot[bot]]

(Experimental duplicate detection)
Thanks for submitting this issue. Please also check if it is already covered by an existing one, like:

• provide profile function for different programming language (#69434)
  

[alexdima]

@refs A .cpuprofile must be loaded in the JavaScript Profile tab:

[refs]

@alexdima that is indeed the sequence of steps I follow:

[alexdima]

@refs Can you please use ls in a terminal to confirm the file extension is .cpuprofile? I have just tried to profile the extensions, which generates a file named CPU....cpuprofile.txt and for whatever reason using the macOS finder to strip the .txt extension does not work. The macOS finder is ignoring my file rename. I have tried in a terminal and that worked well.

[refs]

@alexdima wow... can confirm that renaming it via the cli did solve the issue, as opposite to using the finder app to rename it. The file extension on an ls was .cpuprofile, but using the finder app, even with the .cpuprofile extension, the finder still thinks displays a text file metadata. Only after renaming through the cli it doesn't recognize it as a text file anymore, and loading works.

[alexdima]

• the macOS finder is written by Apple
• the Chrome developer tools are written by Chromium

Please create issues against those projects if you want.