Not the same behavior for a chrome process

@postwick ok as soon as possible i’ll try without killing chrome