-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
CPU usage 100% in Linux (ubuntu 20.04) #5192
Comments
Does your system have a gpu or is it relying on software rendering? |
Driver version |
I experienced same problem using 0.10.0-preview5 and nvidia gtx 1050ti but using latest 0.10.0-rc1 problem solved. Seen now that sakya already used 0.10.0-rc1, please try to cleanup bin and obj <Project Sdk="Microsoft.NET.Sdk">
<PropertyGroup>
<OutputType>Exe</OutputType>
<TargetFramework>net5.0</TargetFramework>
</PropertyGroup>
<ItemGroup>
<PackageReference Include="Avalonia.Desktop" Version="0.10.0-rc1" />
</ItemGroup>
</Project> or try with older version such as |
Hi, I cleaned the build, changed to net5.0 but the cpu is always 100% |
Thanks, It's ok its related to known bug ( #2012 ) if you comment out this cpu goes ok <!-- <ProgressBar IsIndeterminate="True" Margin="0 40" /> --> btw for my project where I not used progress bar I had that problem of cpu when using the previous 0.10.0-preview5 while 0.10.0-rc1 solve, so seems there are some progress fixating the issue of high cpu usage on x11 excluding in fact the progressbar when indeterminate mode. |
You're right, many thanks! EDIT: or are animations just a lot heavier on Linux? |
CPU usage is probably caused by triggering the render timer more frequently. Everything else should be the same for all platforms. |
Ok, many thanks for the help! |
CPU usage 100% in Linux (ubuntu 20.04)
The project XamlControlsGallery under Ubuntu 20.04 and using Avalonia 0.10.0-rc1 has a CPU usage of 100%
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The app shouldn't use 100% of CPU
Screenshots
Desktop:
The text was updated successfully, but these errors were encountered: