https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86295
--- Comment #2 from Kristian Spangsege <kristian.spangsege at gmail dot com> --- Oh, I missed that crucial fact. Sorry. We can close this as invalid then. On Mon, Jun 25, 2018 at 3:35 PM, redi at gcc dot gnu.org < gcc-bugzi...@gcc.gnu.org> wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86295 > > --- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> --- > (In reply to Kristian Spangsege from comment #0) > > The problem occurs when either `std::__uninitialized_copy_a()` or > > `std::__uninitialized_move_a()` throws due to throwing from the copy or > move > > constructor of the value type. In this case, the logical size of the > vector > > remains at its prior value, which means that if any objects were created, > > they will be forgotten about (leaked). > > Do you have a testcase? > > If an exception occurs in __uninitialized_copy_a and __uninitialized_move_a > they will destroy any objects they created, so I don't see how they can > leak. > > -- > You are receiving this mail because: > You reported the bug. >
