Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

error in web Cannot read properties of null (reading 'rangeMin') #2426

Open
YOEL311 opened this issue May 13, 2024 · 1 comment
Open

error in web Cannot read properties of null (reading 'rangeMin') #2426

YOEL311 opened this issue May 13, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@YOEL311
Copy link

YOEL311 commented May 13, 2024

Description

The crash occurs when the user changes the props from the Storybook interface (I used invalid props that are not used).

canvaskit.js:251 Uncaught TypeError: Cannot read properties of null (reading 'rangeMin')
    at Ob (canvaskit.js:251:1)
    at canvaskit.wasm:0x31efb
    at canvaskit.wasm:0x25d627
    at canvaskit.wasm:0x522836
    at canvaskit.wasm:0xce89d
    at Object._MakeGrContext (canvaskit.js:186:1)
    at a.MakeWebGLContext (canvaskit.js:15:1)
    at a.MakeWebGLCanvasSurface (canvaskit.js:18:1)
    at SkiaDomView.onLayoutEvent (SkiaBaseWebView.js:47:1)
    at Platform.web.js:21:1

Version

1.2.3

Steps to reproduce

git clone https://github.com/YOEL311/storybookPublic
cd storybookPublic
git switch main
yarn
yarn storybook

go to the storybook in Browser
change the props in the Simple story

Snack, code example, screenshot, or link to a repository

https://github.com/YOEL311/storybookPublic

image

@whistlecube
Copy link

whistlecube commented Sep 19, 2024

I've been encountering this too. It doesn't error if you delay loading any skia components by ~500ms or more. I would assume this means WithSkiaWeb is prematurely loading its children before the WASM is truly loaded. Can we get some input @wcandillon ? Thanks

EDIT:
I fixed it in my case by preventing re-renders caused by parent component. This is still unexpected behaviour I think, but if you encounter this, try checking if you have anything causing re-renders during the loading of the WASM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants