IssueTracker

Linking failed

Execution failed for task ':app:processDebugResources'.
> Android resource linking failed
  /<Stripped Path>/app/src/main/res/layout/activity_main.xml:9: AAPT: error: attribute layout_behaviour (aka com.example.testlayout:layout_behaviour) not found.
     
  error: failed linking file resources.

If it's Gradle issuse, then I tried with 5.2.1-all and same happens.

it's an issue with your application, looks like you are referencing @string/appbar_scrolling_view_behavior but do not define it in your resources.

No, the resource is within Android Library itself, and we implement it in xml by app:layout_behavior="@string/appbar_scrolling_view_behavior". But as of Android Studio 3.4-RC1, it seems to be fixed.:)

I'm sorry but it seems to persist. I'm posting a xml layout:

<?xml version="1.0" encoding="utf-8"?>
<layout xmlns:android="http://schemas.android.com/apk/res/android"
    xmlns:app="http://schemas.android.com/apk/res-auto"
    xmlns:tools="http://schemas.android.com/tools">

    <androidx.coordinatorlayout.widget.CoordinatorLayout
        android:layout_width="match_parent"
        android:layout_height="match_parent">

        <com.google.android.material.appbar.AppBarLayout
            android:id="@+id/appbar"
            style="@style/AppTheme.AppBarStyle"
            android:layout_width="match_parent"
            android:layout_height="wrap_content"
            android:theme="@style/AppTheme.AppBarOverlay">

            <androidx.appcompat.widget.Toolbar
                android:id="@+id/toolbar"
                android:layout_width="match_parent"
                android:layout_height="wrap_content"
                app:layout_scrollFlags="scroll|enterAlways|snap"
                tools:title="@string/app_name" />
        </com.google.android.material.appbar.AppBarLayout>

        <androidx.recyclerview.widget.RecyclerView
            android:id="@+id/message_recyclerView"
            android:layout_width="match_parent"
            android:layout_height="match_parent"
            android:contentDescription="@string/message_selection_view"
            android:shadowColor="@color/grey_800"
            app:layout_behavior="@string/appbar_scrolling_view_behavior" />

        <com.google.android.material.floatingactionbutton.FloatingActionButton
            android:id="@+id/fab"
            android:layout_width="wrap_content"
            android:layout_height="wrap_content"
            android:layout_gravity="bottom|end"
            android:layout_margin="@dimen/dp_16"
            android:visibility="invisible"
            app:backgroundTint="@color/white"
            app:rippleColor="?attr/colorControlHighlight"
            app:srcCompat="@drawable/ic_cloud_upload"
            app:tint="@color/colorAccent" />
    </androidx.coordinatorlayout.widget.CoordinatorLayout>
</layout>

As you can see within the RecyclerView that I've used the string resource and it's giving me the error.

Gradle: gradle-5.2.1-all.zip
Project level:
buildscript {
    repositories {
        google()
        jcenter()
    }
    dependencies {
        classpath 'com.android.tools.build:gradle:3.4.0-rc01'
    }
}
Modules:
dependencies {
    implementation fileTree(include: ['*.jar'], dir: 'libs')
    implementation 'androidx.appcompat:appcompat:1.1.0-alpha02'
    implementation 'com.google.android.material:material:1.1.0-alpha04'
    implementation 'androidx.constraintlayout:constraintlayout:2.0.0-alpha3'
    implementation 'androidx.recyclerview:recyclerview:1.1.0-alpha02'
   ...

Another example of AS 3.4 RC 1:

<androidx.core.widget.ContentLoadingProgressBar
                android:id="@+id/progress_bar"
                style="@style/Widget.MaterialProgressBar.ProgressBar.Horizontal.NoPadding"
                android:layout_width="match_parent"
                android:layout_height="wrap_content"
                android:max="100"
                android:progress="1"
                android:progressTint="@color/colorPrimary" />

Error I'm getting: Can't resolve symbol '@style/Widget.MaterialProgressBar.ProgressBar.Horizontal.NoPadding'

Gradle: gradle-5.1.1-all

Dependencies are same as above. While with latest AS 3.3.2, I'm getting no such error and clicking it, takes me to Android's resource file of values.xml.

P.S. "looks like you are referencing @string/appbar_scrolling_view_behavior but do not define it in your resources.", I would like to add that it compiles perfectly!

Let's track this in the other bug.

I couldn't repro this on my device and find any suspicious system log in the feedback report. So, I set the status to "ExtrernalDependency" until screenshot of top within the guest is provided.
Sorry for not mentioning it.

Sorry, keiichi, I gave you bad advice here. I didn't realize it was an internally reported bug.
Let's try to figure out a way to reproduce this. Do you have a device you can try to repro on in dev mode?

If it's of any help at all my Linux app of choice is vscode and I think it was indexing when this usually happened

I got it. I don't have ASUS Chromebox 3 but one ASUS Chromebook Flip C433 (shyvana) whose kernel version is same.
As the first step, let me try to flash 84.0.4147.127 on it.

I've changed my channel back to beta and version 85. All was well until beta updated to 86.0.42 then the problem started to come back. I didn't notice at first. 85 had the hyperthreading enabled flag 86 doesn't so the problem only happened after I enabled hyperthreading with the scheduler flag.

I played around a few times with that flag on and off. With the flag on crostini runs terrible within a few seconds of startup. The last time I toggled it off COG indicated that it is off by only showing me 2 cpus but I still had the problem with laggy keyboard / mouse input and random high CPU usage from Crostini. I check with htop, which shows the cpu usage too, it thought I still had hypertreading enabled because it showed 4 cpus

Once restarted crostini it was back to 2 cpus and the high cpu usage in task manager went away along with input lag.

I'm not sure of the flags used to start the virtual machine but it sounds like it was trying to virtualize 4 cpus on 2 cpu hardware which could certainly account for high cpu usage.  Not sure what happening when using the scheduler flag though.