I believe I was seeing this issue or one much like it myself.

I could reproduce it every time by running a query with a large result set, then...