[AD] [ alleg-Bugs-3395632 ] Memory leak in osxgl.m |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
- To: SourceForge.net <noreply@xxxxxxxxxx>
- Subject: [AD] [ alleg-Bugs-3395632 ] Memory leak in osxgl.m
- From: SourceForge.net <noreply@xxxxxxxxxx>
- Date: Tue, 23 Aug 2011 18:16:37 +1000
Bugs item #3395632, was opened at 2011-08-21 18:26
Message generated for change (Comment added) made by evanwallace
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105665&aid=3395632&group_id=5665
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Mac OSX
Group: 5.1
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Evan Wallace (evanwallace)
Assigned to: Peter Hull (peterhull90)
Summary: Memory leak in osxgl.m
Initial Comment:
destroy_display in osxgl.m never releases d->ogl_extras->backbuffer
----------------------------------------------------------------------
>Comment By: Evan Wallace (evanwallace)
Date: 2011-08-23 18:16
Message:
The changes that I am considering are pretty major (large refactoring).
What is the preferred channel for discussing them?
----------------------------------------------------------------------
Comment By: Evan Wallace (evanwallace)
Date: 2011-08-23 08:08
Message:
Funnily enough, most of the work seems to have been done already (in
aintern_opengl.h and ogl_display.c). I am cooking up a patch at the moment.
If all goes to plan I will be done within 24 hours.
----------------------------------------------------------------------
Comment By: Peter Hull (peterhull90)
Date: 2011-08-22 20:56
Message:
I agree, there could be a common 'free_ogl_extras' function.
----------------------------------------------------------------------
Comment By: Evan Wallace (evanwallace)
Date: 2011-08-21 18:31
Message:
A lot of the code in osxgl.m is similar to the code in wgl_disp.c, but the
code in wgl_disp.c seems to be far less buggy. Maybe the common
functionality could be collected somewhere?
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105665&aid=3395632&group_id=5665