Jump to content
  • Advertisement
Sign in to follow this  
Zervoxe

Angelscript stdstring

This topic is 2074 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

Angelscript in the latest revisions seems to have snuck in a memory leak into stdstring implementation. Atleast Esenthel Engine's memory leak detector seems to find that somewhere inside it is when using string inside angelscript.

Edited by Zervoxe

Share this post


Link to post
Share on other sites
Advertisement

Ok I see, its because of the string factory, I actually have to disable it to prevent those messages from popping up.

Not sure how Esenthel Engine is doing his memory leak detection but it is annoying as hell.

 

Although I notice CleanupEngineStringPool isn't being called on application shutdown. Shouldn't the breakpoint still be activated?

Edited by Zervoxe

Share this post


Link to post
Share on other sites

Perhaps you need to bring this up with Andre Santee? I'm not sure how he has integrated AngelScript within the Esenthel engine.

Share this post


Link to post
Share on other sites

ok, but who is Andre Santee?

oh Ethanon engine, well its quite different from Esenthel Engine though. :)

Edited by Zervoxe

Share this post


Link to post
Share on other sites

My mistake. The names are so similar :)

 

Is AngelScript pre-integrated in Esenthel, or did you do that yourself?

 

I don't know how the Esenthel engine works, but I imagine the memory leak detection routine it has might be executed before the script engine is released. Most likely the memory leak detection is executed as part of the destruction of some global object. In C++ it is difficult to define the order in which global objects are destroyed, so if the AngelScript is also stored as a global object it is quite possible that the memory leak detection runs before the engine is destroyed.

 

The script engine will only call the CleanupEngineStringPool callback when it is about to be destroyed (it's called from within the engine destructor).

Share this post


Link to post
Share on other sites
Sign in to follow this  

  • Advertisement
×

Important Information

By using GameDev.net, you agree to our community Guidelines, Terms of Use, and Privacy Policy.

GameDev.net is your game development community. Create an account for your GameDev Portfolio and participate in the largest developer community in the games industry.

Sign me up!