I’m using GLFW for the first time. Pulled the latest stable release (3.2.1) and I’m using the example code found on the GLFW website:
/* Initialize the library */
/* Create a windowed mode window and its OpenGL context */
window = glfwCreateWindow(640, 480, "Hello World", NULL, NULL);
/* Make the window's context current */
/* Loop until the user closes the window */
/* Render here */
/* Swap front and back buffers */
/* Poll for and process events */
There’s a fairly long delay (20 seconds or so) on the call to choosePixelFormat() (wgl_context.c) - nativeCount has a value of 627 and it seems to just take a long time in the for loop.
There’s no delay if I use freeGLUT to create a window or if I just create a window directly with WinAPI calls (CreateWindow, etc) and set up the PFD myself.
I’m using Windows 10, tried it first with Visual Studio 2015 and then in 2017. Graphics card is NVidia Quadro M6000.
I did slightly modify the above code to add a call to initialize glew, but having this call or not did not change the delay.
That’s a ridiculously long time. Can you get more detailed information on what inside of
choosePixelFormat is taking so long and whether it’s on the first iteration or across them all?
Hi Elmindreda. I apologize about not responding - we ended up just sticking with the Win32 API directly, but we’re back at a point where we want to use GLFW for our project and I wanted to revisit this because it’s still occurring.
I timed it out to 13 seconds from the moment I start the application to when the window appears. The bulk of that time is spent inside choosePixelFormat() in wgl-context.c, iterating through that loop. The loop counter is checked against the value nativeCount, which for me is 672. It doesn’t appear to hang on any particular iteration, at least not the first ten.
When the loop does end, I end up with a usableCount of 180 for what it’s worth.
While running through the loop, _glfw.wgl.ARB_pixel_format conditional always returns true. It does seem odd, because a loop of 672 doesn’t seem like it should take 13 seconds to process. I have to assume it’s getting caught up in one of the other function calls inside that loop (getPixelFormatAttrib), but I’m not sure on which iteration it would be.
Hi Doug, thanks for the reply.
I built the project in Release configuration and ran without debugging, no change. Even running the executable directly outside of VS has no impact.
I could not find a Focus Assist setting anywhere. Perhaps I’m on an older version of Windows 10? Mycompany is slow at releasing these updates.
Unfortunately I think my company restricts updating our drivers on our work laptops. Right now we’re using NVidia Quadro M2000M, and the driver version says 188.8.131.5249. My NVidia control panel says Version 369.49.
It looks like 369.49 was released in Oct 2016. https://www.nvidia.com/download/driverResults.aspx/108579/en-us.
To view your Windows Version number in Start Menu type “system information” and click that. The version number for the April 2018 release is Build 17134 https://en.wikipedia.org/wiki/Windows_10_version_history#Version_1803_(April_2018_Update).
Have you tried running the same executable on a machine not from your work with recent Windows and driver? This may help narrow down the issue.
The large amount of time spent makes me think there is something very different with your system to anything I’m used to seeing.
On my machine if I run a profile in Visual Studio (Analyze->Performance Profiler select CPU) I can drill down into glfwPlatformCreateWIndow (which takes 250ms) to see ChoosePixelFormat takes 174ms. Debugging shows that the nativeCount is 467, and the loop uses the _glfw.wgl.ARB_pixel_format branch of the conditional with a usableCount of 180. You have around 1.5x more pixel formats, but 13 seconds is almost 100 times slower so there’s something odd here.
ChoosePixelFormat calls getPixelFormatAttrib around 20x per loop. This in turn calls wglGetPixelFormatAttribivARB which could be slow on your system for some reason.
Calling wglGetPixelFormatAttribivARB once for all required attributes might improve performance if this is the case by up to 20x, which could get you within reasonable performance times for your setup.
If you’re willing to help test this I could look into doing some work on this area.
Quick update: I just ran the same executable on another machine that has NVidia drivers 148.92 and the window opened immediately. So it’s certainly something specific to my laptop.
As I started looking into this work I noted that the profile I was looking at had ChoosePixelFormat taking 174ms but this was the WIN32 API ChoosePixelFormat. The GLFW function choosePixelFormat was only taking 2ms.
I have a version of the glfw choosePixelFormat which uses only one call to wglGetPixelFormatAttribivARB per format on:
If you pull that array-based-choosePixelFormat (it’s based off master branch so as to make a pull request easier if this works out for you) it might help with your issue, in which case we should raise an issue on Github then I can clean up the code ready for a pull request to GLFW.
Here’s one more thing to look into: https://hero.handmade.network/forums/code-discussion/t/2503-[day_235]_opengls_pixel_format_takes_a_long_time#12672
Some time ago I’ve debugged into nvidia GL implementation to figure out why it takes so long to create GL context. Turns out it was looping all over the game profile settings. Reducing profile list to smaller (by taking from older driver) helped significantly. Still it was in hundreds of msec range, not multiple seconds.
Right - if the time is being spent in ChoosePixelFormat (capital letter start) then this is purely driver related.
If the time is being spent in choosePixelFormat this is GLFW code and whilst the likely problem may be the driver my commit might lower this slightly.
Hello - I tried it again with the changes you provided. There’s a noticeable improvement, it’s down to 4-5 seconds before the window launches. Thank you for the help.
Apologies for the delay.
I’ve submitted a pull request as below, though due to the additional complexity I’m unsure if this it is a wise decision to add to the codebase (you may want to chime in if it’s very useful to you).
These changes have now been merged into the master branch of GLFW and should arrive in version 3.3.
hi i am having a similar problem GLFW window opens up ok on the first run but then after I hit run 3-4 times on Vs Studio 2019 with Windows 10 pro all updated as of may2020 with Nvidia RTX 2070 on a 32gb ram i7 9700k cpu desktop, the GLFW window opening slows down considerably that I had to grab a coffee İ checked my drivers are uptimes uptodate , checked from both device manager also Nvidia geforce experience…When I restart the system or shutdown/ start then it again runs OK for the first 3-4 times and start getting slower both release and debug mode. I also tried the .exe file which actually performs a little better but after6-7 runs then it does the same thing. The code does not nothing just basic window create update and swap …just typically basic code. I have the latest GLFW files and build on my machine… I also contacted Nvidia but no response yet from…not sure what to do…I would really appreciate if you can direct me how to solve this problem
Slow program launches from Visual Studio can be due to VS loading symbols, you can turn this off if needed.
If you’re seeing slow launches when running the executable outside of VS, or from VS with “Start Without Debugging” then it would be worth while looking into whether you see the same slowdown from any of the GLFW examples.
Additionally, profiling the code to find out where the slow down occurs would be useful, Visual Studio has an in-built profiler but you can also use VerySleepy or another profiler.
It’s possible that something else is causing your executable to load slowly, perhaps a virus, so I recommend a virus scan. It could also be that you have an anti-virus program which is scanning your exe before it loads.
hi doug i solved my problem on this after debugging. it was a USB input device call back and my keyboard driver was causing. Apparently this was an issue with certain brands of any USB ınput devices. I had Corsair K55 Keyboard and after updating my drivers opening time came from 20-40 secs to 450-650 milliseconds. I had an issue open on the GitHub site but I closed after that Issue https://github.com/glfw/glfw/issues/1709.
There are some more details over there in case any comes up with a similar problem
Wow, that’s a great find, glad you resolved it.
it was really good debugging session for me and I went thru deep in the codeThanks to people at Nvidia Developer who walked me thru debugging session and GLFW GitHub site & team…one of the members remember that weird USB input device issue & keyboard drivers…I was thinking it was GPU drivers but it happened to be the KeyBoard Lessons learned keep drivers upto date