Comment 3 for bug 515236

It looks as if you've analyzed this pretty well. Could you try to put it into code? It will probably get resolved faster that way and you seem to have a good understanding of the algorithm needed to fix it.