Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

'Extension host terminated unexpectedly' - Argdown #1312

Closed
1 of 6 tasks
cybermails opened this issue Sep 8, 2021 · 6 comments
Closed
1 of 6 tasks

'Extension host terminated unexpectedly' - Argdown #1312

cybermails opened this issue Sep 8, 2021 · 6 comments
Assignees
Labels
area.misc status.info-needed More information is needed from filer for issue to be actionable type.bug Something isn't working

Comments

@cybermails
Copy link

Please select the area your Bug applys to. (Multiple selections are Possible)

  • Onboard. Initial vault setup and import/export pods
  • Create. Note creation, lookup, snippets and templates
  • Retrieve. Backlinks, references, graph view
  • Structure. Refactoring, multi-vault and schemas
  • Publish. Sharing your repo with the world
  • Misc (Choose this if your not sure)

Describe the bug

Getting 'Extension host terminated unexpectedly' error upon starting Dendron in VSCode no matter how many times I reloaded/restarted and rebooted my computer.

To Reproduce

Steps to reproduce the behavior:

  1. Have the Argdown extension already installed.
  2. Open Dendron in VSCode and either open the Calendar or the Dendron Preview V2.

Expected behavior

'Extension host terminated unexpectedly' error appears.

Desktop (please complete the following information)

  • OS: MS Windows 10
  • Browser: Chrome

Additional context

After uninstalling Argdown extension, the problem was resolved.

@kevinslin
Copy link
Member

Thanks for the issue. We'll be investigating this separately when we have some more bandwidth 😅

@lnicola
Copy link
Contributor

lnicola commented Dec 4, 2021

I'm also seeing this. It appears to run out of memory:

image

Note that it's happening outside of Dendron workspaces (CC #1540).

@SeriousBug SeriousBug self-assigned this Dec 6, 2021
@lnicola
Copy link
Contributor

lnicola commented Dec 7, 2021

This might be a pre-existing issue, but it got worse recently and disabling dendron.watchForNativeWorkspace seems to fix it for me.

SeriousBug added a commit that referenced this issue Dec 16, 2021
…umber of files

When there's a lot of files in non-Dendron workspaces, the native workspace creation watcher would cause Dendron to crash.
This PR disables the watcher by default, and instead simply reloads the workspace when a native workspace is created.

#1312
SeriousBug added a commit that referenced this issue Dec 16, 2021
…umber of files

When there's a lot of files in non-Dendron workspaces, the native workspace creation watcher would cause Dendron to crash.
This PR disables the watcher by default, and instead simply reloads the workspace when a native workspace is created.

#1312
kevinslin pushed a commit that referenced this issue Dec 18, 2021
…s a large number of files (#1913)

When there's a lot of files in non-Dendron workspaces, the native workspace creation watcher would cause Dendron to crash.
This PR disables the watcher by default, and instead simply reloads the workspace when a native workspace is created.

#1312
@SeriousBug
Copy link
Contributor

Dendron 0.74 disables dendron.watchForNativeWorkspace by default now, and this crash should not occur anymore. If it continues to happen, please let us know. Otherwise this issue will close automatically in a few days.

@SeriousBug SeriousBug added the status.info-needed More information is needed from filer for issue to be actionable label Dec 21, 2021
@lnicola
Copy link
Contributor

lnicola commented Dec 22, 2021

People might still enable that preference, shouldn't this be kept open for tracking as long as it exists?

@no-response
Copy link

no-response bot commented Dec 24, 2021

This issue has been automatically closed because there has been no response to our request for more information from the original author. We don't have enough information to take action. Please reopen if the question from the maintainer has been answered and the issue is still valid.

@no-response no-response bot closed this as completed Dec 24, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area.misc status.info-needed More information is needed from filer for issue to be actionable type.bug Something isn't working
Projects
None yet
Development

No branches or pull requests

5 participants