Open GiusBen opened 4 years ago
Do you happen to have the core dump file? If not, can you enable core dumps, then run again, and upload the core dump and the executable?
Yes, I've uploaded both the dump and the executable here, along with the Makefile (apart from the aforementioned flags, the only other thing I've set is ARCH at line 36). OS is Ubuntu 18.04 x86_64, kernel 4.15.0-55-generic.
The same problem showed with yolov4-tiny. It turned out that max=50
at the and of the .cfg
file was the culprit (I don't know why I set it to 50 when the instruction said to set it to 200 or more).
@GiusBen OK, good to hear you found a fix. It's nevertheless a bug in darknet if it crashes mysteriously simply because some parameter in a config file is incorrect.
I had a quick look at the dump already, but because I'm running Debian Sid I couldn't install all the dependency libraries right away. I'll create an Ubuntu 18.04 chroot to get all the libraries and debugging symbols available, maybe the backtrace reveals a low-hanging fruit to fix.
Hi, I'm not really sure this is an issue, most likely it's me but I've spent this afternoon looking for a way around it to no avail. Basically I'm trying to start a yolov3-tiny training following the instructions here: https://github.com/AlexeyAB/darknet#how-to-train-tiny-yolo-to-detect-your-custom-objects . Any idea why this happens? Thanks in advance.
OS: Ubuntu 18.04 CUDA: 10.1 GPU: GTX 1080 Ti
Makefile flags:
My .cfg: yolov3-tiny_obj.cfg.txt
How I'm starting the training: From a bash script, only containing the command
./darknet detector train data/obj.data ../data/v3-tiny/yolov3-tiny_obj.cfg ../data/v3-tiny/yolov3-tiny.conv.15 -dont_show -mjpeg_port 6007 -map
What I get:
I see the block
output twice, is that expected?
Also, the function
cuda_pull_array
in dark_cuda.c gets called twice, with variablestatus
(line 476) getting assigned 0 the first time and 1 the second (maybe this is what triggers the early exit?).