-
Notifications
You must be signed in to change notification settings - Fork 251
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
High CPU usage for temporary files #776
Comments
👋 Hey @DallasO, thanks for the detailed report. The spike in CPU usage sounds strange. Granted, How big is the project? If the Also, what system are you running, and what other packages do you have installed/activated? |
👋 System: Linux (Debian 10) Packages, not including the core Atom packages: |
Ah, that reminds me. I've recently witnessed Atom crash a few times after opening a PDF (and having the console open). It just... hang for a long time, and the workspace vanished with an "Atom has crashed." system dialogue. Wondering if there isn't a connection there. 🤔 BTW, |
😆 Haha. OK. I'll keep playing around and see if I can narrow it down. Thanks! |
Hello,
I'm not sure how I can describe this with any debugging from Atom, so let me know if you need anything.
Basically, I have a project using a sqlite DB, and while running a script, sqlite is creating a journal file that pops in and out of existence multiple times every few milliseconds. Having
file-icons
enabled is using +60% cpu and after a few hours of running will crash Atom.As soon as I disable
file-icons
, cpu drops down to 15% usage, which I'll attribute to Atoms tree parser.Not completely sure if its
file-icons
or Atom causing the crashing at that point. I'm testing their other File System Watchers.I'm also not sure if
file-icons
even has an image for a db.sqlite3-journal file, so I wouldn't think the default image would be hitting the disk so hard.Versions
Atom==1.35.0-beta0
file-icons==2.1.30
I am running a first-time script to load a data set into my database, so this isn't a routine task. If that means this isn't an important issue, you can just close this.
The text was updated successfully, but these errors were encountered: