Hi Vignesh, On Thu, 19 Oct 2023 at 09:07, Vignesh Raman <vignesh.raman@xxxxxxxxxxxxx> wrote: > +# Some tests crashes with malloc error and IGT tests floods > +# the CI log with error messages and we end up with a warning message > +# Job's log exceeded limit of 4194304 bytes. > +# Job execution will continue but no more output will be collected. This is just from GitLab warning that we have a huge log, so not related to the actual fails here. > +# Below is the error log: > +# malloc(): corrupted top size > +# Received signal SIGABRT. > +# Stack trace: > +# #0 [fatal_sig_handler+0x17b] > +# #1 [__sigaction+0x40] > +# #2 [pthread_key_delete+0x14c] > +# #3 [gsignal+0x12] > +# #4 [abort+0xd3] > +# #5 [__fsetlocking+0x290] > +# #6 [timer_settime+0x37a] > +# #7 [__default_morecore+0x1f1b] > +# #8 [__libc_calloc+0x161] > +# #9 [drmModeGetPlaneResources+0x44] > +# #10 [igt_display_require+0x194] > +# #11 [__igt_unique____real_main1356+0x93c] > +# #12 [main+0x3f] > +# #13 [__libc_init_first+0x8a] > +# #14 [__libc_start_main+0x85] > +# #15 [_start+0x21] > +# malloc(): corrupted top size By the time we get this error, it indicates that there was previously memory corruption, but it is only being noticed at a later point. The skip lists here are way too big - stuff like drm_read is common testing not affected by virtio at all - so we really need to isolate the test which is actually breaking things. The way to do this would be to use valgrind to detect where the memory corruption is. VirtIO can be run locally so this is something you can do on your machine. Cheers, Daniel
