Hello,
Thomas Schwinge, on Mon 28 Nov 2016 17:10:26 +0100, wrote:
> ..., but on the new ("bad") system, the first non-sensical (huge;
> -2147479552 is 0x80001000) vm_allocate call actually succeeds:Yes, the userland address space is now 3G again, so it can now indeed allocate that much. > I have not yet figured out where these vm_allocate calls and/or their > huge size parameters are coming from. Probably the real source of the issue :) Samuel
