extensionHostWorker.esm.js net::ERR_ABORTED 404 (Not Found)

Hello,

I am experiencing a critical issue where one of my Cloud Workspace freezes my entire local computer indefinitely, until I reset or close the IDX upon opening, or close the preview immediately after opening. It makes investigating and troubleshoot near impossible it’s very unusable.

Here is a breakdown of the situation:Project-Specific PC Freeze & 404 Errors:
The severe performance issue is specific to my “CoinAI” workspace. The freeze appears to be directly caused by the IDX failing to load its core components, resulting in critical 404 (file not found) errors for extensionHostWorker.esm.js and editorSimpleWorker.esm.js. The 404 error is stuck in an infinite loop.

Troubleshooted

Restart VM Workspace
Duplicate Workspace
Disabled all extensions
Attempting to reconfigure the environment via dev.nix, but the schema in my environment does not support hardware changes.

Any efforts to assist in resolving the 404 Errors: extensionHostWorker.esm.js and editorSimpleWorker.esm.js would be greatly appreciated, there is not much online on these errors and most suggest its on the backend side and cannot be done within IDX.

I’ve attached some console logs

9000-idx-asset-insight-viewgit-XXXXXXX.cluster-sumfw3zmzzhzkx4mpvz3ogth4y.cloudworkstations.dev/www/404.html:1 Failed to load resource: the server responded with a status of 404 ()
404.html:1 Failed to load resource: the server responded with a status of 404 ()

msg:9 GET https://idx-asset-insight-viewgit-XXXXXXXX.cluster-sumfw3zmzzhzkx4mpvz3ogth4y.cloudworkstations.dev/cde-d297be3909dda4d1c38806bd974b32180bdd3efd/static/out/vs/workbench/api/worker/extensionHostWorker.esm.js net::ERR_ABORTED 404 (Not Found)

msg:10 GET https://idx-asset-insight-viewgit-XXXXXXXX.cluster-sumfw3zmzzhzkx4mpvz3ogth4y.cloudworkstations.dev/cde-d297be3909dda4d1c38806bd974b32180bdd3efd/static/out/vs/editor/common/services/editorSimpleWorker.esm.js net::ERR_ABORTED 404 (Not Found)

I am having a problem loading the same two files in the same relative location. I did look for the files using the terminal and they simply are not there, thus the 404 error. I am looking at placing the missing files in the appropriate location. If I succeed, I will let you know.

I was able to download the troublesome two files by creating a temp storage location, building the target locations as displayed in the 404 error messages in the console, and then moving the files to the newly created path locations. I now have zero errors when loading up the environment.