Godot version:
Godot 3.1 alpha 18d06b9
OS/device including version:
Windows 10
Issue description:
Thread 1 received signal SIGSEGV, Segmentation fault.
0x00000000017491ec in VisualServerWrapMT::init() ()
VisualServerWrapMT::init(VisualServerWrapMT * const this) (d:\ubuntu\src\godot\servers\visual\visual_server_wrap_mt.cpp:122)
OS_Windows::initialize(OS_Windows * const this, const OS::VideoMode & p_desired, int p_video_driver, int p_audio_driver) (d:\ubuntu\src\godot\platform\windows\os_windows.cpp:1356)
Main::setup2(Thread::ID p_main_tid_override) (d:\ubuntu\src\godot\main\main.cpp:1086)
Main::setup(const char * execpath, int argc, char ** argv, bool p_second_phase) (d:\ubuntu\src\godot\main\main.cpp:1034)
widechar_main(int argc, wchar_t ** argv) (d:\ubuntu\src\godot\platform\windows\godot_win.cpp:138)
_main() (d:\ubuntu\src\godot\platform\windows\godot_win.cpp:172)
main(int _argc, char ** _argv) (d:\ubuntu\src\godot\platform\windows\godot_win.cpp:189)
Steps to reproduce:
Run editor, crash.
@vnen #23434.
Same in Linux compiling with latest changes.
ERROR: initialize: Condition ' ctxErrorOccurred || !p->glx_context ' is true. returned: ERR_UNCONFIGURED
At: platform/x11/context_gl_x11.cpp:188.
handle_crash: Program crashed with signal 11
Dumping the backtrace. Please include this when reporting the bug on https://github.com/godotengine/godot/issues
[1] /usr/lib/libc.so.6(+0x37e00) [0x7fd92e087e00] (??:0)
[2] VisualServerWrapMT::init() (??:0)
[3] OS_X11::initialize(OS::VideoMode const&, int, int) (??:0)
[4] Main::setup2(unsigned long) (??:0)
[5] Main::setup(char const, int, char*, bool) (??:0)
[6] ./godot.x11.tools.64(main+0x9f) [0x56527b5173f8] (??:0)
[7] /usr/lib/libc.so.6(__libc_start_main+0xf3) [0x7fd92e074223] (??:0)
[8] ./godot.x11.tools.64(_start+0x2e) [0x56527b51728e] (??:0)
-- END OF BACKTRACE --
Aborted (core dumped)
EDIT: I solved adding this line on os_x11.cpp:
345 visual_server = memnew(VisualServerRaster);
Working on a fix.
Sorry about that.
My apologies as well -- I was the one who suggested it might be a memory leak there.
Most helpful comment
Sorry about that.