I’ve got a crash on a C++ mac debug compilation (virtual machine). It used to work but after an upgrade, not anymore.
This same project with the same haxelib list works on windows.
Here is the stack :
Starling.hx:462: [Starling] Display Driver: OpenGL Vendor=Apple Inc. Version=2.1 APPLE-11.0.7 Renderer=Apple Software Renderer GLSL=
Called from ApplicationMain::main ApplicationMain.hx line 80
Called from ApplicationMain::create ApplicationMain.hx line 102
Called from *::_Function_1_1 haxe/Timer.hx line 244
Called from starling.core.Starling::initialize starling/core/Starling.hx line 448
Called from starling.core.Starling::initializeGraphicsAPI starling/core/Starling.hx line 464
Called from starling.core.Starling::updateViewPort starling/core/Starling.hx line 583
Called from openfl.display.Stage3D::set_x openfl/display/Stage3D.hx line 266
Called from openfl.display3D.Context3D::__updateBackbufferViewport openfl/display3D/Context3D.hx line 1302
Called from openfl.display3D.Context3D::__setViewport openfl/display3D/Context3D.hx line 1090
Called from openfl._internal.stage3D.GLUtils::CheckGLError openfl/_internal/stage3D/GLUtils.hx line 20
Error : Error calling openGL api. Error: 1280
And the haxelib list
format: 3.2.1 [3.3.0]
hxcpp: 3.4.2 [3.4.49]
lime: 3.5.0 3.5.2 [3.7.4]
openfl-samples: 4.5.0 4.5.1 [4.7.0]
openfl: 4.5.0 4.5.2 [4.8.1]
starling: 1.8.2 1.8.3 [1.8.7]
Maybe it has to do with recent changes, I don’t know, thanks for your help.
Try adding this to your install
It works, but I’ve got weird behaviour on the starling demo. The first button becomes black when I come back from a scene. And the benchmark crash the app when I press back.
I’m building my project now, I will let you know.
It crashes as well after a couple of seconds without any usefull runtime errors. it doesn’t seem to crash when doing a specific action.
Thanks, I saw the same thing when re-testing this morning.
I made OpenGL garbage collection fixes in Lime today which resolved this problem. Are you on dev builds?
I tried the last dev version on mac VM, I get this crash report when I changed pages in the menu, has to do with a textfield.dispose() (bitmapfont) it looks like.
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 ??? 000000000000000000 0 + 0
1 com.early_melon 0x00000001016ce6a5 lime::_backend::native::NativeGLRenderContext_obj::deleteBuffer(hx::ObjectPtrlime::graphics::opengl::GLObject_obj) + 101
2 com.early_melon 0x0000000100cbd044 openfl::display3D::VertexBuffer3D_obj::dispose() + 244
3 com.early_melon 0x0000000100abf70d starling::display::QuadBatch_obj::__destroyBuffers() + 301
4 com.early_melon 0x0000000100abdc0f starling::display::QuadBatch_obj::dispose() + 431
5 com.early_melon 0x00000001009ff81a starling::text::TextField_obj::dispose() + 794
6 com.early_melon 0x0000000101b3818b menus::MenuPage_obj::remove() + 475
That’s the very latest Lime and OpenFL development versions, after running
lime rebuild mac first?
It works !
I had just updated lime and openfl, it’s working with
lime rebuild mac
Thank you and sorry about that.
Oh, no problem! Glad its working