Dzmitry Malyshau

@arbrk1 Could you please provide the output of your `glxinfo`?

Ok, I see `GL_ARB_framebuffer_sRGB`, so it's not simply the lack of `srgb` support.

Wow, great investigation, @arbrk1! So, if I understand correctly, Glutin needs to take the client extensions into account under some conditions (e.g for the compatibility context)? Cc @tomaka > On...

@daboross that's not sRGB. That happens when your PSO definition is lacking the output target component. Since the definition comes from `gfx_graphics`, it surely has a bug in there then.

ok, I briefly looked at `gfx_graphics` and didn't see anything wrong in there. the bug might be related to https://github.com/gfx-rs/gfx/pull/927 , especially considering the weird slot 255 in the error....

That error is fixed in GFX latest published version. Regards, Dzmitry > On Jun 28, 2016, at 5:47, Joel W Kall [email protected] wrote: > > That code gives me thread...

@bvssvni looks to be happening in the winit's X11 window destructor. `PoisonError` is for mutex being locked twice without unlocking. I suggest filing an issue to winit.

I don't like run-time argument here, because: - you always know in advance - no need to link and compile multiple instances of gl-rs

You proposed to add a switch to the `WindowSettings` [here](https://github.com/PistonDevelopers/window/issues/56). This would be a run-time switch, so all the gl is still going to be linked and compiled. I vote...

Turns out the intersection here is expected. The whole chain of allocation is spawned by a single small allocation. `alloc_chunk` tries to allocate `MIN_BLOCKS_PER_CHUNK` number of block sizes, doesn't find...