public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug libstdc++/58737] New: leak in std::regex_match
@ 2013-10-15 11:25 larsbj at lyx dot org
  2013-10-15 11:26 ` [Bug libstdc++/58737] " larsbj at lyx dot org
                   ` (5 more replies)
  0 siblings, 6 replies; 7+ messages in thread
From: larsbj at lyx dot org @ 2013-10-15 11:25 UTC (permalink / raw)
  To: gcc-bugs

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58737

            Bug ID: 58737
           Summary: leak in std::regex_match
           Product: gcc
           Version: 4.9.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: libstdc++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: larsbj at lyx dot org

I have something that certainly looks like a memory leak.

g++ --version
g++ (GCC) 4.9.0 20131014 (experimental)

g++ -std=gnu++11 -O2 leak.cpp

If I increase the amount of looping the leak reports
increases linearly.

All output from valgrind below. It might be regex or it might be some
allocator issue, I have seen something with std::deque as well outside
any regex context. Not been able to reproduce though.


^ permalink raw reply	[flat|nested] 7+ messages in thread

end of thread, other threads:[~2013-10-15 15:06 UTC | newest]

Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2013-10-15 11:25 [Bug libstdc++/58737] New: leak in std::regex_match larsbj at lyx dot org
2013-10-15 11:26 ` [Bug libstdc++/58737] " larsbj at lyx dot org
2013-10-15 11:27 ` larsbj at lyx dot org
2013-10-15 11:32 ` redi at gcc dot gnu.org
2013-10-15 14:50 ` paolo.carlini at oracle dot com
2013-10-15 15:01 ` timshen at gcc dot gnu.org
2013-10-15 15:06 ` paolo.carlini at oracle dot com

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).