forked from firka/flutter
8fc02f5b1dadc8caad555152ccaa3f0d80c23c64
Verified that the tests fail on issues like https://github.com/flutter/engine/pull/8166. Unfortunately, there is no x-platform way to perform this check but this should gate incorrect traces being added to the engine.
Add an allocator specific check to ensure that strings passed to the timeline are not heap allocated. (flutter/engine#8168)
Description
No description provided
Languages
Dart
75.4%
C++
16.4%
Objective-C++
2.7%
Java
2.7%
Objective-C
0.6%
Other
1.8%