Segment fatal (core dump) using 3.8.0

[hajime9652]

but I have solved by uisng 3.7.0.
I just report bag.

$ xnmt examples/01_standard.yaml
[dynet] random seed: 4203878271
[dynet] allocating memory: 512MB
[dynet] memory allocation done.
running XNMT revision ca4eac4 on hoge on 2019-12-13 00:19:58
=> Running standard
> use randomly initialized DyNet weights of all components
  DyNet param count: 5880901
> Training
Starting to read examples/data/head.ja and examples/data/head.en
Done reading examples/data/head.ja and examples/data/head.en. Packing into batches.
Done packing batches.
The dy.parameter(...) call is now DEPRECATED.
        There is no longer need to explicitly add parameters to the computation graph.
        Any used parameter will be added automatically.
Fatal Python error: Segmentation fault

Thread 0x00007f9ca0bc8700 (most recent call first):
  File "/home/sysadmin/.pyenv/versions/3.8.0/lib/python3.8/threading.py", line 306 in wait
  File "/home/sysadmin/.pyenv/versions/3.8.0/lib/python3.8/queue.py", line 179 in get
  File "/home/sysadmin/hoge/venv/lib/python3.8/site-packages/tensorboardX/event_file_writer.py", line 200 in run
  File "/home/sysadmin/.pyenv/versions/3.8.0/lib/python3.8/threading.py", line 932 in _bootstrap_inner
  File "/home/sysadmin/.pyenv/versions/3.8.0/lib/python3.8/threading.py", line 890 in _bootstrap

Current thread 0x00007f9e19e64100 (most recent call first):
  File "/home/sysadmin/hoge/venv/lib/python3.8/site-packages/xnmt-0.0.1-py3.8.egg/xnmt/train/regimens.py", line 41 in backward
  File "/home/sysadmin/hoge/venv/lib/python3.8/site-packages/xnmt-0.0.1-py3.8.egg/xnmt/train/regimens.py", line 161 in run_training
  File "/home/sysadmin/hoge/venv/lib/python3.8/site-packages/xnmt-0.0.1-py3.8.egg/xnmt/experiments.py", line 111 in __call__
  File "/home/sysadmin/hoge/venv/lib/python3.8/site-packages/xnmt-0.0.1-py3.8.egg/xnmt/xnmt_run_experiments.py", line 101 in main
  File "/home/sysadmin/hoge/venv/bin/xnmt", line 11 in <module>
Segmentation fault (core dumped)

[thak123]

facing the same issue. any solution ?