ahillss

Yeah it's a bit hard to test fps without a window or rendering. Alternately you could test the time it takes to loop. Here's all the default plugins, with as...

The previous test with the window/rendering and removed plugins still has the issue. I am testing it with the `MinimalPlugins` now. It loops 60 times a second and prints the...

The problem doesn't seem to occur with only MinimalPlugins (after running for a day).

I've had the problem occur on two different win 10 machines, and tried running cargo clean. It can take quite a while to occur, I'll try come up with a...

> We can probably rule out the World, the App and everything that is within the MinimalPlugins. My guess is that the bevy_winit is at fault here, but not sure...

I noticed something while putting together the [multiple windows test](https://github.com/ahillss/bevy_framerate_loss_tests/tree/master/multiple_window_render), if one window visible and the rest are minimised, the visible window's frame rate drops until the others are made...

I ran the [multiple windows without rendering](https://github.com/ahillss/bevy_framerate_loss_tests/tree/master/multiple_window_norender), for a couple of days, I didn't notice any framerate loss. But it can be hard to tell since the framerate without rendering...

I hadn't notice the memory leakage. I tested it with window_render, it seems to happen when a window is minimised, and the leak rate increases for each additional minimised window....

I updated the [examples](https://github.com/ahillss/bevy_framerate_loss_tests) for 0.13. The frame rate loss issue still persists, but the memory seems to leak much slower now. I also noticed after the frame rate has...