Evolve getting error

[ferro07]

Hello Dear @glenn-jocher ,

I have evaluated my trained models with different pytorch and different gpu cards, but still I am getting this error.
It gave error after between 10-50 generations. I changed batch size epochs and other settting with no chance. I am using your latest version and yolov5m model...Thanks in advance.
Now, my train evolve stopped (After 10 generations with 20 epochs), but it still uses %96 gpu ram. When I try to evolve again, it gives cuda out of memory. So I need to restart computer, then it is ok.

Traceback (most recent call last):
File "/home/xxx/anaconda3/envs/yolov5/lib/python3.8/tkinter/init.py", line 4014, in del
self.tk.call('image', 'delete', self.name)
RuntimeError: main thread is not in main loop
Exception ignored in: <function Image.del at 0x7fa091edfa60>
Traceback (most recent call last):
File "/home/xxx/anaconda3/envs/yolov5/lib/python3.8/tkinter/init.py", line 4014, in del
self.tk.call('image', 'delete', self.name)
RuntimeError: main thread is not in main loop
Exception ignored in: <function Image.del at 0x7fa091edfa60>
Traceback (most recent call last):
File "/home/xxx/anaconda3/envs/yolov5/lib/python3.8/tkinter/init.py", line 4014, in del
self.tk.call('image', 'delete', self.name)
RuntimeError: main thread is not in main loop
Exception ignored in: <function Image.del at 0x7fa091edfa60>
Traceback (most recent call last):
File "/home/xxx/anaconda3/envs/yolov5/lib/python3.8/tkinter/init.py", line 4014, in del
self.tk.call('image', 'delete', self.name)
RuntimeError: main thread is not in main loop
Tcl_AsyncDelete: async handler deleted by the wrong thread
Aborted (core dumped)

[glenn-jocher]

Hello, thank you for your interest in our work! This issue seems to lack the minimum requirements for a proper response, or is insufficiently detailed for us to help you. Please note that most technical problems are due to:

• Your modified or out-of-date code. If your issue is not reproducible in a new git clone version of this repo we can not debug it. Before going further run this code and verify your issue persists:

$ git clone https://github.com/ultralytics/yolov5 yolov5_new  # clone latest
$ cd yolov5_new
$ python detect.py  # verify detection

# CODE TO REPRODUCE YOUR ISSUE HERE

• Your custom data. If your issue is not reproducible in one of our 3 common datasets (COCO, COCO128, or VOC) we can not debug it. Visit our Custom Training Tutorial for guidelines on training your custom data. Examine train_batch0.jpg and test_batch0.jpg for a sanity check of your labels and images.

• Your environment. If your issue is not reproducible in one of the verified environments below we can not debug it. If you are running YOLOv5 locally, verify your environment meets all of the requirements.txt dependencies specified below. If in doubt, download Python 3.8.0 from https://www.python.org/, create a new venv, and then install requirements.

If none of these apply to you, we suggest you close this issue and raise a new one using the Bug Report template, providing screenshots and minimum viable code to reproduce your issue. Thank you!

Requirements

Python 3.8 or later with all requirements.txt dependencies installed, including torch>=1.6. To install run:

$ pip install -r requirements.txt

Environments

YOLOv5 may be run in any of the following up-to-date verified environments (with all dependencies including CUDA/CUDNN, Python and PyTorch preinstalled):

• Google Colab Notebook with free GPU:
• Kaggle Notebook with free GPU: https://www.kaggle.com/models/ultralytics/yolov5
• Google Cloud Deep Learning VM. See GCP Quickstart Guide
• Docker Image https://hub.docker.com/r/ultralytics/yolov5. See Docker Quickstart Guide

Status

If this badge is green, all YOLOv5 GitHub Actions Continuous Integration (CI) tests are passing. These tests evaluate proper operation of basic YOLOv5 functionality, including training (train.py), testing (test.py), inference (detect.py) and export (export.py) on MacOS, Windows, and Ubuntu.

[Bangbanggetnithecar]

I have this problem too, do you solve it now?

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.