• Announcements

    • khawk

      Download the Game Design and Indie Game Marketing Freebook   07/19/17

      GameDev.net and CRC Press have teamed up to bring a free ebook of content curated from top titles published by CRC Press. The freebook, Practices of Game Design & Indie Game Marketing, includes chapters from The Art of Game Design: A Book of Lenses, A Practical Guide to Indie Game Marketing, and An Architectural Approach to Level Design. The GameDev.net FreeBook is relevant to game designers, developers, and those interested in learning more about the challenges in game development. We know game development can be a tough discipline and business, so we picked several chapters from CRC Press titles that we thought would be of interest to you, the GameDev.net audience, in your journey to design, develop, and market your next game. The free ebook is available through CRC Press by clicking here. The Curated Books The Art of Game Design: A Book of Lenses, Second Edition, by Jesse Schell Presents 100+ sets of questions, or different lenses, for viewing a game’s design, encompassing diverse fields such as psychology, architecture, music, film, software engineering, theme park design, mathematics, anthropology, and more. Written by one of the world's top game designers, this book describes the deepest and most fundamental principles of game design, demonstrating how tactics used in board, card, and athletic games also work in video games. It provides practical instruction on creating world-class games that will be played again and again. View it here. A Practical Guide to Indie Game Marketing, by Joel Dreskin Marketing is an essential but too frequently overlooked or minimized component of the release plan for indie games. A Practical Guide to Indie Game Marketing provides you with the tools needed to build visibility and sell your indie games. With special focus on those developers with small budgets and limited staff and resources, this book is packed with tangible recommendations and techniques that you can put to use immediately. As a seasoned professional of the indie game arena, author Joel Dreskin gives you insight into practical, real-world experiences of marketing numerous successful games and also provides stories of the failures. View it here. An Architectural Approach to Level Design This is one of the first books to integrate architectural and spatial design theory with the field of level design. The book presents architectural techniques and theories for level designers to use in their own work. It connects architecture and level design in different ways that address the practical elements of how designers construct space and the experiential elements of how and why humans interact with this space. Throughout the text, readers learn skills for spatial layout, evoking emotion through gamespaces, and creating better levels through architectural theory. View it here. Learn more and download the ebook by clicking here. Did you know? GameDev.net and CRC Press also recently teamed up to bring GDNet+ Members up to a 20% discount on all CRC Press books. Learn more about this and other benefits here.
Sign in to follow this  
Followers 0
Aggrav8d

as memory leaks?

8 posts in this topic

I'm into the final stages of development on my project so I thought i'd run it through paul nettle's memory manager (www.fluidstudios.com) and it got very annoyed with angelscript (currently working with 1.10.1WIP1). I will resolve the memory leaks on my end, I just thought it was worth mentioning to whom it may concern. :)
0

Share this post


Link to post
Share on other sites
I'm not aware of any memory leaks in AngelScript. Would you mind helping me by pointing out in what situations you get memory leaks? Neither of my test frameworks report any memory leaks.

I can't access fluidstudios.com from here (it's barred by the company's proxy) so I can't check out Paul's memory manager. How does it work? Is it free?
0

Share this post


Link to post
Share on other sites
It is free and you just plug it in somewhere convenient like as_config.h and recompile. it doesn't actually optimize memory allocation by partitioning of small sections from a few large allocations - rather it works a lot like boundschecker to veryify that every single byte allocated has been freed & can even tell you when you are allocating blocks bigger than is actually needed. The mmgr complains some 20 times if I

a=asCreateScriptEngine(ANGELSCRIPT_VERSION);
delete a;

and once or twice for every Register...() call.

You can also get it here: ftp://ftp.flipcode.com/code/mmgr.zip
0

Share this post


Link to post
Share on other sites
I plugged in Paul's memory manager in the library and gave it a run. I didn't find any memory leaks, but there are a few places where AngelScript apparently deletes memory that it never allocated. I'm currently tracking these down.

The first one I found was not in AngelScript but in MSVC++'s std::string's destructor.

Did you find any actual memory leaks in AngelScript?
0

Share this post


Link to post
Share on other sites
Quote:
Original post by Aggrav8d
The mmgr complains some 20 times if I

a=asCreateScriptEngine(ANGELSCRIPT_VERSION);
delete a;

and once or twice for every Register...() call.


I hope you're not actually calling delete on the script engine? You should be calling a->Release();

I don't get any complaints on the Register...() calls.
0

Share this post


Link to post
Share on other sites
After removing the illegal delete in std::string, the memory manager no longer reports any problems with the AS library or the test framework.

AngelScript doesn't actually use std::string, so the problem actually not with the library itself.

Let me know if you still have trouble with AS.

Regards,
Andreas
0

Share this post


Link to post
Share on other sites
Good to know. ...i'm embarassed to say that, yes, i was deleting it. I guess I didn't read the doccos closely enough. That was the source of the problems. Why isn't the destructor protected or private?
0

Share this post


Link to post
Share on other sites
Good question. I simply forgot about it. I'll add it to 2.0.0. I won't add it to 1.10.1 because it changes the interface.
0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0