Let me guess, you were watching on Mtgoxlive or something using the same feeding method.
This is one of two known bugs. Ignore it, it didn't happen. The two bugs are on new changes: one does and undoes them frequently, the other adds it twice, then undoes it a few iterations later.
Don't trust these order book pages, they're written by people who think it's funny to never do any sanity checks, never correct the view and induce extra madness. Best proof: the scale on the right side of Mtgoxlive. Come on, after seeing that, it's your fault for taking the site all too seriously. And the CPU usage should remove any remaining doubt of the joky nature of the page. It's CPU mining, isn't it? I hope so, because it's the only sane explanation for the performance.
I kinda miss Bitcoinity. That one was slower in updates, but fairly decent in what it displayed.
This is one of two known bugs. Ignore it, it didn't happen. The two bugs are on new changes: one does and undoes them frequently, the other adds it twice, then undoes it a few iterations later.
Don't trust these order book pages, they're written by people who think it's funny to never do any sanity checks, never correct the view and induce extra madness. Best proof: the scale on the right side of Mtgoxlive. Come on, after seeing that, it's your fault for taking the site all too seriously. And the CPU usage should remove any remaining doubt of the joky nature of the page. It's CPU mining, isn't it? I hope so, because it's the only sane explanation for the performance.
I kinda miss Bitcoinity. That one was slower in updates, but fairly decent in what it displayed.
CPU usage is caused by JS engine in a browser which constantly updates the page. before suggesting CPU mining check page's html and js sources. from what i remember seeing some other sites in the past implementing browser miner - browser would throw a red flag notification that something maybe going on in the background and whether you want to proceed or not.