question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. ItĀ collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

VSCode Prisma extension host crashing and interfering with editor usage

See original GitHub issue

Bug description

After a while of using VSCode with the Prisma extension enabled, VSCode will get sluggish and other extensions will crash. The VSCode developer console is filled with warnings saying ā€œUNRESPONSIVE extension host ā€˜Prisma.prismaā€™ā€ is taking large amounts of time. I have included a screenshot.

Dev tools screenshot

How to reproduce

I’m honestly not entirely sure how to reproduce this. I will be using VSCode normally for a while without issue until things start acting strange. The first thing I usually notice is TypeScript intellisense stops working, infinitely showing ā€œLoadingā€¦ā€ on any hover or Ctrl+Space. When this happens, I check the developer console and sure enough, Prisma extension is unresponsive.

I can provide additional information if necessary.

Expected behavior

Normal extension usage without interfering with editor usage.

Environment & setup

  • OS: Windows
  • Editor: VSCode
  • Editor version: 1.56.2
  • Extension version: 2.23.0

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Reactions:8
  • Comments:31 (12 by maintainers)

github_iconTop GitHub Comments

4reactions
alexdimacommented, Jun 29, 2021

@janpio I would have not thought so myself, but file watching is apparently a very difficult problem.

Could you please try using vscode’s built-in file watcher? On Windows we are shipping a separate .exe that is written in C# and does file watching to isolate the high CPU usage. On other platforms we also depend on chokidar, but we still execute it on a separate process so we are isolated from crashes.

2reactions
Jolg42commented, Sep 28, 2022

The fix is now in the latest 4.4.0 version on the marketplace https://marketplace.visualstudio.com/items?itemName=Prisma.prisma šŸŽŠ

For those who disabled the File Watcher functionality, you can enable it again.

Read more comments on GitHub >

github_iconTop Results From Across the Web

How do I determine which VS Code extension is causing a ...
I'm using VS Code in a fairly large repo and my extension host keeps crashing. When I run the editor with extensions disabled...
Read more >
Improving the Prisma VS Code Extension with WebAssembly
Learn about the Prisma schema and how we improved reliability and simplified the Prisma Visual Studio Extension with Rust and WebAssembly.
Read more >
Available CRAN Packages By Date of Publication
2022-12-22, easySdcTable, Easy Interface to the Statistical Disclosure Control Package 'sdcTable' Extended with Own Implementation of 'GaussSuppression'.
Read more >
CVE - Search Results - MITRE
The mission of the CVEĀ® Program is to identify, define, and catalog publicly disclosed cybersecurity vulnerabilities.
Read more >
Read more - Aaron Powell
nIf you want to verify this, open the your file editor extension (VS Code or File ... as hosting a GraphQL server, which...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found