Matthew Amato
Matthew Amato
As a test, I updated the `CesiumViewer.js` sample app to be 3 lines long: ```js window.CESIUM_BASE_URL = "../../Source/"; import { Viewer } from "../../Source/Cesium.js"; new Viewer("cesiumContainer"); ``` Hangs (almost) every...
I tried enabling/disabling various Viewer features one at a time to determine if something was triggering a bug (either in our code or Chrome) but it seems completely non-deterministic. On...
I think we're out of options from our side and given this works everywhere by Chrome/Chromium on Linux, I'm going to open a Chromium issue to hopefully get some help.
I checked all the way back to 1.70 and it's still broken, so definitely not a regression anywhere near our end..
This gets worse. The same thing that crashes constantly locally for me works when on S3, this could point to a possible race condition related to the network stack? This...
@kring pointed out that `createTaskProcessorWorker.js` seems to be the last file successfully loaded right before everything hangs. I've verified that this is the case, but it seems to be a...
Another thing I noticed loading Cesium Viewer is that `approximateTerrainHeights.json` is the first item that the initiator is the VM and not an import from a JS file (i.e. I...
Looks like this is actually working again.
That's what @kring and @lilleyse are still seeing as well. I have no idea what changed on my machine that it's suddenly working again.
UPDATE: I rebooted and it's broken on my machine again. I have no idea what anything means anymore.