Samuel Thibault, le mer. 01 nov. 2023 13:14:17 +0100, a ecrit: > Samuel Thibault, le mer. 01 nov. 2023 01:50:40 +0100, a ecrit: > > Samuel Thibault, le mar. 31 oct. 2023 04:40:43 +0100, a ecrit: > > > (it looks like there are memory leaks in proc, its vminfo keeps > > > increasing). > > > > It seems 64bit-specific: the program below makes proc leak memory, 100 > > vminfo lines at a time. Possibly __mach_msg_destroy doesn't actually > > properly parse messages to be destroyed, so that in the error case the > > server leaks non-inline data? Flavio, perhaps you have an idea? > > I don't think we have the kernel-to-user equivalent for > adjust_msg_type_size? So that we end up pushing twice too much data to > userland for port arrays?
I found and fixed the allocation issue in the kernel. We however still probably need some adjust_msg_type_size in copyoutmsg, otherwise userland will see a 64bit size for ports? Samuel
