mozilla/rust — Issue #1815: 0 bytes definitely lost on i686
Author: brson
Created: 2012-02-12 05:58:46+00:00
State: open
Labels: bug, mem, rt

Since I made some changes to the way C stacks work the linux2 bot periodically reports this failure

```
==55854== 0 bytes in 19 blocks are definitely lost in loss record 41 of 42
==55854== at 0x4D70E8A: malloc (vg_replace_malloc.c:236)
==55854== make: *** [check-stage2-T-i686-unknown-linux-gnu-H-x86_64-unknown-linux-gnu-std-dummy] Error 100
```

I don't know why yet, but I think it might be because I'm not giving valgrind the right hints. Unfortunately, giving valgrind hints in a way that is most likely to be correct results in a big perf hit.

On my machine I also get additional valgrind errors on i686 relating to the pthread stack that don't show up on the bots.