some remarks:
- if you catch it  early enough you are better off killing it
- it seems to be doing it even in  case it is performing just a sSELECT witount any modification of the database. Microsoft should be able to something about this.
-  if i can't  stop it  I would like to know how long it is still going to last - is there a way to find out ?
- in a complex query, is there a way rto find out where it ran away ?