|
From: K. F. <kfr...@gm...> - 2014-12-25 04:42:11
|
Hello All! This may not be relevant, but I may have seen a similar memory issue with mingw-w64 (a project distinct from mingw). On Wed, Dec 24, 2014 at 10:27 PM, Edward Diener <eld...@tr...> wrote: > On 12/24/2014 9:13 PM, asmwarrior wrote: >> On 2014-12-25 9:31, Edward Diener wrote: >>> I could report this on the gcc bugzilla tracker but reproducing it using >>> my VMD library, although it is public on Github, will be fairly >>> complicated task ( the latest modular Boost must also be downloaded and >>> setup from Github ) for whomever handles the bug. I was hoping this sort >>> of problem, based on what seems to me to be a large-scale memory leak, >>> would be known for these later versions of gcc and I could find a >>> workaround. >> ... I had what appeared to be an out-of-memory issue with a 64-bit mingw-w64 build of gcc 4.9.2 when building Wt. The Wt build failed when compiling Wt's CssParser.C. This was on a 4 GB machine. I killed off some unnecessary processes and restarted the build. It succeeded, but it looks like compiling CssParser.C took about 2 GB. I wrote this off as "normal," even though it seems very large, because CssParser.C uses the boost spirit template-metaprogramming parser generator, and I presumed that the template-metaprogramming was the source of the memory consumption. But maybe this reflects a problem in gcc, and not the memory needs of compiling Wt / boost. Note, I only tried this with gcc 4.9.2. I have know idea whether I would have seen similarly large memory usage with an earlier gcc such as 4.7. Best. K. Frank |