setTimeout callbacks with stale closures

[rmcc3]

Description

Several setTimeout callbacks capture the layers state at call time, but execute later when layers may have changed.

Affected File

components/canvas-editor.tsx

Current Behavior

// In captureCanvasAsLayer (~line 2280):
setTimeout(async () => {
  // ...
  const updatedLayers = [...layers, newLayer]  // 'layers' is stale!
  setLayers(updatedLayers)
}, 50)

// In handleGLBThumbnailGenerated (~line 2919):
setTimeout(() => setForceRedraw(prev => prev + 1), 50)
setTimeout(() => setForceRedraw(prev => prev + 1), 150)

Security Impact

• New layers may be lost if user adds/deletes layers during timeout
• Undo history may become corrupted
• Canvas state may become inconsistent with layer state

Suggested Fix

Use functional updates consistently:

setTimeout(async () => {
  canvas.toBlob(async (blob) => {
    // ...
    // Use functional update to get latest state
    setLayers(currentLayers => [...currentLayers, newLayer])
  })
}, 50)

[rmcc3]

There is more I can add, but I am taking a break from this review.

[camenduru]

Thanks 🍞❤ I'll work on all those issues.

[rmcc3]

Thanks 🍞❤ I'll work on all those issues.

I'd work on the image proxy first. I was able to replicate it on your cloud deployment to load up Google.