It seems that it started happening after the MSDP/GMCP match. In 32424864e42a0b75e77d2c02c301209eb14d4e62 this did not happened, so it must be this update.
