Odd segfault in erl_drv_cond_create -> erts_alcu_alloc_thr_pref -> mbc_alloc -> bf_get_free_block
yrashk opened this issue · comments
Never seen this on my mac pro, but got this couple of times on my slow macbook air:
Thread 6 (core thread 5):
0 0x000000001001a3a9 in bf_get_free_block ()
1 0x0000000010011c56 in mbc_alloc ()
2 0x00000000100130dc in erts_alcu_alloc_thr_pref ()
3 0x00000000100e51c4 in erl_drv_cond_create ()
4 0x0000000013b002cc in VM::VM (this=0x107016f0) at c_src/erlv8.cc:28
5 0x0000000013b00487 in new_vm (env=0xb0356df0, argc=0, argv=0x110f0500) at c_src/erlv8.cc:124
6 0x00000000100ff227 in process_main ()
7 0x00000000100715a1 in sched_thread_func ()
8 0x000000001018e431 in thr_wrapper ()
9 0x000000001030e536 in _pthread_start ()
10 0x000000001030e3e9 in thread_start ()
May be it is RAM that is the factor? This MBA has 2GBs. EDIT: Unlikely.
97d40b8 seemed to help a bit, but I am not sure
Getting rid of erlang wrapper for threads help. Now I am wondering what are those yet-unseen consequences of dropping erlang threads?