Subject: Crash/Instability Report - Multiple Errors in Logs

Bug Reports
1

I’ve been experiencing crashes and instability with Cursor recently. I followed the steps to check the logs and found several potential issues that might be related.

Here’s a summary of the errors I observed:

  1. Repeated TypeError: path must not be empty in exthost.log: This error appears multiple times and seems related to file system operations, possibly involving ignore rules or file watching. Example snippet:

    TypeError: path must not be empty
    at lus (…/workbench.desktop.main.js:103:8458)
    at E$ (…/workbench.desktop.main.js:103:8589)
    at cus._test (…/workbench.desktop.main.js:103:9543)
    …

Network Error [aborted] socket hang up in renderer.log: This occurred during network calls, specifically mentioning getTeams and refreshMembershipType. Example snippet:

[error] [aborted] socket hang up: ConnectError: [aborted] socket hang up
    at t (.../workbench.desktop.main.js:2510:204519)
    at async Object.getTeams (.../workbench.desktop.main.js:97:15148)
    at async fst.getTeams (.../workbench.desktop.main.js:97:156814)
    ... [aborted] socket hang up

  1. Extension Host Unresponsiveness: The renderer.log showed messages like Extension host (…) is unresponsive, although it sometimes recovered.

  2. Terminal (ptyHost) Issues: The main.log contained multiple warnings like No ptyHost heartbeat after 6 seconds.

  3. Missing Bundled Extensions: The renderer.log reported errors that some bundled Anysphere remote extensions (anysphere.remote-ssh, anysphere.remote-wsl, etc.) were not found.

These issues, particularly the TypeError and the network error, seem like strong candidates for the cause of the instability.

Could you please take a look? I’m happy to provide more complete log files if needed.

Thanks for your help!

1 Like