This is likely to be fixed in 3.0.11 if it is not 3.0 will not receive this fix leaving open until 3.0.11 is out
This is likely to be fixed in 3.0.11 if it is not 3.0 will not receive this fix leaving open until 3.0.11 is out