<p>I have got a weird bug that I cannot figure out. The Apple forums were not too helpful.
I updated my MacBookPro (Retina, early 2015) to the newest OS X Sierra. My code ran fine before, now when I call <code>glfwCreateWindow(mWidth, mHeight, mTitle, nullptr, nullptr);</code>, I get following error:</p>

<pre><code>&gt; ERROR: Setting &lt;private&gt; as the first responder for window&lt;private&gt;,but it is in a different window ((null))! This would
&gt; eventually crash when the view is freed. The first responder will be
&gt; set to nil.
</code></pre>

<p>I have got no idea, why my program does not work and yes, I have set the glfw to be forward compatible.</p>

<p>P.S. computer info:</p>

<ul>
<li>MacBook Pro (Retina 13 inch, early 2015)</li>
<li>CPU: 2.7 GHz Intel core i5</li>
<li>GPU: Intel Iris Graphics 6100 1536 MB</li>
</ul>

CC BY-SA 3.0
2016-10-23T22:09:37.427Z
Are you able to include your code in the question? I recommend removing most of the code until you stop getting the error message, so you can then provide just enough code to cause the error message. This will help narrow down the source of the problem and is likely to make it easier to answer your question.
trichoplax is on Codidact now
CC BY-SA 3.0
2016-10-24T06:58:24.050Z
The problem is not my Code, it used to work fine with OS X El Capitan. The Error I get has something todo within the underlaying window management of OS X Sierra. I have contacted Apple already and they are working on resolving the issue
string111
CC BY-SA 3.0
2016-10-24T12:55:40.133Z
If there's some aspect of your code that worked with the old version but doesn't work with the new version, then we would need to see your code to narrow down what needs to change to work with the new version. If the problem is a bug in closed source software provided by a company, then that would make this question off topic here as we have no way of fixing the problem. If you think there's a chance it is the first, providing a [minimal working example](http://meta.computergraphics.stackexchange.com/questions/126/should-we-require-minimal-working-examples-mwes) will allow us to investigate.
trichoplax is on Codidact now
CC BY-SA 3.0
2016-12-12T13:03:18.890Z
I have the same issue with a PDF view when using full screen. To what I found else on the net this looks like a Sierra bug :-(
qwerty_so
<opengl>
Error when calling glfwCreateWindow() on OS X after updating to Sierra
string111
# Error when calling glfwCreateWindow() on OS X after updating to Sierra

(Asked by: username_0 on 2016-10-20)

I have got a weird bug that I cannot figure out. The Apple forums were not too helpful.
I updated my MacBookPro (Retina, early 2015) to the newest OS X Sierra. My code ran fine before, now when I call `glfwCreateWindow(mWidth, mHeight, mTitle, nullptr, nullptr);`, I get following error:

```
> ERROR: Setting <private> as the first responder for window<private>,but it is in a different window ((null))! This would
> eventually crash when the view is freed. The first responder will be
> set to nil.

```

I have got no idea, why my program does not work and yes, I have set the glfw to be forward compatible.

P.S. computer info:

* MacBook Pro (Retina 13 inch, early 2015)
* CPU: 2.7 GHz Intel core i5
* GPU: Intel Iris Graphics 6100 1536 MB

**Tags:** opengl

> **Comments:**
> **username_1**: Are you able to include your code in the question? I recommend removing most of the code until you stop getting the error message, so you can then provide just enough code to cause the error message. This will help narrow down the source of the problem and is likely to make it easier to answer your question.  
> **username_0**: The problem is not my Code, it used to work fine with OS X El Capitan. The Error I get has something todo within the underlaying window management of OS X Sierra. I have contacted Apple already and they are working on resolving the issue  
> **username_1**: If there's some aspect of your code that worked with the old version but doesn't work with the new version, then we would need to see your code to narrow down what needs to change to work with the new version. If the problem is a bug in closed source software provided by a company, then that would make this question off topic here as we have no way of fixing the problem. If you think there's a chance it is the first, providing a [minimal working example](http://meta.computergraphics.stackexchange.com/questions/126/should-we-require-minimal-working-examples-mwes) will allow us to investigate.  
> **username_2**: I have the same issue with a PDF view when using full screen. To what I found else on the net this looks like a Sierra bug :-(  

---

## 0 answers

