Closed leon-marzahn closed 3 years ago
Hello. Can you try disabling the "Overwolf" program? That is, OWExplorer.dll per given segfault log.
Is Overwolf essential for your project? How do you use it?
See if turning it off will change the situation, or at least the stack log.
Oh my god, i didn't know OWExplorer is Overwolf. Yes, turning it off fixed it actually. So Overwolf hooks into games to give information on it, i just didn't expect it to hook into a random glfw context. And also why it would segfault it, i have no idea.
Also which version of the module do you use? Your glfw.createWindow
call looks odd to me, it should be more like
const emitter = { emit: (t, e) => this.emit(t, e) };
const window = glfw.createWindow(640, 480, emitter, 'some title');
in case you use the latest version.
There is class Window that handles a lot of window-related stuff for you, like fullscreen switching for instance.
I think i am using the latest version, and yeah i used th emitter incorrectly, i just noticed thanks! And also i just used low level to see if it's an issue in the Window class.
To be honest, this hook-related segfault issue is not the first one I heard of. So there might be a bigger picture or some low-level issue behind it.
The other known hook problem was with Nahimic A-Volume, and I have no idea what is wrong with these hooks...
May be one day I might find an answer.
Alright, good luck on that, keep it up :)
I really love this library, but the problem is after creating a window, after some time it throws a segfault. I can theoretically ignore the segfault as it doesn't happen again and doesn't affect the application as far as i can, but it's kind of weird to ignore a segfault.
Segfault:
Code:
Running on Windows x64 - Node 12.16.1 x64 - ES6