[Bug libstdc++/65434] Memory leak in pool constructor

2016-12-13 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65434 --- Comment #10 from Jonathan Wakely --- See https://gcc.gnu.org/ml/gcc-patches/2016-12/msg01158.html

[Bug libstdc++/65434] Memory leak in pool constructor

2016-12-13 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65434 --- Comment #9 from Jonathan Wakely --- (Although I have a simpler patch that does something similar, as well as allowing the arena size to be controlled form the environment).

[Bug libstdc++/65434] Memory leak in pool constructor

2016-12-13 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65434 --- Comment #8 from Jonathan Wakely --- Please send patches to the libstdc++@ and gcc-patches@ mailing lists, rather than attaching them to closed bugs. https://gcc.gnu.org/onlinedocs/libstdc++/manual/appendix_contributing.html

[Bug libstdc++/65434] Memory leak in pool constructor

2016-12-13 Thread meisenmann....@fh-salzburg.ac.at
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65434 --- Comment #7 from Markus Eisenmann --- Hi! My motivation to use/implement this patch (comment #6) is to prevent using malloc to allocate the needed emergency-buffer region, if the needed overall size is bellow a (configurable) limit; e.g., emb

[Bug libstdc++/65434] Memory leak in pool constructor

2016-12-13 Thread meisenmann....@fh-salzburg.ac.at
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65434 Markus Eisenmann changed: What|Removed |Added CC||meisenmann.lba@fh-salzburg.

[Bug libstdc++/65434] Memory leak in pool constructor

2016-04-15 Thread lopresti at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65434 Patrick J. LoPresti changed: What|Removed |Added CC||lopresti at gmail dot com --- Comm

[Bug libstdc++/65434] Memory leak in pool constructor

2016-01-26 Thread emil.styrke at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65434 Emil Styrke changed: What|Removed |Added CC||emil.styrke at gmail dot com --- Comment #

[Bug libstdc++/65434] Memory leak in pool constructor

2015-03-16 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65434 --- Comment #3 from Jonathan Wakely --- (In reply to Dmitry Shachnev from comment #2) > Will anything bad happen if that memory is freed in the destructor? Yes, because other destructors could run later, and could (potentially) need to use the p

[Bug libstdc++/65434] Memory leak in pool constructor

2015-03-16 Thread mitya57 at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65434 --- Comment #2 from Dmitry Shachnev --- Will anything bad happen if that memory is freed in the destructor? For me, the issue is mostly aesthetic — I got used to not seeing any Valgrind warnings in my programs :)

[Bug libstdc++/65434] Memory leak in pool constructor

2015-03-16 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65434 Jonathan Wakely changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---