Mmm, no reason why Totem would break things unless it's running as a service and blocking something that tvh is then looking for.
ps -eaf | grep totem, perhaps? See if anything is running?
After that, I can only immediately suggest:
1. Upgrading tvheadend. 4.1-343 is about two weeks old, but, more importantly, an over-write of tvhmight grab back whatever Totem took away. Perhaps. Maybe. If you were on the genuinely unstable/nightly branch then I'd have thought you'd have got that already.
2. Proper debugging. I'd need to think about how that would work with gdb and a service... as an initial though, try:
sudo service tvheadend stop
sudo tvheadend -f -u hts -g video
... see if it crashes then. If it doesn't, then it's something to do with systemd, although those are clearly tvheadend messages. If it does crash, then we're closer to using gdb.
You'll need a deb built from source and the corresponding debug symbols - I'll build you a version (64-bit?) if necessary.
Then run the tvheadend command above within gdb - and that's where my memory fades, so I'd need to look.
Hoping that someone else comes along with some more recent experience. I think it's simply "gdb /usr/bin/tvheadend <args as above>", then wait for a crash, then bt to get the stack trace - the debug symbols will convert the hex addresses back to line numbers and modules to tell you where in the source code it's breaking (and, perhaps, why).