Closed mneumann closed 10 years ago
if you run valgrind, does it turn up anything suspicious?
hm, is it only me seeing this failure? I thought it is somehow reproducable everywhere :). I haven't tried valgrind yet.
Ah I was just hoping you still had a build lying around, I hadn't personally tried it out just yet, but I shall do so now!
@mneumann: Is this still an issue with master?
AFAIK this has been fixed. I can't duplicate it on Linux or Windows.
If I build rust with --disable-jemalloc, I am getting a strange memory issue somewhere in stage1 (see below for how to reproduce it on Linux). I also reproduced the same issue during porting rust to DragonflyBSD (which I initially built w/o jemalloc). There I noticed for some input files that it wants to mmap an anonymous region of size 0x800_000_000 or 0x1000_000_000, probably due to a mal-formed malloc call (just a wild guess). And then more or less stalls the system, probably trying to zero that region and swapping to disk. Changing a single letter in the file subject for compilation makes rustc behave well again. With jemalloc, these issues are not existent (both on Dragonfly and Linux)!
results in: