You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The below minimal sample looks fine. It does work when serving with flutter run or a local Python web server. But when served from a Docker container, the app crashes and the browser console spams errors.
Expected behavior
Image displayed. No crash.
Reproduction steps
Serve the minimal sample app from a docker container.
a. build: docker build . -t bug
b. run: docker run -p 8080:8080 bug
main.dart.js:3193 Uncaught Error: SecurityError: Failed to execute 'texImage2D' on 'WebGLRenderingContext': The image element contains cross-origin data, and may not be loaded.
Then, a whole bunch of these:
main.dart.js:3193 Uncaught Error: RuntimeError: memory access out of bounds at canvaskit.wasm:0xd89f at canvaskit.wasm:0x83f5 at canvaskit.wasm:0x44a9e5 at canvaskit.wasm:0x723cd at Tb.<anonymous> (canvaskit.js:116:52) at Tb.<anonymous> (canvaskit.js:156:256) at new PictureRecorder (canvaskit.js:105:189) at cS.iG (main.dart.js:11501:13) at xJ.$0 (main.dart.js:11178:7) at Object.Oa (main.dart.js:1109:17)
The complete stack traces are very long and unreadable. See an export here: browser-console.log
Depending on the surrounding app, the errors are also different, but go into a similar direction.
🐛 Bug Report
The below minimal sample looks fine. It does work when serving with
flutter run
or a local Python web server. But when served from a Docker container, the app crashes and the browser console spams errors.Expected behavior
Image displayed. No crash.
Reproduction steps
a. build: docker build . -t bug
b. run: docker run -p 8080:8080 bug
localhost:8080
.Sample
`main.dart`
`Dockerfile`
Logs
First, a whole bunch of these:
main.dart.js:3193 Uncaught Error: SecurityError: Failed to execute 'texImage2D' on 'WebGLRenderingContext': The image element contains cross-origin data, and may not be loaded.
Then, a whole bunch of these:
The complete stack traces are very long and unreadable. See an export here: browser-console.log
Depending on the surrounding app, the errors are also different, but go into a similar direction.
Uncaught : Null check operator used on a null value
in here browser-console_2.log.I have also seen something along the lines of (reciting from memory) Function Argument Missmatch Error, but cannot reproduce that case at the moment.
Configuration
Version: 3.4.1
Platform: web
The text was updated successfully, but these errors were encountered: