Hein-Pieter van Braam 38ae49e574 Make sure we don't leak when an opcode is followed by itself ...

When compiling with GCC it is now possible for an opcode followed by
itself to never leave the scope it is currently in. This leads to a
situation where the dtor of a scope local variable isn't called which in
turn can lead to a memory leak.

By moving the goto outside of the scope of each opcode we guarantee that
all dtors have been called before the next opcode gets dispatched.

this fixes #12401

2017-11-09 17:57:43 +01:00

41 KiB

Raw Blame History

View Raw