test Rust stdlib with mozjemalloc
Categories
(Core :: Memory Allocator, enhancement)
Tracking
()
People
(Reporter: myk, Unassigned)
Details
Since hooking our allocator into Rust can cause problems like bug 1531887 (and possibly https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=231933190&repo=try&lineNumber=2148, which mgoodwin is investigating), it'd be useful to run the Rust stdlib tests with our allocator to identify such issues in advance.
Comment 1•5 years ago
|
||
Bug 1531887 is related to the weird way things are when running gecko on Android. Reproducing the same setup to run the rust std tests is not going to be trivial. I doubt that other log is related to the allocator. Overall I'm afraid there's not much that is usefully actionable here.
Comment 2•5 years ago
|
||
FWIW, the only reason malloc appears in the stack trace in the logviewer link is that stack scanning tends to find traces of previous allocation on the stack rather often. As long as you don't see it appear with "Found by: call frame info" (or "frame pointer"), it's probably a bogus frame.
Description
•