We are currently migrating Bugzilla to GitHub issues.
Any changes made to the bug tracker now will be lost, so please do not post new bugs or make changes to them.
When we're done, all bug URLs will redirect to their equivalent location on the new bug tracker.

Bug 5423 - Committed memory keeps rising when repeatedly resizing window with openGL context.
Summary: Committed memory keeps rising when repeatedly resizing window with openGL con...
Status: NEW
Alias: None
Product: SDL
Classification: Unclassified
Component: video (show other bugs)
Version: 2.0.14
Hardware: x86_64 Windows 10
: P2 major
Assignee: Sam Lantinga
QA Contact: Sam Lantinga
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-12-29 22:58 UTC by Filippo Crocchini
Modified: 2020-12-31 11:32 UTC (History)
0 users

See Also:

Attachments
Native win32 test case for possibly related problem. (4.31 KB, text/plain)
2020-12-31 11:32 UTC, Filippo Crocchini 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Filippo Crocchini 2020-12-29 22:58:18 UTC 
I managed to repro this problem with this example (not mine) https://gist.github.com/jordandee/94b187bcc51df9528a2f

If you spam "f" to toggle fullscreen the committed memory keeps rising and stays the same after you stop.
It also seems to happen after resizing the window, but for some reason sometimes it decreases although increasing on average.

I checked with Resource Monitor(perfmon.exe)and with Visual Studio.
Comment 1 Filippo Crocchini 2020-12-31 11:31:23 UTC 
Upon further investigation it looks like it could be a driver issue, both the drivers for Intel UHD Graphics 630 version 27.20.100.8681 and for Nvidia RTX 2060 version 27.21.14.6089 have almost the same problem. I tried on a different machine with different drivers and everything works fine.

If the reason is the same as the one I found then it's not an SDL bug, I have attached the code that I used to test it (the problem is with SwapBuffers and wglSwapLayerBuffers). If you don't have the same problem then I may just be very unlucky.

You may have better chances to get those bugs fixed on the driver side so I'm leaving this here.
Comment 2 Filippo Crocchini 2020-12-31 11:32:48 UTC 
Created attachment 4622 [details]
Native win32 test case for possibly related problem.