Re: [osv-dev] Re: OOM query

2020-03-24 Thread Waldek Kozaczuk
I remember it is an Erlang app. Is there any comparable open source app/example I could run to re-create your issue? On Tue, Mar 24, 2020 at 17:49 Waldek Kozaczuk wrote: > Also, besides the main app, what other OSv modules do you have in the > image? Httpserver-api, cloud-init, ? > > On Tue, Mar

Re: [osv-dev] Re: OOM query

2020-03-24 Thread Waldek Kozaczuk
Also, besides the main app, what other OSv modules do you have in the image? Httpserver-api, cloud-init, ? On Tue, Mar 24, 2020 at 17:44 Waldek Kozaczuk wrote: > > > On Tue, Mar 24, 2020 at 17:34 Rick Payne wrote: > >> >> I backed out the original patch, applied the other two. Do I need the >>

Re: [osv-dev] Re: OOM query

2020-03-24 Thread Waldek Kozaczuk
On Tue, Mar 24, 2020 at 17:34 Rick Payne wrote: > > I backed out the original patch, applied the other two. Do I need the > first one still? Nope. You should be fine. > We're not on master, but we're pretty close. Last > synced on March 3rd, commit ref 92eb26f3a645 > > scripts/build check runs

Re: [osv-dev] Re: OOM query

2020-03-24 Thread Rick Payne
I backed out the original patch, applied the other two. Do I need the first one still? We're not on master, but we're pretty close. Last synced on March 3rd, commit ref 92eb26f3a645 scripts/build check runs fine: OK (131 tests run, 274.753 s) Rick On Tue, 2020-03-24 at 17:15 -0400, Waldek Koz

Re: [osv-dev] Re: OOM query

2020-03-24 Thread Waldek Kozaczuk
Is it with the exact same code as on master with the latest 2 patches I sent applied ? Does ‘scripts/build check’ pass for you? On Tue, Mar 24, 2020 at 16:56 Rick Payne wrote: > > I tried the patches, but its crashing almost instantly... > > page fault outside application, addr: 0x56c000

Re: [osv-dev] Re: OOM query

2020-03-24 Thread Rick Payne
I tried the patches, but its crashing almost instantly... page fault outside application, addr: 0x56c0 [registers] RIP: 0x403edd23 RFL: 0x00010206 CS: 0x0008 SS: 0x0010 RAX: 0x56c0 RBX: 0x200056c00040 RCX: 0x004c0