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
Atom Editor freezes occasionally #91
Comments
I'll have to experiment to see if I can reproduce it. It's not something that I have come across in the past. But, I've moved to VS Code so I don't use Atom too often these days. Does it happen frequently? Or just randomly over a long period? |
I experimented VS Code as well, but unfortunately the C++ support (debugging excluded) is still not as good as in Atom, which has so far a decent support of CMake + clang 😞 I noticed this on two setups, the first with Arch Linux (rolling) and the second with Ubuntu 17.04, both with KF5/Plasma. My old setup, running on Ubuntu 16.10 (or 04, don't remember exactly) never had such issues, hence I suppose this is a regression of the most recent X11 releases. If this is the case unfortunately it would take a lot of time to debug, I'd wanted to ask you since you're maintaining this Atom image. It happens every time and right after the container is created. The easier way to trigger it is opening the menu and browsing the items with the cursor. The editor freezes for a couple of seconds (the host system as well) and then the errors I reported are displayed. It keeps happening doing the same operation again, even though other actions can trigger the freezes e.g. opening folders in the tree view. For the sake of clarity I didn't created the container with |
I'm running Fedora 25 with i3. I get the I'll try to replicate your environment and see what happens. |
Good to know that at least you manage to replicate that. My current setup is a Dell AIO with an |
I can't replicate your hardware but I tested in a Kubuntu 17.04 VM. I still see the errors you mentioned earlier in the console output, but there is no freezing. The menus open fine and everything seems to run smoothly. |
Ok so it doesn't happen in a virtualized environment, and I can tell you it doesn't happen either in a regular |
Yes, could be related to |
I 'm also experiencing this behaviour. |
@mitsest can you give some more details about your environment? What window manager do you run, etc. |
Sure! I 'm using unity and here is the lspci output mits@mits:~/nativescript/dev_env (master)*$ lspci | grep -i --color 'vga|3d|2d' 00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09) Also, keep in mind that it does not happen all the time. Thanks! |
On Fedora I have:
I don't experience any problems. Maybe I'll try to build a Ubuntu VM and see if I can reproduce. |
OK, cheers man! Thanks again |
Can you not generate config.cson locally (or in another container) and just add it to your image? |
After some tests on Debian I don't think it's easily reproducible. |
@jamesnetherton I'm trying to debug diegoferigo/dockerfiles#12 and I tested the behavior of your image. I have the same freezes described in the linked issue, but the error generated now is:
Including in the image the packages for HW acceleration (
libgl1-mesa-glx
libgl1-mesa-dri
) the error becomes exactly the same I got:Did you ever notice something similar? It looks like there's something going on between X11 and KF5/Plasma.
The text was updated successfully, but these errors were encountered: