It's now April 2012 and this bug is still unassigned? Also, not only does it consume 100% cpu, overtime it will also consume more and more memory and can in some cases easily make the machine completely run out of memory.
It's now April 2012 and this bug is still unassigned?
Also, not only does it consume 100% cpu, overtime it will also consume more and more memory and can in some cases easily make the machine completely run out of memory.