On Sun, Jun 26, 2016 at 10:12 AM, Neeraj Sharma <[email protected]> wrote: > On Fri, Jun 24, 2016 at 11:02 PM, Antti Kantee <[email protected]> wrote: >> >> Well, it probably won't take too many minutes to at least identify the >> problem. >> > > My gut feeling is that this has something to do with memory allocation > (based on my initial attempt to port Erlang on Rumprun) and I wonder > what will happen if mmap is called with memory allocation larger than > the system available memory in Rumprun? > >> But I don't want to distract you from the tracing efforts ;) >> > > I somehow want to find an excuse to take the longer path, hopefully > adding more value in general. Having said that I'd probably envisage > it in multiple phases to get something out sooner than later. >
I couldn't give sufficient dedicated time to tracing, hence running into delays. While the activity is just starting out I resorted to using gdb (finally) to at least track the issue. As anticipated Erlang VM is requesting for larger chunk 1GB of memory while VM is running 256MB which surprisingly goes into an infinite loop within rumprun. I have raised an issue https://github.com/rumpkernel/rumprun/issues/81 to track the same and will be great if it's looked at. -Neeraj
