It looks like 2.4 hopefully has (another) fix for this:
Hope to see some reports here, when 2.4 is getting released.