Home/ Questions/Q 6770673
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-26T15:20:24+00:00

I have a very strange crash when using the Apple LLVM 3.0 compiler. So

  • 0

I have a very strange crash when using the Apple LLVM 3.0 compiler.
So there is some code, that uses Assimp to load assets and create the scene (I’ve excluded all my code and even then it crashes):

aiScene* ai_scene = const_cast<aiScene*>(aiImportFileFromMemory(fileBuf, fInfo.uncompressed_size, aiProcessPreset_TargetRealtime_MaxQuality, NULL));

delete ai_scene;

Here is the screenshot of the stack trace for GCC:

enter image description here

And here is for LLVM:

enter image description here

In LLVM version destructor is called twice (and probably that’s why I’ve got a crash).

I should also mention that all destructor code is located in header file and crashes only on device (tested on iPod 4 and iPad 2).

Is it a bug in LLVM compiler (probably in generation of arm assembly) or did I miss something?

Edit:

in case someone has similar problem use aiReleaseImport(scene) instead of delete scene;

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    You are not supposed to delete that pointer at all. Read the documentation. It clearly states that you should not attempt to free it in any way.

    If the call succeeds, the contents of the file are returned as a
    pointer to an aiScene object. The returned data is intended to be
    read-only, the importer keeps ownership of the data and will destroy
    it upon destruction. If the import fails, NULL is returned. A
    human-readable error description can be retrieved by calling
    aiGetErrorString().

    And in addition, the documentation explicitly states that it’s read-only, so do not const_cast the const away.

    • 0