VSCode Prisma extension host crashing and interfering with editor usage
See original GitHub issueBug 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.

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:
- Created 2 years ago
- Reactions:8
- Comments:31 (12 by maintainers)

Top Related StackOverflow Question
@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
.exethat is written in C# and does file watching to isolate the high CPU usage. On other platforms we also depend onchokidar, but we still execute it on a separate process so we are isolated from crashes.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.