| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | Change ddmc run-test to make new objects instead of strings. | Jeff Hao | 2015-04-28 | 1 | -1/+1 |
| | | | | | | | | | | | Before, the test was creating new strings until overflowing allocations, which was half string objects and half character arrays. Now, it allocates all strings with the character data, which is larger than before, causing the test to run out of memory. Allocating only objects prevents the test from running out of memory. Change-Id: Icf3f0fd2ae847e76a9b8d5dfb762be92de16aaa3 | ||||
| * | Fix numerous issues with DdmVmInternal allocation tracking | Brian Carlstrom | 2014-09-05 | 1 | -0/+154 |
| Issues addressed: - Using without JDWP attached caused native crash. - When buffer is full (64k entries), number of entries reported was 0. - Disabling tracking after disabling tracking caused native crash. - Asking for allocations after disabled caused native crash. - Lock ordering issues between mutator lock and alloc tracker lock. Adding 098-ddmc test to cover these cases. Bug: 17392248 (cherry picked from commit a5815065ac0877add9c0db3605d27b4d6c426e61) Change-Id: Ib0bc18dfcdafcc050ab9dceed3d167dd878d1d7a | |||||
 |
index : art.git | |
| Android's art |
| summaryrefslogtreecommitdiffstats |