Urbit Crashing on Bootup after Dojo Stopped working #5304
Description
Describe the bug
I restarted my pier and urbit booted up as normal. Dojo took forever to load but after it finally did I would get
gall: not running %hood yet, got %poke
Whenever a keyboard input occured.
I restated urbit a few times with no such luck and the last time i restarted it I got:
~
urbit 1.5
boot: home is /home/XXXX/urbit/XXXXX
loom: mapped 2048MB
lite: arvo formula 79925cca
lite: core 59f6958
lite: final state 59f6958
loom: mapped 2048MB
boot: protected loom
live: loaded: MB/720.781.312
pier: serf unexpectedly shut down
I asked for help on ~bitbet-bolbel/urbit-community/ and they recommended I run urbit with gdb and the core. Here is that output:
Core was generated by `./urbit-worker serf xxxx 0:0:0:0 128 50000 0'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x000000000042ecf2 in _box_free (box_u=0xc16d3422) at noun/allocate.c:183
183 noun/allocate.c: No such file or directory.
(gdb) thread ap[ply all bt
Invalid thread ID: [ply all bt
(gdb) thread apply all bt
Thread 1 (LWP 1256453):
#0 0x000000000042ecf2 in _box_free (box_u=0xc16d3422) at noun/allocate.c:183
#1 _box_free (box_u=0xc16d3422) at noun/allocate.c:161
#2 u3a_wfree (tox_v=0xc16d342a) at noun/allocate.c:632
#3 0x0000000200000000 in ?? ()
#4 0x000000020c660550 in ?? ()
#5 0x000000000042ed75 in _box_free (box_u=0xc3198154) at noun/allocate.c:240
#6 _box_free (box_u=<optimized out>) at noun/allocate.c:161
#7 u3a_wfree (tox_v=<optimized out>) at noun/allocate.c:632
#8 0x0000000000000000 in ?? ()
(gdb)
To Reproduce
Steps to reproduce the behaviour:
- run
./urbit ~my-planet
Expected behaviour
urbit to load
System (please supply the following information, if relevant):
- OS: Ubuntu 20.03 64-bit
- Urbit 1.5
- Can't access