[Mesa-users] Segfault when running the tutorial

[Francis Timmes]

i’ve not seen this message from x11/pgstar before, 
but my first guess is that your still low on memory.

again, please cc mesa-users on all replies.

fxt




> On Aug 24, 2019, at 4:50 PM, Croxmor Moraga <rodrigo.moraga.merino at gmail.com> wrote:
> 
> Forget what I asked before jeje. It happens that I fixed it, by keeping the first windows that appears from pgstar once I created the model, and keep it open, the loaded one create the plots as normal.
> In that case, anytime i decided to load a model I used, i should run a test model, conserve that window, and then load the desired model?
> Or it is some method to fix that?
> Thanks for your pacience, and good night.
> 
> El sáb., 24 ago. 2019 a las 19:03, Croxmor Moraga (<rodrigo.moraga.merino at gmail.com>) escribió:
> But going back to my last problem, when I load that model I created before, and continued it. It runs, but the pgstar plots didn't appear, and instead this is written in my terminal.
> PGPLOT /xw: Waiting for /home/rodrigo/mesasdk/lib/pgplot/pgxwin_server to start (timeout in 7 seconds).
> PGPLOT /xw: Timed out waiting for program /home/rodrigo/mesasdk/lib/pgplot/pgxwin_server to start
> PGPLOT /xw: Waiting for /home/rodrigo/mesasdk/lib/pgplot/pgxwin_server to start (timeout in 7 seconds).
> PGPLOT /xw: Timed out waiting for program /home/rodrigo/mesasdk/lib/pgplot/pgxwin_server to start
> 
> Is that normal when I load a model, and because of that, I have to write something else in the code?
> Or is just another ram memory problem?
> 
> El jue., 22 ago. 2019 a las 15:44, Croxmor Moraga (<rodrigo.moraga.merino at gmail.com>) escribió:
> I did built my own, with oracle virtual machine on windows, created a ubuntu distribution
> 
> El jue., 22 ago. 2019 12:49, amber lauer via Mesa-users <mesa-users at lists.mesastar.org> escribió:
> Jon, I think it's because he's running a VM. I make the VMESA virtual machine, and though I'm not sure if that's what he's running, but it's a known problem if you don't extend the default memory and OMP cores. The How-to immediately recommends this, but I should add a statement specifically about the error. Croxmor, are you running VMESA or did you build your own VM?
> =================================
> Dr. Amber Lauer
> Postdoctoral Researcher
> Triangle Universities Nuclear Lab
> Duke University
> amber.lauer at tunl.duke.edu
> 
> 
> On Wed, Aug 21, 2019 at 6:51 PM Josiah Schwab via Mesa-users <mesa-users at lists.mesastar.org> wrote:
> Hi Jon,
> 
> I'm haven't looked carefully at the chain of events that leads of the SIGSEGV, but after the eos table allocation fails MESA should stop more gracefully.  One of the eos routines wasn't properly reporting that it failed to its caller, a bug which I just fixed.
> 
> Josiah
> _______________________________________________
> mesa-users at lists.mesastar.org
> https://lists.mesastar.org/mailman/listinfo/mesa-users
> 
> _______________________________________________
> mesa-users at lists.mesastar.org
> https://lists.mesastar.org/mailman/listinfo/mesa-users
>