Android Studio: can't edit files after a while

Question

I just installed Android Studio and I have a problem:

after some time of work, I'm not able to edit files anymore, I have to restart the IDE to edit them for a while again.

That's very annoying. Is there a way to solve this? I saw others on google having almost the same problem (mostly on ubuntu), but I wasn't able to find any solution except a temporary one: if I click on the scrollbar of the file I'm able to edit it again, but the problem will be triggered again if I change file or do anything else outside of it; so the actual problem it's the editor not getting the focus by clicking on it.

I'm on Windows 8.1.

http://stackoverflow.com/questions/30407869/android-studio-cant-edit-files — IntelliJ Amiya, Oct 19 '15 at 11:21
yes I already seen those, but seem not entirly my case. android studio it's not on readonly mode and I can open files normally, edit XMLs but not java files I'm on windows 8 — jack_the_beast, Oct 19 '15 at 12:25
Please check that if this is happening after pressing some key combination, like alt+left/right (to change tab) — droidev, Oct 25 '15 at 16:08
@robodev absolutely not. they just lose focus after the IDE stay inactive for some time — jack_the_beast, Oct 25 '15 at 16:11

score 9 · Answer 1 · edited Jun 01 '20 at 13:34

9

Assuming you are using Ubuntu OS.

As given here

The bug seems to be triggered by some missing synchronization between IBus (the server) and Xlib + AWT (the client JVM), exposed by a combination of a quick succession of key presses and the client’s slower event handling. The bug has already been reported upstream:

the bug is already reported here

The 2 workarounds that helped me were :

Workaround #1: Force ibus in synchronous mode
$ IBUS_ENABLE_SYNC_MODE=1 ibus-daemon -xrd
Do this preferably before starting Studio. This workaround was suggested in https://code.google.com/p/ibus/issues/detail?id=1733 for a different Java application facing the same problems.

Workaround #2: Disable IBus input in Studio
$ XMODIFIERS= ./bin/studio.sh
This will only disable input methods for Studio, not the other applications. Restarting the daemon while Studio is running (‘ibus-daemon -rd’) effectively disables the input methods for all other applications, and can also crash Studio's JVM with a segmentation fault.

edited Jun 01 '20 at 13:34

Sufian

6,405
16
66
120

answered Oct 19 '15 at 11:28

droidev

7,352
11
62
94

2

I'm on windows not Ubuntu. – jack_the_beast Oct 19 '15 at 12:26
1

@Elltz actually I asked OS information by commenting to the question. Since he didnt reply, I posted this answer :-) – droidev Oct 25 '15 at 16:05
Can I make the workaround #2 persist across restart? – Vincent Paing Jun 24 '20 at 04:44
Yes... it should.. but I think the issue is not happening anymore.. they might have fixed it already – droidev Jun 24 '20 at 17:05

score 1 · Accepted Answer · answered Jun 15 '18 at 15:21

1

My robotics team had this problem before on Windows 7. It has been a while, so I don't remember exactly how (this was years ago), but we had found that the problem was related to the project files being in a google drive and the syncing process would make Android Studio lock the files into read-only mode. the workaround we found was to take the files out of the drive folder and use a version control system.

answered Jun 15 '18 at 15:21

The cocatrice

26
2

It's probably what happened back then. – jack_the_beast Jun 15 '18 at 15:23

Android Studio: can't edit files after a while

2 Answers2