processing / processing/processing4

NullPointerException on Dynamic Window Resize in Processing

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

@tudasamenc 已经在做这个了。

开始于 2025年7月10日。

bug
主要语言
Java
星标
497
派生
183
平均合并
4 小时 39 分钟
30 天内合并 PR
3

描述

Most appropriate sub-area of Processing 4?

Core/Environment/Rendering

Processing version

4.4.4

Operating system

Windows 10

Steps to reproduce this

1. Description :
When dynamically resizing a Processing sketch window (via surface.setSize(w, h) or by enabling surface.setResizable(true)), a NullPointerException may occur in Component$BltBufferStrategy.revalidate(...), due to an internal backBuffers[] array being null.

This happens during the rendering phase, likely due to an invalidated or uninitialized BufferStrategy after the resize.

2. Example Stack Trace :

java.lang.NullPointerException: Cannot invoke "java.awt.image.VolatileImage.validate(java.awt.GraphicsConfiguration)" because "this.backBuffers[...]" is null
    at java.desktop/java.awt.Component$BltBufferStrategy.revalidate(Component.java:4552)
    at java.desktop/java.awt.Component$BltBufferStrategy.getDrawGraphics(Component.java:4449)
    at processing.awt.PSurfaceAWT.render(PSurfaceAWT.java:242)
    at processing.awt.PSurfaceAWT$9.callDraw(PSurfaceAWT.java:1389)
    at processing.core.PSurfaceNone$AnimationThread.run(PSurfaceNone.java:356)

3. Expected Behavior :
When resizing the window, either manually (with setResizable(true)) or programmatically (via surface.setSize(w, h)), the sketch should continue rendering smoothly without crashing or throwing an exception.

snippet

// Paste your code below :)

void setup() {
  size(600, 400);
  surface.setResizable(true);
}

void draw() {
  background(200);
}
Additional context

Discovered Workaround :

Calling surface.setVisible(true) immediately after resizing prevents the crash :

surface.setSize(w, h);
surface.setVisible(true);               // Prevents the NPE
Would you like to work on the issue?

No

贡献指南

打开贡献指南

从这里开始

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

评估

这个 Issue 还没有评估数据。

把新 issue 发到你的邮箱

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