Hacktoberfest 2026：维护者为十月标记出来的 issue，仍然开放、适合新手。 浏览 Hacktoberfest issue

scattergl remains blank after WebGL context restoration; regl refresh retains stale ANGLE_instanced_arrays

未关闭
#8,068 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
45/100
Issue 类型
缺陷
描述清晰度
描述清楚
活跃度
活跃
技术栈
javascript
领域
computer-graphics, data-visualization

调研方向

The issue is in the bundled @plotly/regl library, specifically in the generated refresh procedure that retains a stale ANGLE_instanced_arrays extension object. Start by examining lib/core.js around line 3658 in the regl repository. The reproduction HTML provides a test case; run it to see the blank scattergl after context restoration. Investigate other WebGL state restoration issues beyond the extension reference, as fixing the divisor alone did not restore rendering.

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

描述

bug P3 size: 1

Summary

After a WebGL context is lost and restored, scattergl line traces can remain blank even after Plotly.redraw. Axes and legends remain visible, the trace data is intact, and gl.isContextLost() returns false.

This reproduces with the official Plotly.js 4.1.1 bundle in a standalone HTML page, independently of Jupyter. Investigation identified one concrete defect in the bundled @plotly/regl: its generated refresh procedure retains a pre-loss ANGLE_instanced_arrays extension object. Correcting that reference repairs attribute divisors but does not fully repair rendering, so this report does not claim that it is the only recovery defect.

Environment

  • Plotly.js 4.1.1, official CDN bundle (latest stable checked on 2026-09-23).
  • macOS; Chromium 153.0.0.0, in the Codex embedded browser; WebGL 1.
  • Initially observed in JupyterLab with Plotly.py 7.1.0. Both the Jupyter renderer bundle and window.Plotly were 4.1.1.
  • The standalone reproduction below has no Python/Jupyter dependency. Other browsers/GPUs have not been tested.

Reproduction

  1. Save the following as an HTML file and open it in the browser. It uses only synthetic data.
  2. Confirm that four line traces are visible.
  3. Click Lose and restore the plot context once. This uses WEBGL_lose_context on this test plot only, waits for both context events, and then calls Plotly.redraw.

The internal line2d.gl path and the first six attribute locations are diagnostics for this tested version/configuration, not a proposed public API. The visual failure does not depend on inspecting those locations.

Complete standalone reproduction 
<!doctype html>
<meta charset="utf-8">
<title>Plotly scattergl context restoration</title>
<script src="https://cdn.plot.ly/plotly-4.1.1.js"></script>
<button id="run" disabled>Lose and restore the plot context</button>
<div id="plot"></div>
<pre id="log"></pre>
<script>
const gd = document.getElementById('plot');
const button = document.getElementById('run');
const log = document.getElementById('log');
const data = Array.from({length: 4}, (_, j) => ({
  type: 'scattergl', mode: 'lines', name: 'series ' + j,
  x: Array.from({length: 403}, (_, i) =>
    new Date(Date.UTC(2025, 0, 2 + i)).toISOString()),
  y: Array.from({length: 403}, (_, i) =>
    j === 3 ? 0 : 10000 * (Math.sin(i / 23 + j) + i * (j + 1) / 150))
}));
const once = (target, name) => new Promise(resolve =>
  target.addEventListener(name, resolve, {once: true}));
const delay = ms => new Promise(resolve => setTimeout(resolve, ms));

function snapshot(gl) {
  const ext = gl.getExtension('ANGLE_instanced_arrays');
  const pixels = new Uint8Array(gl.drawingBufferWidth * gl.drawingBufferHeight * 4);
  gl.readPixels(0, 0, gl.drawingBufferWidth, gl.drawingBufferHeight,
    gl.RGBA, gl.UNSIGNED_BYTE, pixels);
  let nontransparentPixels = 0;
  for (let i = 3; i < pixels.length; i += 4) if (pixels[i]) nontransparentPixels++;
  return {
    contextLost: gl.isContextLost(),
    divisors: Array.from({length: 6}, (_, i) =>
      gl.getVertexAttrib(i, ext.VERTEX_ATTRIB_ARRAY_DIVISOR_ANGLE)),
    nontransparentPixels
  };
}

Plotly.newPlot(gd, data, {width: 642, height: 360}).then(() => {
  // Internal diagnostic path for Plotly.js 4.1.1; not a public API.
  const gl = gd._fullLayout._plots.xy._scene.line2d.gl;
  log.textContent = JSON.stringify({version: Plotly.version, before: snapshot(gl)}, null, 2);
  button.disabled = false;
  button.onclick = async () => {
    button.disabled = true;
    try {
      const before = snapshot(gl);
      const oldExtension = gl.getExtension('ANGLE_instanced_arrays');
      const loss = gl.getExtension('WEBGL_lose_context');
      gl.canvas.addEventListener('webglcontextlost', event => event.preventDefault(), {once: true});
      const lost = once(gl.canvas, 'webglcontextlost');
      loss.loseContext();
      await lost;
      await delay(150);
      const restored = once(gl.canvas, 'webglcontextrestored');
      loss.restoreContext();
      await restored;
      await delay(150);
      await Plotly.redraw(gd);
      log.textContent = JSON.stringify({
        version: Plotly.version, before,
        sameExtensionObject: oldExtension === gl.getExtension('ANGLE_instanced_arrays'),
        afterRestoreAndRedraw: snapshot(gl)
      }, null, 2);
    } catch (error) { log.textContent += '\n' + error.stack; }
  };
});
</script>
Expected

The four line traces render again once the context is restored and the plot is redrawn.

Actual

The plotting area remains blank while the axes and legend remain. The exact reproduction above produced:

{
  "version": "4.1.1",
  "before": {
    "contextLost": false,
    "divisors": [1, 1, 1, 1, 1, 1],
    "nontransparentPixels": 18394
  },
  "sameExtensionObject": false,
  "afterRestoreAndRedraw": {
    "contextLost": false,
    "divisors": [0, 0, 0, 0, 0, 0],
    "nontransparentPixels": 0
  }
}

Pixel counts are environment-dependent; the relevant observation is the visible-to-blank transition after restoration.

Investigation

Evidence from the original failure
  • The browser had already logged WARNING: Too many active WebGL contexts. Oldest context will be lost. before investigation began.
  • The affected figure still had four enabled scattergl traces, each with 403 finite y values, and valid axis ranges. Its canvas contained only a tiny fragment of a line.
  • Its WebGL context was no longer lost. The six line-coordinate/color attribute divisors were 0 in actual GL state, while the corresponding regl attribute cache entries were 1. Healthy neighboring line plots had matching actual/cached divisors of 1.
  • Debugger inspection showed that the generated refresh closure retained an extension object different from the current gl.getExtension('ANGLE_instanced_arrays'). The regl instance and canvas identities were correct.

The context-limit warnings explain why recovery becomes relevant. The exact allocation sequence that exceeded the limit was not recorded. The original failing output was inspected without rerunning its cell or redrawing it; subsequent experiments used a separate synthetic page.

Confirmed stale extension reference

In the published @plotly/regl 2.1.2 source, the generated refresh procedure captures the extension instance using INSTANCING = env.link(extInstancing). Context restoration calls extensionState.restore(), but the compiled refresh procedure still refers to the old object.

In a separately instrumented synthetic reproduction:

  1. The ANGLE extension object identity changed after restoration.
  2. Refresh called vertexAttribDivisorANGLE(index, 1) through the old extension; immediately querying that attribute still returned 0.
  3. The draw procedure used the current extension, but its cached attribute state already said divisor=1, so it skipped the assignment needed to restore actual GL state.
Partial diagnostic patch, not a complete fix

In a temporary copy of the official bundle, replacing the captured reference with a dynamic lookup:

- INSTANCING = env.link(extInstancing);
+ INSTANCING = refresh.def(shared.extensions, ".angle_instanced_arrays");

made the same restore/redraw sequence correctly restore all six divisors to 1, with no failed divisor assignments recorded. The chart still remained blank. Manually restoring divisors through the new extension likewise did not recover the whole chart. Other resource/state restoration problems remain to be isolated; this patch should not be treated as a complete solution.

Related reports

I could not find an existing issue specifically covering this stale compiled extension reference. Please let me know if this should instead be tracked in plotly/regl, or if additional context/resource diagnostics would help.

主要语言
JavaScript
星标
18.3k
派生
2k
平均合并
2 天 10 小时
30 天内合并 PR
30

贡献指南

打开贡献指南

从这里开始

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

plotly/plotly.js 的其他 Issue

查看 plotly/plotly.js 的全部 Issue

相似的 Issue

更多 JavaScript Issue

把新 issue 发到你的邮箱

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