WebQuake low performance on Android (WebGL)

NEW
Assigned to

Status

()

defect
P3
normal
6 years ago
a month ago

People

(Reporter: marco, Assigned: mbest)

Tracking

(Blocks 1 bug)

Trunk
All
Android
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [games:p?] webgl-site, URL)

(Reporter)

Description

6 years ago
Looks like on Desktop we are the fastest, but on Android we are really slow.
(Reporter)

Updated

6 years ago
Blocks: gecko-games
Let's get an about:support dump. We need to know what device this is. Current Android perf can change drastically based on the device.
We need to get more data here.
Assignee: nobody → mbest
No longer blocks: gecko-games
Whiteboard: [games:p2]
I highly suspect this was one of the devices that hit the slowpath we fixed in 22.
(Reporter)

Comment 4

6 years ago
I can't execute the demo anymore, it won't load. Can anyone test and close this if necessary?
This demo no longer works on Firefox.
First, the demo is directly reachable at:
https://www.quaddicted.com/stuff/WebQuake/Client/WebQuake.htm

I get this error when running the demo:
TypeError: Not enough arguments to AudioContext.createBuffer.

This works in Chromium.
Component: Canvas: WebGL → Web Audio
Actually, let me make a new bug for the error.
Depends on: 935740
Filed bug 935740 to check if this (seemingly Web Audio) error is our fault or the site's.
If it's the site's fault, this bug should be closed INCOMPLETE.
Component: Web Audio → Canvas: WebGL
Whiteboard: [games:p2] → [games:p2] webgl-site
The demo runs when adding media.webaudio.legacy.AudioContext set to true.

media.webaudio.legacy.AudioBufferSourceNode and/or media.webaudio.legacy.OscillatorNode will be necesssary for sound.
(Assignee)

Comment 9

4 years ago
Should we transfer this to the web audio team?
Whiteboard: [games:p2] webgl-site → [games:p?] webgl-site
(Reporter)

Comment 11

3 years ago
Performance on Android is still not very good. The image is not completely rendered correctly.
Priority: -- → P3
You need to log in before you can comment on or make changes to this bug.