-
Notifications
You must be signed in to change notification settings - Fork 5.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
运行识别数字样例崩溃 #11251
Comments
推荐docker解决环境问题,可否使用docker呢? |
是的,是基于docker的。 |
没有线索,试试基于标准版的linux镜像可以跑吗(非jupyternotebook) |
如果以上办法不work,请提供一个可复现的docker image |
基于jupyterhub/k8s-singleuser-sample:5d060de这个镜像跑的 |
您好,此issue在近一个月内暂无更新,我们将于今天内关闭。若在关闭后您仍需跟进提问,可重新开启此问题,我们将在24小时内回复您。因关闭带来的不便我们深表歉意,请您谅解~感谢您对PaddlePaddle的支持! |
基于pip安装的Paddle
$paddle version
PaddlePaddle 0.12.0, compiled with
with_avx: OFF
with_gpu: OFF
with_mkl: ON
with_mkldnn: ON
with_double: OFF
with_python: ON
with_rdma: OFF
with_timer: OFF
$uname -a
Linux fb943f316d3a 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
相关日志:
I0606 22:18:44.254832 344 Util.cpp:166] commandline: --use_gpu=False --trainer_count=1
W0606 22:18:44.254894 344 CpuId.h:112] PaddlePaddle wasn't compiled to use avx instructions, but these are available on your machine and could speed up CPU computations via CMAKE .. -DWITH_AVX=ON
[INFO 2018-06-06 22:18:44,261 layers.py:2716] output for __conv_pool_0___conv: c = 20, h = 24, w = 24, size = 11520
[INFO 2018-06-06 22:18:44,263 layers.py:2858] output for __conv_pool_0___pool: c = 20, h = 12, w = 12, size = 2880
[INFO 2018-06-06 22:18:44,265 layers.py:2716] output for __conv_pool_1___conv: c = 50, h = 8, w = 8, size = 3200
[INFO 2018-06-06 22:18:44,266 layers.py:2858] output for __conv_pool_1___pool: c = 50, h = 4, w = 4, size = 800
I0606 22:18:44.273077 344 GradientMachine.cpp:94] Initing parameters..
I0606 22:18:44.275305 344 GradientMachine.cpp:101] Init parameters done.
*** Aborted at 1528294724 (unix time) try "date -d @1528294724" if you are using GNU date ***
PC: @ 0x0 (unknown)
*** SIGSEGV (@0x50) received by PID 344 (TID 0x7fa7d0414700) from PID 80; stack trace: ***
@ 0x7fa7cfbc8390 (unknown)
@ 0x7fa7d020573c (unknown)
@ 0x7fa7d020e851 (unknown)
@ 0x7fa7d0209564 (unknown)
@ 0x7fa7d020dda9 (unknown)
@ 0x7fa7cf2205ad (unknown)
@ 0x7fa7d0209564 (unknown)
@ 0x7fa7cf220664 __libc_dlopen_mode
@ 0x7fa7cf1f2a85 (unknown)
@ 0x7fa7cfbc5a99 __pthread_once_slow
@ 0x7fa7cf1f2ba4 backtrace
@ 0x7fa7ca655643 (unknown)
@ 0x7fa7ca655b80 (unknown)
@ 0x7fa7ca63c83b (unknown)
@ 0x7fa7cfe2587d PyNumber_Multiply
@ 0x7fa7cfedcb61 PyEval_EvalFrameEx
@ 0x7fa7cfe4ea43 gen_iternext
@ 0x7fa7cfedcfac PyEval_EvalFrameEx
@ 0x7fa7cfe4ea43 gen_iternext
@ 0x7fa7cfedcfac PyEval_EvalFrameEx
@ 0x7fa7cfe4ea43 gen_iternext
@ 0x7fa7cfe4931f enum_next
@ 0x7fa7cfedcfac PyEval_EvalFrameEx
@ 0x7fa7cfee3ced PyEval_EvalCodeEx
@ 0x7fa7cfee0e72 PyEval_EvalFrameEx
@ 0x7fa7cfee3ced PyEval_EvalCodeEx
@ 0x7fa7cfee0e72 PyEval_EvalFrameEx
@ 0x7fa7cfee3ced PyEval_EvalCodeEx
@ 0x7fa7cfee3e22 PyEval_EvalCode
@ 0x7fa7cff0fd72 PyRun_FileExFlags
@ 0x7fa7cff110e9 PyRun_SimpleFileExFlags
@ 0x7fa7cff2700d Py_Main
gzip: stdout: Broken pipe
Segmentation fault (core dumped)
The text was updated successfully, but these errors were encountered: