Quote Originally Posted by QNewbie View Post
Hey everyone, I've recently been poking around migrating and adding features to an old project using Qt 5.14.1,
This time I'm more than sure that I introduced a memory corruption bug (due to the line where it consistently fails) but upon calling the debugger it gets stuck.

At first, launching it gets it stopped at RtlUserThreadStart, and on thread #4, however when I try to continue cdb, it launches another thread (stoping at the same place).
This keeps on going until it reaches thread number 7, when "Run requested" is seen in the status bar, and I can no longer press the continue running button.

The bottom right status message from QtCreator keeps on at 25% saying "Launching debugger".

The code where it fails leads me to think there is memory corruption do to it being:

The widget is removed from view correctly, however aparently renglones has some issue (QVector) and upon trying to access the remaining ones upon saving the data is where the bug is triggered -size() shows after the elimination that its been removed-.
What can I do to fix the debugger stopping doodle jump? In the meantime I'll try to audit the code and look for anything I've dynamically allocated to see if I can find the issue.
You’re removing from renglones using the layout index: renglones.remove(contenedorRenglones->indexOf(renglon)). That index may not match the vector, so you end up erasing the wrong pointer and later iterate a dangling one; instead do renglones.removeOne(renglon) or renglones.remove(renglones.indexOf(renglon)), then contenedorRenglones->removeWidget(renglon); renglon->deleteLater(); and consider passing the widget pointer in the signal rather than relying on sender().