xref: /aosp_15_r20/art/test/175-alloc-big-bignums/info.txt (revision 795d594fd825385562da6b089ea9b2033f3abf5a)
1*795d594fSAndroid Build Coastguard WorkerAllocate large numbers of huge BigIntegers in rapid succession. Most of the
2*795d594fSAndroid Build Coastguard Workerassociated memory will be in the C++ heap. This makes sure that we trigger
3*795d594fSAndroid Build Coastguard Workerthe garbage collector often enough to prevent us from running out of memory.
4*795d594fSAndroid Build Coastguard Worker
5*795d594fSAndroid Build Coastguard WorkerThe test allocates roughly 10GB of native memory, approximately 1MB of which
6*795d594fSAndroid Build Coastguard Workerwill be live at any point. Basically all native memory deallocation is
7*795d594fSAndroid Build Coastguard Workertriggered by Java garbage collection.
8*795d594fSAndroid Build Coastguard Worker
9*795d594fSAndroid Build Coastguard WorkerThis test is a lot nastier than it looks. In particular, failure on target tends
10*795d594fSAndroid Build Coastguard Workerto exhaust device memory, and kill off all processes on the device, including the
11*795d594fSAndroid Build Coastguard Workeradb daemon :-( .
12