Hello Mahmoud,
I was looking at the mdtConsoleLogs file, but the LASSERT message didn't produce a stack trace because it entered kdb. It would have been useful to provide a stack backtrace. It would also be more useful if the backtrace and bug description was in the initial bug Description field rather than only in an attachment, since that makes it easier to review, prioritize, and assign this ticket, and later search for it if needed.
That said, it appears that this problem is a duplicate of LU-5934, which was fixed for the 2.5.4 release, but it isn't 100% clear without a stack trace.
Thanks Mahmoud.
~ jfc.