Emil Ernerfeldt

I've tried `run_return` in the past, and it caused two problems: * https://github.com/emilk/egui/issues/755 * Very jittery resizing of windows So I reverted it in https://github.com/emilk/egui/commit/3e1db880dcba1db061e0b0208d73fce22896d055

Reopened, because this is something a lot of people want. We need to either change how `winit::EventLoop::run` works, or fix the problems with `winit::EventLoop::run_return`, or test an alternative, like [`tao`](https://github.com/tauri-apps/tao)

This will finally be fixed in https://github.com/emilk/egui/pull/1889 🥳

There is nothing stopping you from using `run_return` with egui_glow 0.18 - just follow the structure in my PR! The PR is for `eframe`, and if it works well I...

How annoying! On Mac it works well. Is it the same using `egui-wgpu` as the backend? Perhaps add a few breakpoints and try to find out what goes wrong!

@HideakiAtsuyo since this affects your computer and you are a programmer, maybe you can investigate?

You are not the maintainer, but you can become a contributor. I have a thousand things to do that has a higher priority, so if you want this to be...

Definitely a bug. Even shorter repro: ``` egui::SidePanel::right("sidebar") .frame(egui::Frame::default().fill(egui::Color32::WHITE)) .show(ctx, |ui| { egui::ScrollArea::vertical().show(ui, |ui| { ui.label("aaaaaaaaaaaaaaaaaaaaaaaaaaaaaa"); }); }); ```

Before making assumptions about what is the slow part of the code, run an profiler and find out! You may be surprised. Each point in a line that the Plot...

To get a _very rough_ feel for where the milliseconds are being spent you can use `puffin`: https://github.com/emilk/egui/pull/1483 - note that this is no replacement for a REAL profiler.