Simon's

Results 9 comments of Simon's

![image](https://user-images.githubusercontent.com/17590947/175889416-70809900-f6bd-44a0-b0db-5348f8ffa289.png) I checked the possible panic at FEngine::Loop,is the crash happened here?

yes, I've tried to print the emit messages to our app log, but I've found that sometimes it didn't invoke the panic function. ![截屏2022-06-30 10 53 17](https://user-images.githubusercontent.com/17590947/176582806-73d66d20-f3d5-419a-b264-01d7e79347ac.png) If all panic...

> @starccode Are you able to show us the full log output of your program when it crashes? no problem, I'm trying to collect the crash log, I will show...

Recently, I've collected some TPanic crash macro output log, here it is: 1. Panic in MetalTexture:474 reason: Could not create Metal texture. Out of memory? 2.Panic in acquireDrawable:145 reason: Could...

The stack trace as following: It crashed because of bad access of NULL value

I'm using an old version 1.21.2. And It seems raise error since glBindBuffer()

And I run the code at version 1.25.0 of filament gltf-viewer sample. The GLError disappear, but receive a warning: ![warning](https://user-images.githubusercontent.com/17590947/199153276-8d85eb10-5318-4f8a-80cc-251219b7031d.png) And besides, the memory increase constantly. ![memory](https://user-images.githubusercontent.com/17590947/199153502-f7d15f20-3b08-42ba-a3e0-1f611a0f7dac.png) I analyze it...

I've just run the sample project "gltf-Viewer" without any extra code, and I found that the memory also increase at openGL backend as shown above. But it works right at...