std::unique_ptr going out of scope causes access violation?

I've been trying to make a plugin for Assimp for a while now, and for the most part, it works until the end of the function, which by then an exception is thrown about the std::unique_ptr variable I used. I compared its use to other plugins and I'm... baffled. It seems to be okay, I thought?

My apparently faulty std::unique_ptr: assimp/ISM2Loader.cpp at master * NebuHiiEjamu/assimp * GitHub

Working code with unique_ptr by someone else: assimp/ASELoader.cpp at master * NebuHiiEjamu/assimp * GitHub

Presumably the pointer that pIoHander->Open() returns should not be deleted, so a unique_ptr doesn't apply here.
If you were just using a regular pointer would you call delete on it at the end of the function? I suspect not.
E.g., in C we don't free a FILE* at the end of a function.

Hmm... I'll give it a try with a regular pointer. Not sure how ASELoader uses it differently though... Maybe I'm supposed to close it

I didn't look at the other code last time. Now that I look, I wonder if perhaps that code is also making a mistake and just getting "lucky" (or not, depeding on how you look at it).


I would read up on exactly how those classes (IOHandler and IOStream) are supposed to be used. You probably do have to close it.

That's certainly awkward, but yeah I'll look. Thanks

Just try opening with:

Code:

---

IOStream *io = pIOHandler->Open(pFile.c_str(), "rb");

---

and closing it with

Code:

---

pIOHandler->Close(io);

---

Have you tried running the other code? Does it seem to run properly?

EDIT:
I looked at the documentation, and it seems like your original code should probably have worked. I don't know what's going on.

Assimp: Assimp::IOSystem Class Reference

Assimp: Assimp::IOStream Class Reference