Andreas Reich

We use [`default_memory_pool`](https://arrow.apache.org/docs/cpp/api/memory.html#_CPPv4N5arrow19default_memory_poolEv) everywhere so far, not sure if it's possible (or safe) to shut it down entirely.

Thanks for your interest in using Rerun. Unfortunately, we don't have anything planned regarding low latency & lossy transmission in the mid term (next few months) and it's very unlikely...

yep, we definitely shouldn't crash and instead try to forward an error if needed As to actual source of the issue (and how to show it better): this might be...

Hmm yeah then it is probably something that wgpu could do different. There's unfortunately [quite many](https://github.com/gfx-rs/wgpu/issues?q=sort%3Aupdated-desc+is%3Aissue+is%3Aopen+label%3A%22platform%3A+wayland%22) wayland issues there that are waiting for contributors to look into (the maintainers either...

Huh, strange why would docs fail for 0.29 Oo. They're up for 0.28 and the struct hasn't changed. Yes, indeed you should be able to adjust which gpu is choosen...

Yeah I think that "this surface doesn't have any formats" should be an exclusion criteirum for an adapter. That ofc still leaves the separate issue of the surface mysteriously not...

for reference, found this issue on `egl-wayland` today which might be related. However, the user there reports that `glxgears` has the issue as well which wasn't the case for you...

This probably relevant fix landed in wgpu 23.0.1: https://github.com/gfx-rs/wgpu/pull/6510 this fixes vulkan sometimes incorrectly being identified as a viable adapter we have to update wgpu in the egui lock file...

wgpu 23.0.1 is now on egui `master` branch. @VorpalBlade could you please check if that makes any difference for you?

nice! That's _probably_ GLES: the way we run with wgpu here it tries through all adapters before it settles on one. If you run with `RUST_LOG=debug` it should show up...