bevyengine / bevyengine/bevy

Bevy on VSCode always use CPU to render when running on Linux but not other OS

Open
#20,815 1 comment 0 reactions 0 assignees View on GitHub
A-Rendering C-Bug O-Web S-Blocked
Dominant language
Rust
Stars
48.2k
Forks
4.8k
Avg merge
3d 16h
Merged PRs (30d)
171

Description

## Bevy version and features

- Bevy 0.16

## \[Optional\] Relevant system information

- Linux

## What you did

Run this minimal example on VSCode on Linux
https://github.com/notmd/bevy_vscode_bug

## What went wrong

The app is very laggy and unusable because Bevy uses CPU to render.

## Additional information
- This bug only happens when running wasm build on VSCode on Linux and does not happen on other OS. It's also doesn't happen when I run on Chrome. My teammate confirmed the app used to work about 3-4 months ago when our app use Bevy 0.15. But last night I try built and test the old version, it also not work
- Discord discussion https://discord.com/channels/691052431525675048/1411085632083726346

| OS | Software | Bug |
|---------|------------|------|
| Linux | VSCode | ❌ |
| Linux | Chrome | ✅ |
| Windows | VSCode | ✅ |
| macOS | VSCode | ✅ |
- Update: This only happen with the July release of VSCode. I tested the June and May releases, they work fine

Contributor guide

Open the contributing guide

Research direction

Start with the minimal example at https://github.com/notmd/bevy_vscode_bug on Linux using the July VSCode release, then compare it with the May and June releases and Chrome. Confirm the renderer and performance behavior across those environments; done means the wasm app no longer renders through the CPU in the affected VSCode setup.

Written by the indexing model from the issue text.

Assessment

Tech stack
linux, rust, vscode, wasm
Domain
computer-graphics, devtools, game-dev, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.