Alexander Prinzhorn

Should be fixed with the next npm release https://github.com/npm/config/pull/25

The fix landed in npm v8.2.0 (2021-12-02), seven days ago. Are you still experiencing the issue?

> stopped it after few minutes: Which makes the logs you've posted not helpful from what I can tell. They literally tell us that you've interrupted the process via SIGINT...

> I'm also having the same issue I don't think so > │ cc: fatal error: Killed signal terminated program cc1 You are probably running out of memory, Google "...

Did you clear your `node_modules` and try again? https://github.com/JoshuaWise/better-sqlite3/issues/500

@JoshuaWise your pinned repositories no longer include better-sqlite3, I assume because of the move. Didn't know how else to contact you, you probably want that up there :+1: 

> that shows a clear memory leak. > still got the same result. Can you clarify how you detected said leak? What is the result you get? I don't see...

You can also look into `db.pragma('shrink_memory');` and other ways to control the memory SQLite uses. I'm not saying there can't be a memory leak, but there is a difference between...

> on Windows with Electron Is it different from running Node.js directly? That would be interesting to see, since Electron does some funny things. If it repros in Node.js it...

I am using better-sqlite3 in an Electron worker thread as well, so I'm interested in figuring out what is happening here. Can you provide full steps to reproduce please? I...