Closed JessieMeng closed 6 years ago
我在计算auc的时候是可以计算的 ,但是在预测时候却预测不了,而且把空值判断了也没行,还是报错,auc和预测的区别在于input不同报错
F0921 20:23:53.614132 22409 MemoryHandle.cpp:49] Check failed: size != 0 allocate 0 bytes
*** Check failure stack trace: ***
@ 0x7f8b2e4e3e6d google::LogMessage::Fail()
@ 0x7f8b2e4e791c google::LogMessage::SendToLog()
@ 0x7f8b2e4e3993 google::LogMessage::Flush()
@ 0x7f8b2e4e8e2e google::LogMessageFatal::~LogMessageFatal()
@ 0x7f8b2e44fb39 paddle::CpuMemoryHandle::CpuMemoryHandle()
@ 0x7f8b2e4256be paddle::CpuVectorT<>::CpuVectorT()
@ 0x7f8b2e42639a paddle::VectorT<>::create()
@ 0x7f8b2e4cce02 IVector::create()
@ 0x7f8b2e1cef87 _wrap_IVector_create
@ 0x4a9e33 PyEval_EvalFrameEx
@ 0x4ad70d PyEval_EvalCodeEx
@ 0x4aa88c PyEval_EvalFrameEx
@ 0x4aa9a7 PyEval_EvalFrameEx
@ 0x4aa9a7 PyEval_EvalFrameEx
@ 0x4ad70d PyEval_EvalCodeEx
@ 0x51c1f0 function_call
@ 0x4243c3 PyObject_Call
@ 0x427b3d instancemethod_call
@ 0x4243c3 PyObject_Call
@ 0x4a79f6 PyEval_EvalFrameEx
@ 0x4ad70d PyEval_EvalCodeEx
@ 0x4aa88c PyEval_EvalFrameEx
@ 0x4ad70d PyEval_EvalCodeEx
@ 0x51c1f0 function_call
@ 0x4243c3 PyObject_Call
@ 0x427b3d instancemethod_call
@ 0x4243c3 PyObject_Call
@ 0x479685 slot_tp_call
@ 0x4243c3 PyObject_Call
@ 0x4a79f6 PyEval_EvalFrameEx
@ 0x519db3 gen_iternext
@ 0x4a69dc PyEval_EvalFrameEx
Aborted (core dumped)
@JessieMeng 请贴出相关代码或疑问的部分,目前贴的相关配置,信息量太大,不利于定位问题。
Close the inactivate issue.