search for: didreceivememorywarn

Displaying 3 results from an estimated 3 matches for "didreceivememorywarn".

2016 May 05
1
R process killed when allocating too large matrix (Mac OS X)
...; Not directly, because the system is happy to accommodate R's request for more memory but then it will strike out of the blue. Since that decision is made by the kernel and it doesn't expose its thinking about how it feels, it's hard to tell. I couldn't find any API on OS X akin to didReceiveMemoryWarning in iOS, unfortunately. > > You could guess - e.g. by checking the total system memory > > int mib [] = { CTL_HW, HW_MEMSIZE }; > int64_t value = 0; > size_t length = sizeof(value); > sysctl(mib, 2, &value, &length, NULL, 0); > > and comparing it to the sizes in...
2016 May 05
4
R process killed when allocating too large matrix (Mac OS X)
Hi Simon, thanks for your quick reply. 1) ... so you can reproduce this? 2) Do you know a way how this can be 'foreseen'? We allocate larger matrices in the copula package depending on the user's input dimension. It would be good to tell her/him "Your dimension is quite large. Be aware of killers in your neighborhood"... before the killer attacks. Thanks & cheers,
2016 May 05
0
R process killed when allocating too large matrix (Mac OS X)
...Not directly, because the system is happy to accommodate R's request for more memory but then it will strike out of the blue. Since that decision is made by the kernel and it doesn't expose its thinking about how it feels, it's hard to tell. I couldn't find any API on OS X akin to didReceiveMemoryWarning in iOS, unfortunately. You could guess - e.g. by checking the total system memory int mib [] = { CTL_HW, HW_MEMSIZE }; int64_t value = 0; size_t length = sizeof(value); sysctl(mib, 2, &value, &length, NULL, 0); and comparing it to the sizes involved. However, even that is not foolproo...