Android Studio freezes when right clicking the project explorer - android-studio

I'm using Android Studio 1.5.1 on Kubuntu 15.10 and lately, Android Studio freezes completely whenever I right click into the project explorer. The only thing I can do then is to kill the process.
More oddly, whenever I hover the Help menu with the mouse, the complete OS freezes completely and I have to restart the computer. I am not 100% sure if these two issues are related, but they started at the same time.
Sometimes (about 10% of the time) it works well. I have no idea what influences this pattern, though. This used to happen earlier as well, but much less frequent.
The usage of different color schemes or deactivating plugins seem to have no influence on this behavior. I also did not install any fishy third party software or anything else that could (to my knowledge) have influenced this. Any ideas?

The issue seems to be resolved in the latest stable release (2.0).

I've recently run into this as well. Pointing jstack at the hung process suggests that it's this problem.
Switching to the Darcula or GTK+ theme resolved it for me. Weirdly, I can switch back to the Intellij theme afterwards and the problem stays fixed - I just have to switch to GTK+ or Darcula at some point after startup but before triggering a right-click menu.
Edit, 1 day later: In a deeply unimpressive plot twist, this solution no longer works for me. I've changed nothing since yesterday, but now attempting to switch themes triggers the lockup ಠ_ಠ
Edit, 1 day, 5 minutes later: After a restart the situation improved slightly - changing the theme now works again, and avoids the freeze-on-rightclick failure. I'm finding it difficult to take this as much of a victory.
Edit: As karpfen notes below, this issue has been resolved in the latest release. Huzzah!

Related

Is there a way to keep quick documentation on one screen in newest version of Android Studio?

My setup is a main display set above my laptop screen. I've recently upgraded to the newest version of Android Studio Dolphin 2021.3.1 on Windows 11 after a couple months away and now the quick docs bleed down into my laptop screen:
I've downgraded again to Chipmunk 2021.2.1 to confirm that the quick docs used to stay on the main display:
As both my main and my laptop display are the same resolution, but different sizes, it offsets and shrinks half of the quick docs window, not to mention separates it with a taskbar and two bezels, which makes them unreadable most of the time. I'd much prefer the old way.
Am I missing some setting or is this a bug (or intended feature)?
I've browsed and searched through the settings, but found no way to revert the way the quick docs are displayed. I've done a google search and found noone experiencing the same issue.
EDIT: After tinkering a bit I found that clicking on code and pressing the ctrl+Q shortcut makes the quick docs draw on main display as expected. Only on hovering over code does the above problem appear. I've reported it as a bug

Android studio keeps underlining all classes red while saying that R doesn't exist

I know this has been asked many times, but usually the advice is something along the lines of "decrease Android gradle plugins version" or something like that. Firstly, that doesn't seem to work for me, secondly, decreasing the version in order to solve this kind of problem doesn't seem like a good practice and I'd like to avoid it (especially since Android Studio warns me I should increase the version back again when I try to decrease it).
So now what exactly is happening + some details that might help:
Every class is underlined with red color in the project explorer and there are loads of "java package R does not exist" messages in the Problems view
When I open any class, suddenly its red underline disappears and there are actually no errors in this class
It happens if and only if AS does an automatic build (I can see "21:03 Auto build completed with errors" in the Event log). When I build manually, there are no errors in the Problems view, and no class is underlined (that is, until AS does auto build again, which happens all the time)
In any way, this doesn't prevent building of the application/APK/AAB, installing it on the phone/virtual, and running it
This has been happening ever since I updated Android Studio to v4.1 (I now use Android gradle plugin v4.1.0)
(Of course, I also tried all the obvious stuff - deleting every temporary/generated file, invalidating cache, restarting, cleaning, etc. etc. Everything I could think of.)
I had a problem like this before, it had nothing to do with the gradle ijust add "import com.package.appname.R;" into myclass and is worked

The Godot Engine Editor's IDE/GUI seems to be slow and to ignore mouse interaction

I'm using Godot_v3.2.1-stable_win64.exe(current Godot version) on my Windows 10. When running a project everything seems to work fine but when using the actual IDE of the Godot engine it seems like the IDE screen doesn't update fluidly on every mouse interaction but like only every 5 seconds instead (as like FPS would be low).
So mostly on hovering or clicking something it would light up or be triggered after you clicked on some other thing elsewhere (which is stupid of course).
This makes it even impossible to hit a button sometimes in the IDE.
E.g. when renaming a file a Window/Box for renaming pops up but you do not see it, because the IDE screen isn't updated. So if you don't blindly click on the box (which you don't see) the option for renaming is lost, because the box closes when clicking anywhere else. See what I mean?
Thank you for listening. Have a great day.
This is a known issue. Try updating your graphics driver to the latest version provided by Intel (not your OEM).

MyEclipse's accelerate keyszoom in(ctrl+-) and zoom out(ctrl+=) are invalid

I use myeclipse (version :myeclipse-2015-stable-3.0 or myeclipse-2016-ci-7) in windows 7, and I want to zoom in/out the fonts while editing by accelerate keys ctrl+ =/-,but they don't work.
I don't want to use the way that windows--preference--color and fonts--...to change fonts size because it isn't convenient,there is no accelerate keys confilcts also,and after changing accelerate keys,they still don't work.
Any ways to solve this problem?
Those commands don't seem to be defined in the General->Keys preferences page, for text editing, but even though they are defined in eclipse Mars (on which MyEclipse 2016 is based), they don't work there either. I can't find an eclipse bug for that, though there probably should be one.
However, I did find a solution, if you're willing to update to MyEclipse 2017 (the CI stream or the Stable stream), since the zoom function works fine there.

PyQt Release vs Debug

I have a system,written on PyQt4. It is mostly developed and debug under linux (ubuntu) systems, in Eric IDE, and everything works fine. Last task was to create a nested editor for a table cell. So, i did it and it also looks nice in ubuntu. I also ran it under Windows 7 x64, and the behavior was the same.
However, after making executable file with cx_Freeze in Windows 2000 (it's weird, but this environment was configured before me), the editors behavior became unexpected. After opening Editor it's first cell have 'role == Qt.EditRole', and it's almost impossible to commit any changes there without closing the whole Editor. Another issue is about "OK" button - it closes the Editor window, but doesn't commit any changes in it also, and you cannot call it again without changing the active cell (but maybe i just forgot to emit some signals here, so it's not the main bug here).
So my question - where should i look to find the reason for these problems. I'm new to qt, and maybe it is normal behavior and just my fault in code? Or the reason is in different environments (python 2.7, latest pyqt vs python 2.6 and some older pyqt). Or it is the influence of cx_Freeze... Maybe some other directions?
Sorry for long post and my English :)
Hope to get any answers soon.
I think there's a chance that Qt or PyQt on windows 2000 server is outdated or broken.
So If possible, bring cx_freeze related code to your local computer and test it out.
If it fixes the problem, you can upgrade or reinstall Qt on windows 2000 server.

Resources