atom won't open files or settings anymore, the github module broke it

[mh-cbon]

Prerequisites

• Put an X between the brackets on this line if you have done all of the following:
  • Reproduced the problem in Safe Mode: https://flight-manual.atom.io/hacking-atom/sections/debugging/#using-safe-mode
  • Followed all applicable steps in the debugging guide: https://flight-manual.atom.io/hacking-atom/sections/debugging/
  • Checked the FAQs on the message board for common solutions: https://discuss.atom.io/c/faq
  • Checked that your issue isn't already filed: https://github.com/issues?utf8=✓&q=is%3Aissue+user%3Aatom
  • Checked that there is not already an Atom package that provides the described functionality: https://atom.io/packages

Description

the Atom IDE stopped working suddenly. The symptoms were:

• not being able to open file anymore from the treeview
• not being able to save my files
• not being able to open settings pane

Steps to Reproduce

Start atom, then it randomly freezes
after a ctrl+s,
or after opening a few files,
or without any action at all

The problem did not start today, it was there before but was not so painful.
I used to restart the ide and continue my work,
but today nothing worked and it bugged 100% of time.

I was working on this repo https://github.com/etcd-io/bbolt when things became totally out of control.

Versions

$ atom --version
Atom : 1.39.1
Electron: 3.1.10
Chrome : 66.0.3359.181
Node : 10.2.0

$ apm --version
apm 2.2.4
npm 6.2.0
node 8.9.3 x64
atom 1.39.1
python 2.7.16
git 2.21.0

$ lsb_release -a
LSB Version: :core-4.1-amd64:core-4.1-noarch
Distributor ID: Fedora
Description: Fedora release 30 (Thirty)
Release: 30
Codename: Thirty

Additional Information

I re installed atom, deleted .atom folder, updated to the beta, downgraded.... ran in foreground , dev, safe, gpu disabled, cleared window state, all sorts of things recommended in the project manual.

The only things that got it fixed was to disable the github module. It happened i disabled that one purely out of luck.
I really don't know why / how this has happened, i did not find how to properly debug the program either.

The only thing i noticed, running foreground, and fixed without any luck was

[2019-08-05 16:33:35.360] [ERROR] code-highlight - Error getting code highlights { TypeError: result.sameids is not iterable
    at HighlightProvider.highlight (~/.atom/packages/go-plus/lib/highlight/highlight-provider.js:71:28) rawStack: [ CallSite {} ] }

I also noticed this, but have not tried to figure it out,

Attempting to call a function in a renderer window that has been closed or released.
Function provided here: worker.js:79:22
Remote event names: destroyed, crashed

Showing up the console and the dev tools did not help, it even was misleading in my case.

I post because this was really annoying, no previous issues helped to solve it, i also spent time evaluating alternatives ide, I was two fingers away to switch to vscode only to get back to work.
All of this for a module i don t even remember manually installing...... i only hope it helps other people if they are stuck with this issue.

Lastly, i know the very last thing i should have done was to enable/disable each module one by one until i can find the problem. But TBH doing that by hand is a no-go, there is just too many modules by default. if there were some ways to script that it could be helpful in the future to detect problematic modules.

Atom is really a great IDE, that is (really^10000) unfortunate it fails so badly with such cryptic behaviors.

[rsese]

Sorry for the trouble here - I wonder if you're running into a similar issue as described in #2019 (comment) and #2166 (comment)?

[mh-cbon]

hey, thanks for handling my report. Sorry if i did hurt anyone.

To summarize, if i m reading correctly the reports you mentioned,
after I re enable the github module,
then i should be able to work on repository without remote branch ?
In contrary if i open a package having a remote branch it should break again ?

i tried for 5 min with the github module re enabled, it worked well on the bolt repo with remote branches to github (... disappointing non reproducible bug).
It was rather early in the morning (before regular office work hours), so if this is network issue, could it be a congestion issue that occurs only under certain circumstances ? (in such case its unclear to me if this is a github, vpn or isp struggle)

Quickly going through the provided reports, few things i can add, if that helps anyhow

$ git remote -v
origin	https://github.com/etcd-io/bbolt (fetch)
origin	https://github.com/etcd-io/bbolt (push)

How did you install Atom? => rpm (distro rpm (1.39) and atom website rpm (1.40-beta) )
Did you reproduce in safe mode?=>yes
Do you see any errors in devtools console=> yes but not it is relevant i believe

• an exception is thrown from go-plus here https://github.com/joefitzgerald/go-plus/blob/master/lib/test/tester.js#L429
• a warning [DEP0079] DeprecationWarning: Custom inspection function on Objects via .inspect() is deprecated at internal/process/warning.js:18 (node:3361)

Have you reproduced with multiple projects? => yes, they had remote branch too

Is this behavior new for you as of 1.37.0? => idk

Are these remotes pointing to github.com repos or somewhere else? => github, i don t have other remote host as of now.

Are the projects you're working on local to your machine or on some kind of network drive? => local

$ cat ~/.atom/github.cson
# Store non-visible GitHub package state.

I did not see this message, or anything similar to
Gtk-Message: 21:46:18.705: GtkDialog mapped without a transient parent. This is discouraged.

fyi, i configured an ssh key in my github account.

I will wait few hours and try to reproduce.

[m1ga]

@mh-cbon found this issue here and I'm in the same boat as you. Wrote a question in the discuss section https://discuss.atom.io/t/unable-to-open-or-save-files/68842

Using Fedora 30 too

Atom : 1.40.0
Electron: 3.1.10
Chrome : 66.0.3359.181
Node : 10.2.0
Fedora Linux 5.2.17-200.fc30.x86_64

Following this issue now and hope there will be a solution besides disabling the package 😄

[jowrjowr]

This is definitely still an issue. I'm able to reproduce it with my current system state on a repo with an active merge going on.

Even with a deleted ~/.atom and a ~/.config/Atom!

[jowrjowr]

Interestingly this went away with a system update + reboot. That did not touch the Atom version, which was happening even with latest.

[jowrjowr]

So, this happened again and a reboot cleared it. I did not specifically update any drivers or anything but I'm starting to think this has something to do with the graphics subsystem somehow.

[circl-lastname]

Bump. This is happening to me