The Flush Printed a View After the Owner Died
A green debug run does not prove a view owns its bytes. Release can reuse that stack slot before the flush reads it. I start every split-brain crash with that suspicion. This is a labeled reconstruction, not a ticket I closed. I did not run this harness for the numbers in this draft. The failure mode is still common enough to practice on purpose. What broke The exporter looks fine in an…
The owner of bytes dies before a view can print them, causing the flush thread to read invalid data. This issue can appear in optimized builds due to the temporary owner dying before the flush thread reads the memory. To fix it, change the Sample struct to store a string instead of a non-owning view.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
