And these are the results of running
enlightenment_start -valgrind --show-reachable=no --vgdb-error=0 --leak-check=full > output.txt 2>&1
That is, with the "--leak-check=full" parameter added, suggested by Valgrind
I confirm that the leak/error found by Valgrind is the Moksha restart created when moving around a window in the main display. As I stated before, that Moksha segfault is not reproducible in the nested display, but it is easily reproduced in the main display by merely moving a window around and, fortunately, that is detected by Valgrind.
This issue continues spreading. Yesterday we installed in a computer labs with 42 computers, that had only two computer brands. Unfortunately, in both models the Moksha restart happen by merely moving a window, so all computers in the lab were unlucky ones to have this bug. The only one that didn't show this behavior was the teacher laptop...