Skip to content

Flutter web not rendering on Chrome with WASM and disabled GPU #173401

Closed

Description

@Gustl22

Steps to reproduce

  1. flutter create wasm_app
  2. cd wasm_app
  3. flutter run -d chrome --web-browser-flag="--disable-gpu" --wasm

Expected results

Run without any error, or give a proper error message that GPU needs to be enabled for wasm.

Actual results

Uncaught RuntimeError: null function or function signature mismatch
    at skwasm.wasm:0x2bb2a
    at skwasm.wasm:0x1ed26c
    at w._surface_renderPicturesOnWorker (skwasm.js:102:295)
    at skwasm.js:33:291
    at h (skwasm.js:32:321)

Code sample

Code sample
flutter create wasm_app

Screenshots or Video

Screenshots / Video demonstration

[Upload media here]

Logs

Logs
Uncaught RuntimeError: null function or function signature mismatch
    at skwasm.wasm:0x2bb2a
    at skwasm.wasm:0x1ed26c
    at w._surface_renderPicturesOnWorker (skwasm.js:102:295)
    at skwasm.js:33:291
    at h (skwasm.js:32:321)

Flutter Doctor output

Doctor output
flutter doctor -v
[✓] Flutter (Channel stable, 3.32.8, on macOS 15.5 24F74 darwin-arm64, locale en-US) [533ms]
    • Flutter version 3.32.8 on channel stable at /opt/homebrew/Caskroom/flutter/stable/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision edada7c56e (13 days ago), 2025-07-25 14:08:03 +0000
    • Engine revision ef0cd00091
    • Dart version 3.8.1
    • DevTools version 2.45.1

[!] Android toolchain - develop for Android devices (Android SDK version 35.0.1) [1,408ms]
    • Android SDK at /Users/.../Library/Android/sdk
    • Platform android-35, build-tools 35.0.1
    • Java binary at: /Users/.../Library/Java/JavaVirtualMachines/jbr-17.0.11/Contents/Home/bin/java
      This JDK is specified in your Flutter configuration.
      To change the current JDK, run: `flutter config --jdk-dir="path/to/jdk"`.
    • Java version OpenJDK Runtime Environment JBR-17.0.11+1-1312.2-nomod (build 17.0.11+1-b1312.2)
    ! Some Android licenses not accepted. To resolve this, run: flutter doctor --android-licenses

[✓] Xcode - develop for iOS and macOS (Xcode 16.4) [981ms]
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 16F6
    • CocoaPods version 1.16.2

[✓] Chrome - develop for the web [72ms]
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2024.3) [72ms]
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 21.0.6+-13368085-b895.109)

[✓] IntelliJ IDEA Ultimate Edition (version 2025.1.1.1) [71ms]
    • IntelliJ at /Applications/IntelliJ IDEA.app
    • Flutter plugin version 86.0.2
    • Dart plugin version 251.27623.5

[✓] Connected device (3 available) [6.1s]
...

[✓] Network resources [287ms]
    • All expected network resources are available.

! Doctor found issues in 1 category.

Related to #171402

Chrome version:
Version 139.0.7258.67 (Official Build) (arm64)

Activity

  1. tirth-patel-nc commented on Aug 7, 2025

    @tirth-patel-nc
    Member

    Thanks for the report. I'm seeing the same behavior with the latest SDK versions when Graphics Acceleration is disabled in Chrome. This might be related to #171402, but since this one involves the --wasm flag, I'm keeping this open for the team's attention.

    I should've reopened #172158 earlier, my mistake.

    Google Chrome Version 139.0.7258.67 (Official Build) (arm64) (macOS Sequoia 15.5)
    
    stable : 3.32.8
    master : 3.33.0-1.0.pre-1305
    beta : 3.35.0-0.2.pre
    
  2. added
    has reproducible stepsThe issue has been confirmed reproducible and is ready to work on
    platform-webWeb applications specifically
    team-webOwned by Web platform team
    e: wasmIssues related to the wasm build of Flutter Web.
    and removed
    in triagePresently being triaged by the triage team
    on Aug 7, 2025
  3. cachius commented on Aug 9, 2025

    @cachius

    Error from STDOUT from gles2_command_buffer_stub.cc

    [ERROR:gpu/ipc/service/gles2_command_buffer_stub.cc:270] ContextResult::kFatalFailure: Failed to create context.
    
  4. github-actions commented on Aug 26, 2025

    @github-actions

    This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.

  5. locked as resolved and limited conversation to collaborators on Aug 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    browser: chrome-desktoponly manifests in desktop Chromee: wasmIssues related to the wasm build of Flutter Web.found in release: 3.32Found to occur in 3.32found in release: 3.33Found to occur in 3.33has reproducible stepsThe issue has been confirmed reproducible and is ready to work onplatform-webWeb applications specificallyr: fixedIssue is closed as already fixed in a newer versionteam-webOwned by Web platform team

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions