[Interest] QT plugins memory footprint and the debugger

[Ulf Hermann]

> Looking at the source of qt, the problem is identical(though it is protected against runaway exceptions). The MinGw debug plugins of qtquick are quite large and use the same mechanism to load plugins. If, as in my case, the initialization of the program allocates considerable memory ( but tbh, not excesively so, there is plenty left) QT (and by extension QT quick) can run into problems; in debug mode, using MinGw. This wasnt the case in 5.2 so I must assume that code of loading plugins was changed in between.

MinGW maps the debug symbols into memory when loading libraries, which on 32bit systems quickly eats up your address range. One trick that worked for me is compiling everything (including Qt) with "-separate-debug-info". This will put the debug symbols into separate files that aren't mapped at run time. The debugger will still read them.

br,
Ulf