Did this happen again since you reported this bug? Is it somehow reproducible? Please try to get new traces against 4.1.2 Thank you.
Did this happen again since you reported this bug?
Is it somehow reproducible?
Please try to get new traces against 4.1.2
Thank you.