WebGL: INVALID_VALUE: vertexAttribPointer: index out of range (Ubuntu)

未关闭
#194 23 条评论 14 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
35/100
Issue 类型
缺陷
描述清晰度
描述清楚
活跃度
停滞
技术栈
javascript

调研方向

The report points to PIXI.WebGLSpriteBatch.flush in phaser.js and the shader.aTextureIndex attribute lookup, where the location is -1; the minimal reproduction is new Phaser.Game({width: 10, height: 10, renderer: Phaser.AUTO, resolution: 1}). Start by comparing the affected 2.7.x behavior with 2.6.2 and trace the shader attribute setup and use. Done means the minimal game no longer produces the vertexAttribPointer warning in Firefox or Chromium.

由索引模型根据 Issue 内容生成。

描述

bug help wanted

A bug in the API:

I am getting WebGL: INVALID_VALUE: vertexAttribPointer: index out of range spam on Firefox as well as on Chromium, running Ubuntu.

There is no condition for it to happen. It just happens always. A "code example" therefore simply is the empty example codepen: https://codepen.io/pen?template=vyKJvw

There is nothing obvious wrong, except those errors being spammed.

Here is the stacktrace from chromium, referencing lines in phaser-arcade-physics.js of 2.7.7:

PIXI.WebGLSpriteBatch.flush @ phaser.js:5153
PIXI.WebGLSpriteBatch.end @ phaser.js:4806
PIXI.WebGLRenderer.renderDisplayObject @ phaser.js:3742
PIXI.WebGLRenderer.render @ phaser.js:3705
updateRender @ phaser.js:21403
update @ phaser.js:21325
updateRAF @ phaser.js:49064
_onLoop @ phaser.js:49047

It happens due to shader.aTextureIndex in the line
gl.vertexAttribPointer(shader.aTextureIndex, 1, gl.FLOAT, false, stride, 20);
being -1

It is -1 because the getAttributeLocation earlier does indeed seem to return -1
I have no idea why that is however. It reminds me of an issue I had in other WebGL code that was due to some attributes being optimized away since they were not used, but the shader code of the respective shader here does seem to at least superficially use the attribute.

The minimal code to create the issue is to have Phaser in your namespace and start it with:

new Phaser.Game({width: 10, height: 10, renderer: Phaser.AUTO, resolution: 1})

From that point on it spams the warning.

I tested 2.7.7 and 2.7.3, both show the error.
2.6.2 is unaffected

主要语言
JavaScript
星标
1.4k
派生
485
平均合并
1 天 2 小时
30 天内合并 PR
9

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

phaserjs/phaser-ce 的其他 Issue

查看 phaserjs/phaser-ce 的全部 Issue

相似的 Issue

更多 JavaScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。