Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FreeTypeFont not freeing d_fontData correctly #60

Closed
Ident opened this issue Jun 22, 2006 · 3 comments
Closed

FreeTypeFont not freeing d_fontData correctly #60

Ident opened this issue Jun 22, 2006 · 3 comments

Comments

@Ident
Copy link
Member

Ident commented Jun 22, 2006

Original report by Anonymous.


Automatic migration. Original reporter: "nightwolf"

In file CEGUIFreeTypeFont.cpp, line 375, the class member d_fontData is freed by calling the Release() method, which is not correct and produces errors when using a custom memory manager.

Please free the d_fontData member using unloadRawDataContainer() from the current resource provider, allowing custom resource providers to free the container themselves.

If the custom memory manager pads the memory buffers, thus returning slightly different pointers from the ones returned by the CRT, this bug causes an exception to be raised in debug mode by the runtime library itself.

Reproducibility: always

OS: Windows, OS build: XP, Platform: PC

@Ident
Copy link
Member Author

Ident commented Jun 29, 2006

Original comment by Anonymous.


Original reporter: zap

Here is a patch file that fixes two things:

  • Calls unloadRawDataContainer() as suggested above
  • Fixes for infinite looping in some special cases in FreeTypeFont.cpp

@Ident
Copy link
Member Author

Ident commented Jul 9, 2006

Original comment by Anonymous.


Original reporter: spannerman

This patch has been tested successfully as described here:
http://www.cegui.org.uk/phpBB2/viewtopic.php?t=1687

@Ident
Copy link
Member Author

Ident commented Jul 23, 2006

Original comment by Anonymous.


Original reporter: lindquist

Patch has been applied to svn :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant