Android Studio Arctic Fox (2020.3.1) crashing while loading XML - android-studio

Today I updated my Android Studio to the newest stable version (Arctic Fox 2020.3.1) and whenever I try to open xml layout, it crashes. I've tried many different things, from rebuilding to invalidating but nothing helped. After upgrade I haven't been able to uninstall Android, because uninstaller was missing (possibly due to crash). I had to restore the system to the point I had an older version. At this point I managed to reinstall Android Studio to the newest version. Even after that the program persisted to crash after trying to open xml (crashes while initializing). At this point I couldn't uninstall again, because the uninstaller is missing (I believe it's due to crash). I had to restore the system again. Any ideas what should I do or did anyone else had the same issue sometimes ago? Thank you in advance. A portion of error is listed below:
--------------- T H R E A D ---------------
Current thread (0x0000000047be3000): JavaThread "Layoutlib Render Thread" daemon [_thread_in_native, id=8752, stack(0x0000000042430000,0x0000000042530000)]
Stack: [0x0000000042430000,0x0000000042530000], sp=0x0000000042525f20, free space=983k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
C [libandroid_runtime.dll+0xb37ff]
Java frames: (J=compiled Java code, j=interpreted, Vv=VM code)
j android.graphics.HardwareRenderer.nSyncAndDrawFrame(J[JI)I+0
j android.graphics.HardwareRenderer.syncAndDrawFrame(Landroid/graphics/FrameInfo;)I+13
j android.graphics.HardwareRenderer$FrameRenderRequest.syncAndDraw()I+8
j com.android.layoutlib.bridge.impl.RenderSessionImpl.renderAndBuildResult(Landroid/view/ViewGroup;Landroid/graphics/HardwareRenderer;)Lcom/android/ide/common/rendering/api/Result;+18
j com.android.layoutlib.bridge.impl.RenderSessionImpl.renderAndBuildResult(ZZ)Lcom/android/ide/common/rendering/api/Result;+522
j com.android.layoutlib.bridge.impl.RenderSessionImpl.render(Z)Lcom/android/ide/common/rendering/api/Result;+3
j com.android.layoutlib.bridge.BridgeRenderSession.render(JZ)Lcom/android/ide/common/rendering/api/Result;+49
j com.android.ide.common.rendering.api.RenderSession.render(J)Lcom/android/ide/common/rendering/api/Result;+3
j com.android.ide.common.rendering.api.RenderSession.render()Lcom/android/ide/common/rendering/api/Result;+4
j com.android.tools.idea.rendering.RenderTask.lambda$renderInner$13(Lcom/intellij/psi/PsiFile;)Lcom/android/tools/idea/rendering/RenderResult;+4
j com.android.tools.idea.rendering.RenderTask$$Lambda$5038.call()Ljava/lang/Object;+8
j com.android.tools.idea.rendering.RenderExecutor$runAsyncActionWithTimeout$2.run()V+205
J 34329 c2 java.util.concurrent.ThreadPoolExecutor.runWorker(Ljava/util/concurrent/ThreadPoolExecutor$Worker;)V java.base#11.0.10 (187 bytes) # 0x00000000174fd4a8 [0x00000000174fce40+0x0000000000000668]
j java.util.concurrent.ThreadPoolExecutor$Worker.run()V+5 java.base#11.0.10
j java.lang.Thread.run()V+11 java.base#11.0.10
v ~StubRoutines::call_stub
siginfo: EXCEPTION_ILLEGAL_INSTRUCTION (0xc000001d)

For Windows
Replace the existing libandroid_runtime.dll at
[PATH_TO_STUDIO_DOWNLOAD]/plugins/android/resources/layoutlib/data/win/lib64/
with this.
For Linux
Replace the existing libandroid_runtime.so at
[PATH_TO_STUDIO_DOWNLOAD]/plugins/android/resources/layoutlib/data/linux/lib64/
with this.
Note: These files are for Arctic Fox
Sources: issuetracker.google.com/issues/195340081 & issuetracker.google.com/issues/195185622

Related

Why does my Selenium VBA code no longer work?

I have a very simple VGA macro in Excel that worked fine for awhile and now has stopped. I now get one of the two error message below:
The code is somewhat longer, but I've taken out the irrelevant lines; even what I have below doesn't work:
Public edgebot As WebDriver
Sub EUPatentClass()
edgebot.Start "edge"
End Sub
The references are as follows:
Current version of Edge is Version 108.0.1462.54 (Official build) (64-bit)
Current version of edgedriver.exe (renamed from msedgedriver.ext) is also Version 108.0.1462.54
I've tried uninstalling and then reinstalling Selenium 2.0.9, and also repairing .NET Core Runtime 3.1.32(x64) and .NET SDK 6.0.307(x64). I'm running Windows 10, ver 22H2 (Build 19045.2364), fully patched and up to date.
Can anyone give me a suggestion as to what to try next? THANKS!!!

Untrusted touch events are blocked Android 12

My app is affected due to untrusted touch events introduced by android in Android 12. If i understand it correctly problem is majorly due to using of the flag FLAG_NOT_TOUCHABLE, so I removed all the occurrences
08-20 16:10:45.752 1716 2206 D InputDispatcher: Stack of obscuring windows during untrusted touch (705, 1575):
08-20 16:10:45.752 1716 2206 D InputDispatcher: * type=2038, package=xxxxxxx, id=204, mode=USE_OPACITY, alpha=1.00, frame=[0,145][1080,2296], touchableRegion=[0,145][1080,2296], window={36c5ada , flags={NOT_FOCUSABLE | NOT_TOUCHABLE | NOT_TOUCH_MODAL | LAYOUT_IN_SCREEN | FORCE_NOT_FULLSCREEN | HARDWARE_ACCELERATED}, inputFeatures={0x0}, hasToken=true, applicationInfo.name=, applicationInfo.token=<null>
Still the NOT_TOUCHABLE flag is not going! There is only one write up available as of now on the subject and my case falls in 'Unnecessarily large windows' in this blog. i.e. my window is already wrap_content and i have removed any occurrence of FLAG_NOT_TOUCHABLE. Still my touches are being blocked. How i know my touches work fine otherwise? As recommended by the developer.android site when i run following command adb shell settings put global block_untrusted_touches 2, everything seems to be working just fine. Any help would be highly appreciated!

An unhandled exception of type 'System.IO.IOException' occurred in PresentationFramework.dll

Application is unable to load ANY xaml. Nor create empty window "var abc = new Window1();"
Error message is still the same:
An exception of type 'System.IO.IOException' occurred in PresentationFramework.dll but was not handled in user code
Additional information: Cannot locate resource 'wvmlog.xaml'. (for wvmlog.xaml)
Exception occur on InitializeComponent();
These objects are created without error on another PC - so problem is not in Project settings.
Do not help:
reinstall VS
new install of VS
reinstal .net frameworks
undo source from TFS
complete new workspace and load from TFS
visual studio Clean colution
find and delete all cached dll, pbd
remove all obj directories in solution
install and use VS 2010, VS 2012, VS 2013
move VS and solution into another hard drive
Do Help:
Copy of project (help for 1-2 days, then problem appear again without any manipulation with xaml)
Change solution configuration from 'Debug' to 'Release' (help for 1-2 days, then problem appear in Release configuration without any manipulation with xaml)
Problem is at one PC with Win 7, 64-bit.
The problem occur suddenly after some xaml window renaming, but these changes was many times undo-ed, but problem remain.
Maybe some OS damage, or some wpf/.net caches?
Why wpf/.net show such error on project which is compiled without error - so compiler KNOW that these resources does exist?
Any help is appreciated.
I had this very same issue.
What design pattern are you using?
The issue I had was when I changed the output window ie created a new one and deleted the old one.
I am using MVVM so I created the window in the View folder.
If this is your issue, your APP.XAML will look like:
<Application x:Class="dotDiff2013.App"
xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
StartupUri="MainWindow.xaml">
<Application.Resources>
</Application.Resources>
</Application>
You then change the startURI to wherever your new window is stored. ie in the view folder.
StartupUri="Main/MainWindow.xaml"
This helped for me. Hope it's the solver to your problem.

False error in XAML parsing

I'm getting a persistent non-fatal error when the building my WinRT project
Error 1 Closing tag for element '' was not found.
Of course there is an ending tag in my XAML and the project builds and runs just fine. How can I get VS to just give up on this error?
(Yes, I've tried a clean build)
I also got a similar error. Closing and reopening the solution resolved it. I believe this issue was fixed with Visual Studio 2012 Update 2
Have a look at : http://social.msdn.microsoft.com/Forums/windowsapps/en-US/dea9687f-5939-4a15-b197-707eb3f26d3b/false-error-in-xaml-parsing

Node.js Setup fails. Where is the log?

Busy trying to setup node.js via the windows download on the nodejs website. It seems run along ok right until the end when it hits the "creating shortcurts..." then starts to rollback and get a pretty useless general error.
Are there no log files I can check to see whats going on?
My preferred option is to use the command line msiexec tool as indicated on WiX's website:
msiexec /i MyApplication.msi /l*v MyLogFile.txt
Another option that I've never used is to edit the registry as indicated on Microsoft's website:
To enable Windows Installer logging yourself, open the registry with Regedit.exe and create the following path and keys:
HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\Installer
Reg_SZ: Logging
Value: voicewarmupx
The letters in the value field can be in any order. Each letter turns on a different logging mode. Each letter's actual function is as follows for MSI version 1.1:
v - Verbose output
o - Out-of-disk-space messages
i - Status messages
c - Initial UI parameters
e - All error messages
w - Non-fatal warnings
a - Start up of actions
r - Action-specific records
m - Out-of-memory or fatal exit information
u - User requests
p - Terminal properties
+ - Append to existing file
! - Flush each line to the log
x - Extra debugging information. The "x" flag is available only on Windows Server 2003 and later operating systems, and on the MSI redistributable version 3.0, and on later versions of the MSI redistributable.
"*" - Wildcard, log all information except for the v and the x option. To include the v and the x option, specify "/l*vx".
Note This should be used only for troubleshooting purposes and should not be left on because it will have adverse effects on system performance and disk space. Each time you use the Add/Remove Programs tool in Control Panel, a new Msi*.log file is created.

Resources