You won't see any message in the log, just the error number. Anyway, it's worth checking. If so, it'll be CR 793065, one we reported back in December.
Looks like they have documented it now under KBA 2252511https://launchpad.support.sap.com/#/notes/2252511/E.
Any spid that has gone into log suspend whilst inserting into a temporary table will fail to have the temporary table dropped when it is killed. It effects back to at least SP100 so not sure why the KBA says SP132.