TRASH1 drops off the face of the earth at large contender sizes?

[solb]

Setting the trash working set size to 102400 (1 GB) on dog results in the first trash process—the one sharing a core with the lockserver, incidentally—never printing ENDLAP002 for some data points! Does it crash? Is it just running extremely slowly, and does waitforexit fail to actually do its job? (Although in the latter case, wouldn't we see it printed later on, during some other trial?)

There doesn't seem to be enough info in the logs to discern...

[solb]

Not observed / unneeded for a long time. Might have been a hugepages allocation failure (just a guess)?

IDK/IDC.