As I mentioned in my last message of the "E crash with Nvidia" thread,
in using ASAN I could trigger quite a bit of additional segmentation
faults. So I disabled the procstat module for now and went hunting. :-)
On closer inspection it now seems to me that the faults are actually all
due to an invalid call in e_object_del() of e_object.c.
Here are the traces and ASAN outputs of two captured crashes:
https://pastebin.com/3du7GYkS
https://pastebin.com/9V1wCjnw
They seem quite identical to me.
I did not find a fully reproducible way to trigger this. It mostly
happened for me right after a restart of E or when dismissing the
initial error dialog (informing me that there was some error with PAM).
Anyway, I hope that this is helpful.
Cheers
Florian
_______________________________________________
enlightenment-users mailing list
enlightenment-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-users
