Fixed a CPU hog bug when rendering slashdot.

https://linux.slashdot.org/comments.pl?sid=5852295&cid=48188823

It was hard to find, sometimes backtraces gave near 85 or more nested calls,
full of different functions. There was no CPU lock because it finally solved
the page (after more than two minutes in my machine).

Finding the bug:  > 99,9% of the effort.
Actual fix     :  ~ 0.01% of the effort.

1 files changed, 1 insertions, 1 deletions

diff --git a/dw/ooffloatsmgr.cc b/dw/ooffloatsmgr.cc
index fe6d25d4..2ec73bf3 100644
--- a/dw/ooffloatsmgr.cc
+++ b/dw/ooffloatsmgr.cc
@@ -657,7 +657,7 @@ void OOFFloatsMgr::markSizeChange (int ref)
                          ->parentRef);
 
    for (int i = first + 1; i < tbInfos->size(); i++)
-      tbInfos->get(first)->getOOFAwareWidget()->updateReference(0);
+      tbInfos->get(i)->getOOFAwareWidget()->updateReference(0);
 
    DBG_OBJ_LEAVE ();
 }