Allocated Size of sf::RenderWindow

[Cyrana]

I was profiling my allocations and tracked about 66mb down to sf::RenderWindow construction. I used break points for this.
While the heap says, it is only 520 bytes big, this is quite contradicting to me.

Does this sound wrong? Where is the rest being allocated on?

I could not find example sizes of SFML classes, they might vary from OS to OS anyway.
66mb seems a lot to me, I might just have a wrong idea of it.

Additional information:
This happened on debug and release build using /O2
Using Visual Studio 2015 and its profiler
Windows 7
SFML 2.3.2

[Hapax]

I suppose the first question should be: is this a debug or release build?

[Cyrana]

The both mentioned sizes were on a debug build.

Same behaviour on release build, using /O2 optimization.

Updated the starting post for further missing specs : )

[eXpl0it3r]

Do you have a system the requires a tight memory usage or is this just a personal annoyance?
I mean, I have no idea how much SFML's RenderWindow should allocate, but then again I don't really see a problem with it allocating 60+MB either.

Can you provide the output log of whatever tool you used?

[Cyrana]

Well, I just hit a milestone in my project and looked at the RAM usage. It was a bit high for what it does (around 90mb). Also keeping it low for Android.
Therefore, I started profiling. I found out, that once the RenderWindow is being allocated, 60 of these are just gone.

To be exact:
rendering_window = (std::make_unique<sf::RenderWindow>(window_mode, title_bar_text));

There is not much I could provide you with, the profiler's graph just shows the attached information.
By exact hovering, it displays: 65.7mb. The snapshot was taken after the allocation, during the break point.

The data is not found on the heap. The heap only owns 20mb, only having a small instance of 520 bytes as sf::RenderWindow.

[eXpl0it3r]

I assume you are aware however that Windows RAM usage isn't really comparable to Android RAM usage, right?

I've quickly ran the most basic SFML application, compiled with MinGW GCC 6.1.0, linked SFML and the runtime lib statically and I ended up with Windows task manager (which is obviously not a good measurement tool) showing pretty much 30MB of memory usage.

Not sure if Visual Studio is adding more (unnecessary) things to it?

#include <SFML/Graphics.hpp>

int main()
{
    sf::RenderWindow window(sf::VideoMode(800, 600), "Test");

    while(window.isOpen())
    {
        sf::Event event;
        while(window.pollEvent(event))
        {
            if(event.type == sf::Event::Closed)
                window.close();
        }
    }
}
 

[Cyrana]

Yeah, I know it's not comparable. But I worried about possible memory leaks and unnecessary allocations and whatnot. It just ended up that sf::RenderVideo was allocating a lot, now I wanted to find out if that is my fault.

Thanks for your effort, eXpl0it3r : )
I tried your code, debug build (SFML 2.3.1, statically linked).

Task-Manager: 52mb
Visual Studio profiler: 64.8mb

Which confuses me already, but well.
This rather odd in general. I could not imagine what Visual Studio would add.

[Raincode]

Using eXpl0it3r's Code (static linking) and nuwen-6.1 MinGW distro O2 gave me 8,5MB in TaskManager. In case you are interested in more data.