# glfwOpenWindow creates 2 threads

**URL:** <https://discourse.glfw.org/t/glfwopenwindow-creates-2-threads/298>\
**Category:** support\
**Created:** [December 6, 2010, 11:16pm UTC](https://discourse.glfw.org/t/glfwopenwindow-creates-2-threads/298 "2010-12-06T23:16:54Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![system](https://canada1.discourse-cdn.com/flex035/uploads/glfw/original/1X/b8cdefe6b61b8d5aee6c43b2c56e9cf5eabecfe4.svg) [@system](https://discourse.glfw.org/u/system)\
**Post date:** [December 6, 2010, 11:16pm UTC](https://discourse.glfw.org/t/glfwopenwindow-creates-2-threads/298/1 "2010-12-06T23:16:54Z")

</div>

**anonymous** wrote on [Monday, December 06, 2010](https://sourceforge.net/p/glfw/discussion/247562/thread/ea420a8d/#3001):

Windows 7 x64 Visual Studio 2010 Debug Win64

glfwOpenWindow creates 2 threads, one of them never exits, and neither does  
the whole process.

I am calling it from a console application and monitoring the threads  
creatiion in the debugger. A minimal blank screen example from the user’s  
guide, once closed, I call glfwTerminate(); and return 0; rather than EXIT,  
because it’s up to the main console App to finish and so it does, but the the  
console stays open and the process won’t exit. So I have to force close the  
console window manually. The orphan thread exits with an error code. What has  
it been doing?

---

<div class="post-metadata">

**Author:** ![system](https://canada1.discourse-cdn.com/flex035/uploads/glfw/original/1X/b8cdefe6b61b8d5aee6c43b2c56e9cf5eabecfe4.svg) [@system](https://discourse.glfw.org/u/system)\
**Post date:** [December 7, 2010, 1:09am UTC](https://discourse.glfw.org/t/glfwopenwindow-creates-2-threads/298/2 "2010-12-07T01:09:57Z")

</div>

**[elmindreda](https://sourceforge.net/u/elmindreda/)** wrote on [Tuesday, December 07, 2010](https://sourceforge.net/p/glfw/discussion/247562/thread/ea420a8d/#6391):

Where in glfwOpenWindow are the threads created?