unfortunately - that there says "something corrupted memory, but we don't know where or what". the corruption happened some time prior to this backtrace and crash - when/where - no idea. this is where you need valgrind to catch it. what were you doing when this happened? what had you done prior to it and over the lifetime of the terminology process? i.e. - how to reproduce it?
Sorry for the late reply, I've been busy.
I cannot find a pattern to the crashes, they seem to happen when I have a lot of terminals open, all continuously updating.
I'm running terminology under valgrind now, but it hasn't crashed yet. I'll stick at it and report valgrind output of any crashes.
I haven't managed to make it crash under valgrind, whether this is because valgrind somehow stops the bug, or because I'm unlucky, I don't know.
The crash seems to only occur when there are many terminals updating at once.