I've been contacted by ATI representatives and I've sent them the sample application that causes the memory leak on context switch. Can anyone with the recent ATI video card and official drivers try to reproduce this issue on their PCs? I'm attaching the sample application and the sources. The more people test this issue the better understanding of the issue we will have.

Sources:
sources

Application exe:
application

Quote:Original post by silvermace
EDIT: As of the latest OpenGL drivers EXT_framebuffer_object is supported (thanks Boku San) But my point was the NVIDIA developers had a basic prelimary implementation to play with months before Catalyst 5.8 (maybe even a year?)

I agree it was annoying having to wait for FBO support, but keep in mind that nvidia users got it so early from a leaked beta driver. Then the drivers were still beta for a while after that. FBO support on ATI cards started with Cat5.7 drivers. And it was only a few months, the spec was only approved on Jan. 31 of this year. It sure did seem like a year though... (and I've been so busy lately I still haven't had the chance to try FBO out [sad]).

Quote:Original post by wazoo
The more people test this issue the better understanding of the issue we will have.

I'll try to test it out later.

Hi.

I have bought lately Radeon 9550 128/128 and Im starting to regret it.
I have the same problem with often wglMakeCurrent calls. Im trying to create 3D modeller, MDI based, couple of windows representing diferrent ortho mode and perspective view. I need to call wglMakeCurrent on every frame, obviously.
Only solution which I currently see is to create couple of threads, but I cant imagine to make it now, especially when I think about syncronisation required.
Ive been working today with my app for about 2 hours, I've experienced 40mb memory leak from wglMakeCurrent. This is a SHOCK, to let such error survive. Sorry, Im running out of patience too. I've been trying to contact ATI, Customer Care sent me to developer page, but I cant find there any email adress, or link when I can contact someone.

Here is mine simple sample of the problem (contains exe and code in devcpp):
http://rogdush.republika.pl/test.rar
Feel free to check it out and see the growing 4-8kb memory on one sec.

Im looking forward on some response, maybe some one have some additional info concering solution or when ATI would like to take care of that problem?

[Edited by - rogdush on September 12, 2005 9:51:32 PM]

Quote:Original post by rogdush
[...]Im trying to create 3D modeller, MDI based, couple of windows representing diferrent ortho mode and perspective view. I need to call wglMakeCurrent on every frame, obviously.[...]

I don't have anything else to say about wglMakeCurrent problem, but if what you're doing is like a typical 3d modeller setup you don't need to make separate windows for the different views. Just use different viewports.

Quote:Original post by Yann L
The wglMakeCurrent leak has been known for years, comes up on the opengl.org forums every couple of months, and has been reported a billion times to ATI - without any reaction.

Its not too nice to hear...

Quote:Original post by Yann L
I don't have an ATI card here right now, but has anyone tried what happens if you destroy the context without ending the process ? Does the driver free the memory (ie. does it keep track of the entire allocated memory, and releases it on context destruction), or is it a hard memory leak ? In the former case, one could destroy and recreate the contexts in regular intervals as a workaround.

I've just tried context recreation, but it didnt free even some memory.

Quote:Original post by Kalidor
I don't have anything else to say about wglMakeCurrent problem, but if what you're doing is like a typical 3d modeller setup you don't need to make separate windows for the different views. Just use different viewports.

Unfortunatelly, I have made MDI ortho windows, and I have made some relations to it, so changing onto viewports is not so easy.

Anyway, if people are trying to force ATI for such a long time to fix it, then probably our talk here wont do any diference. So, only alternative left for me is to change card to GeForce and do not recommend ATI Radeon anymore.