python /home/admin/mtr/script_for_cron.py -j datou_current3 -m 20 -a ' -a 3318 ' -s datou_3318 -M 0 -S 0 -U 95,95,120 import MySQLdb succeeded Import error (python version) ['/Users/moilerat/Documents/Fotonower/install/caffe/distribute/python', '/home/admin/workarea/git/Velours/python/prod', '/home/admin/workarea/install/caffe_cuda8_python3/python', '/home/admin/workarea/install/darknet', '/home/admin/workarea/git/Velours/python', '/home/admin/workarea/install/caffe_frcnn_python3/py-faster-rcnn/caffe-fast-rcnn/python', '/home/admin/mtr/.credentials', '/home/admin/workarea/install/caffe/python', '/home/admin/workarea/install/caffe_frcnn/py-faster-rcnn/tools', '/home/admin/workarea/git/fotonowerpip', '/home/admin/workarea/install/segment-anything', '/home/admin/workarea/git/pyfvs', '/usr/lib/python38.zip', '/usr/lib/python3.8', '/usr/lib/python3.8/lib-dynload', '/home/admin/.local/lib/python3.8/site-packages', '/usr/local/lib/python3.8/dist-packages', '/usr/lib/python3/dist-packages'] process id : 2030337 load datou : 3318 # VR 17-11-17 : to create in DB ! Here we check the datou graph and we reorder steps ! Tree builded and cycle checked, now we need to re-order the steps ! We have currenlty an error because there is no dependence between the last step for the case tile - detect - glue We can either keep the depence of, it is better to keep an order compatible with the id of steps if we do not have sons, so a lexical order : (number_son, step_id) All sons are already in current list ! All sons are already in current list ! All sons are already in current list ! All sons are already in current list ! All sons are already in current list ! All sons are already in current list ! All sons are already in current list ! All sons are already in current list ! All sons are already in current list ! DONE and to test : checkNoCycle ! Here we check the consistency of inputs/outputs number between the given ones and the db ! eke 1-6-18 : checkConsistencyNbInputNbOutput should be processed after step reordering ! WARNING : number of outputs for step 7928 mask_detect is not consistent : 3 used against 2 in the step definition ! Step 8092 crop_condition have less inputs used (1) than in the step definition (2) : maybe we manage optionnal inputs ! WARNING : number of outputs for step 8092 crop_condition is not consistent : 4 used against 3 in the step definition ! WARNING : number of inputs for step 7933 rle_unique_nms_with_priority is not consistent : 2 used against 1 in the step definition ! WARNING : number of outputs for step 7933 rle_unique_nms_with_priority is not consistent : 2 used against 1 in the step definition ! WARNING : number of outputs for step 7935 ventilate_hashtags_in_portfolio is not consistent : 2 used against 1 in the step definition ! Step 7934 final have less inputs used (2) than in the step definition (3) : maybe we manage optionnal inputs ! Step 7934 final have less outputs used (1) than in the step definition (2) : some outputs may be not used ! WARNING : number of outputs for step 13649 velours_tree is not consistent : 2 used against 1 in the step definition ! Step 9283 split_time_score have less inputs used (1) than in the step definition (2) : maybe we manage optionnal inputs ! Number of inputs / outputs for each step checked ! Here we check the consistency of outputs/inputs types during steps connections eke 1-6-18 : checkConsistencyTypeOutputInput should be processed after checkConsistencyNbInputNbOutput ! We ignore checkConsistencyTypeOutputInput for datou_step final ! WARNING : type of output 1 of step 7935 doesn't seem to be define in the database( WARNING : type of input 3 of step 7934 doesn't seem to be define in the database( We ignore checkConsistencyTypeOutputInput for datou_step final ! WARNING : type of input 1 of step 7935 doesn't seem to be define in the database( WARNING : output 1 of step 7933 have datatype=7 whereas input 1 of step 7935 have datatype=None WARNING : type of output 2 of step 7928 doesn't seem to be define in the database( WARNING : type of input 2 of step 8092 doesn't seem to be define in the database( WARNING : type of output 3 of step 8092 doesn't seem to be define in the database( WARNING : type of input 1 of step 7933 doesn't seem to be define in the database( WARNING : type of output 2 of step 7928 doesn't seem to be define in the database( WARNING : type of input 1 of step 10917 doesn't seem to be define in the database( WARNING : type of output 2 of step 7928 doesn't seem to be define in the database( WARNING : type of input 1 of step 10918 doesn't seem to be define in the database( We ignore checkConsistencyTypeOutputInput for datou_step final ! WARNING : output 0 of step 7935 have datatype=10 whereas input 3 of step 10916 have datatype=6 WARNING : output 0 of step 7935 have datatype=10 whereas input 0 of step 13649 have datatype=18 WARNING : type of output 1 of step 13649 doesn't seem to be define in the database( WARNING : type of input 5 of step 10916 doesn't seem to be define in the database( DataTypes for each output/input checked ! Unexpected type for variable list_input_json ERROR or WARNING : can't parse json string Expecting value: line 1 column 1 (char 0) Tried to parse : chemin de la photo was removed should we ? (photo_id, hashtag_id, score_max) was removed should we ? [(photo_id, hashtag_id, hashtag_type, x0, x1, y0, y1, score, seg_temp, polygons), ...] was removed should we ? chemin de la photo was removed should we ? [ (photo_id_loc, hashtag_id, hashtag_type, x0, x1, y0, y1, score, None), ...] was removed should we ? chemin de la photo was removed should we ? id de la photo (peut être local ou global) was removed should we ? chemin de la photo was removed should we ? (x0, y0, x1, y1) was removed should we ? chemin de la photo was removed should we ? donnée sous forme de texte was removed should we ? [ (photo_id, photo_id_loc, hashtag_type, x0, x1, y0, y1, score), ...] was removed should we ? None was removed should we ? donnée sous forme de texte was removed should we ? (photo_id, hashtag_id, score_max) was removed should we ? id de la photo (peut être local ou global) was removed should we ? donnée sous forme de texte was removed should we ? donnée sous forme de texte was removed should we ? donnée sous forme de texte was removed should we ? chemin de la photo was removed should we ? (photo_id, hashtag_id, score_max) was removed should we ? chemin de la photo was removed should we ? (photo_id, hashtag_id, score_max) was removed should we ? None was removed should we ? donnée sous forme de nombre was removed should we ? (photo_id, hashtag_id, score_max) was removed should we ? (photo_id, hashtag_id, score_max) was removed should we ? (photo_id, hashtag_id, score_max) was removed should we ? (photo_id, hashtag_id, score_max) was removed should we ? (photo_id, hashtag_id, score_max) was removed should we ? donnée sous forme de texte was removed should we ? None was removed should we ? donnée sous forme de texte was removed should we ? [ptf_id0,ptf_id1...] was removed should we ? FOUND : 1 Here is data_from_sql_as_vec to set the ParamDescriptorType : (5275, 'learn_RUBBIA_REFUS_AMIENS_23', 16384, 25088, 'learn_RUBBIA_REFUS_AMIENS_23', 'pool5', 10.0, None, None, 256, None, 0, None, 8, None, None, -1000.0, 1, datetime.datetime(2021, 4, 23, 14, 19, 39), datetime.datetime(2021, 4, 23, 14, 19, 39)) load thcls load THCL from format json or kwargs add thcl : 2847 in CacheModelConfig load pdts add pdt : 5275 in CacheModelConfig Running datou job : batch_current TODO datou_current to load to do maybe to take outside batchDatouExec updating current state to 1 list_input_json: [] Current got : datou_id : 3318, datou_cur_ids : ['2808944'] with mtr_portfolio_ids : ['22803397'] and first list_photo_ids : [] new path : /proc/2030337/ Inside batchDatouExec : verbose : 0 # VR 17-11-17 : to create in DB ! Here we check the datou graph and we reorder steps ! Tree builded and cycle checked, now we need to re-order the steps ! We have currenlty an error because there is no dependence between the last step for the case tile - detect - glue We can either keep the depence of, it is better to keep an order compatible with the id of steps if we do not have sons, so a lexical order : (number_son, step_id) All sons are already in current list ! All sons are already in current list ! All sons are already in current list ! All sons are already in current list ! All sons are already in current list ! All sons are already in current list ! All sons are already in current list ! All sons are already in current list ! All sons are already in current list ! DONE and to test : checkNoCycle ! Here we check the consistency of inputs/outputs number between the given ones and the db ! eke 1-6-18 : checkConsistencyNbInputNbOutput should be processed after step reordering ! WARNING : number of outputs for step 7928 mask_detect is not consistent : 3 used against 2 in the step definition ! Step 8092 crop_condition have less inputs used (1) than in the step definition (2) : maybe we manage optionnal inputs ! WARNING : number of outputs for step 8092 crop_condition is not consistent : 4 used against 3 in the step definition ! WARNING : number of inputs for step 7933 rle_unique_nms_with_priority is not consistent : 2 used against 1 in the step definition ! WARNING : number of outputs for step 7933 rle_unique_nms_with_priority is not consistent : 2 used against 1 in the step definition ! WARNING : number of outputs for step 7935 ventilate_hashtags_in_portfolio is not consistent : 2 used against 1 in the step definition ! Step 7934 final have less inputs used (2) than in the step definition (3) : maybe we manage optionnal inputs ! Step 7934 final have less outputs used (1) than in the step definition (2) : some outputs may be not used ! WARNING : number of outputs for step 13649 velours_tree is not consistent : 2 used against 1 in the step definition ! Step 9283 split_time_score have less inputs used (1) than in the step definition (2) : maybe we manage optionnal inputs ! Number of inputs / outputs for each step checked ! Here we check the consistency of outputs/inputs types during steps connections eke 1-6-18 : checkConsistencyTypeOutputInput should be processed after checkConsistencyNbInputNbOutput ! We ignore checkConsistencyTypeOutputInput for datou_step final ! WARNING : type of output 1 of step 7935 doesn't seem to be define in the database( WARNING : type of input 3 of step 7934 doesn't seem to be define in the database( We ignore checkConsistencyTypeOutputInput for datou_step final ! WARNING : type of input 1 of step 7935 doesn't seem to be define in the database( WARNING : output 1 of step 7933 have datatype=7 whereas input 1 of step 7935 have datatype=None WARNING : type of output 2 of step 7928 doesn't seem to be define in the database( WARNING : type of input 2 of step 8092 doesn't seem to be define in the database( WARNING : type of output 3 of step 8092 doesn't seem to be define in the database( WARNING : type of input 1 of step 7933 doesn't seem to be define in the database( WARNING : type of output 2 of step 7928 doesn't seem to be define in the database( WARNING : type of input 1 of step 10917 doesn't seem to be define in the database( WARNING : type of output 2 of step 7928 doesn't seem to be define in the database( WARNING : type of input 1 of step 10918 doesn't seem to be define in the database( We ignore checkConsistencyTypeOutputInput for datou_step final ! WARNING : output 0 of step 7935 have datatype=10 whereas input 3 of step 10916 have datatype=6 WARNING : output 0 of step 7935 have datatype=10 whereas input 0 of step 13649 have datatype=18 WARNING : type of output 1 of step 13649 doesn't seem to be define in the database( WARNING : type of input 5 of step 10916 doesn't seem to be define in the database( DataTypes for each output/input checked ! List Step Type Loaded in datou : mask_detect, crop_condition, rle_unique_nms_with_priority, ventilate_hashtags_in_portfolio, final, blur_detection, brightness, velours_tree, send_mail_cod, split_time_score over limit max, limiting to limit_max 40 list_input_json : [] origin We have 1 , BFBFBFBFBFBFBFBFwe have missing 0 photos in the step download2025-05-08 21:00:45.538679: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcublas.so.10 2025-05-08 21:00:45.699097: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcudnn.so.7 2025-05-08 21:00:47.634120: I tensorflow/stream_executor/cuda/cuda_driver.cc:763] failed to allocate 2.86G (3068002304 bytes) from device: CUDA_ERROR_OUT_OF_MEMORY: out of memory 2025-05-08 21:00:47.634753: I tensorflow/stream_executor/cuda/cuda_driver.cc:763] failed to allocate 2.57G (2761201920 bytes) from device: CUDA_ERROR_OUT_OF_MEMORY: out of memory 2025-05-08 21:00:47.635347: I tensorflow/stream_executor/cuda/cuda_driver.cc:763] failed to allocate 2.31G (2485081600 bytes) from device: CUDA_ERROR_OUT_OF_MEMORY: out of memory 2025-05-08 21:00:47.635927: I tensorflow/stream_executor/cuda/cuda_driver.cc:763] failed to allocate 2.08G (2236573440 bytes) from device: CUDA_ERROR_OUT_OF_MEMORY: out of memory 2025-05-08 21:00:47.635955: W tensorflow/core/common_runtime/bfc_allocator.cc:245] Allocator (GPU_0_bfc) ran out of memory trying to allocate 2.06GiB with freed_by_count=0. The caller indicates that this is not a failure, but may mean that there could be performance gains if more memory were available. 2025-05-08 21:00:47.636555: I tensorflow/stream_executor/cuda/cuda_driver.cc:763] failed to allocate 2.86G (3068002304 bytes) from device: CUDA_ERROR_OUT_OF_MEMORY: out of memory 2025-05-08 21:00:47.636571: W tensorflow/core/common_runtime/bfc_allocator.cc:245] Allocator (GPU_0_bfc) ran out of memory trying to allocate 2.06GiB with freed_by_count=0. The caller indicates that this is not a failure, but may mean that there could be performance gains if more memory were available. 2025-05-08 21:00:47.648588: I tensorflow/stream_executor/cuda/cuda_driver.cc:763] failed to allocate 2.86G (3068002304 bytes) from device: CUDA_ERROR_OUT_OF_MEMORY: out of memory 2025-05-08 21:00:47.648615: W tensorflow/core/common_runtime/bfc_allocator.cc:245] Allocator (GPU_0_bfc) ran out of memory trying to allocate 2.06GiB with freed_by_count=0. The caller indicates that this is not a failure, but may mean that there could be performance gains if more memory were available. 2025-05-08 21:00:47.649208: I tensorflow/stream_executor/cuda/cuda_driver.cc:763] failed to allocate 2.86G (3068002304 bytes) from device: CUDA_ERROR_OUT_OF_MEMORY: out of memory 2025-05-08 21:00:47.649224: W tensorflow/core/common_runtime/bfc_allocator.cc:245] Allocator (GPU_0_bfc) ran out of memory trying to allocate 2.06GiB with freed_by_count=0. The caller indicates that this is not a failure, but may mean that there could be performance gains if more memory were available. 2025-05-08 21:00:47.658511: I tensorflow/stream_executor/cuda/cuda_driver.cc:763] failed to allocate 2.86G (3068002304 bytes) from device: CUDA_ERROR_OUT_OF_MEMORY: out of memory 2025-05-08 21:00:47.658538: W tensorflow/core/common_runtime/bfc_allocator.cc:245] Allocator (GPU_0_bfc) ran out of memory trying to allocate 466.56MiB with freed_by_count=0. The caller indicates that this is not a failure, but may mean that there could be performance gains if more memory were available. 2025-05-08 21:00:47.659138: I tensorflow/stream_executor/cuda/cuda_driver.cc:763] failed to allocate 2.86G (3068002304 bytes) from device: CUDA_ERROR_OUT_OF_MEMORY: out of memory 2025-05-08 21:00:47.659168: W tensorflow/core/common_runtime/bfc_allocator.cc:245] Allocator (GPU_0_bfc) ran out of memory trying to allocate 466.56MiB with freed_by_count=0. The caller indicates that this is not a failure, but may mean that there could be performance gains if more memory were available. 2025-05-08 21:00:47.712748: I tensorflow/stream_executor/cuda/cuda_driver.cc:763] failed to allocate 2.86G (3068002304 bytes) from device: CUDA_ERROR_OUT_OF_MEMORY: out of memory 2025-05-08 21:00:47.712789: W tensorflow/core/common_runtime/bfc_allocator.cc:245] Allocator (GPU_0_bfc) ran out of memory trying to allocate 2.06GiB with freed_by_count=0. The caller indicates that this is not a failure, but may mean that there could be performance gains if more memory were available. 2025-05-08 21:00:47.713381: I tensorflow/stream_executor/cuda/cuda_driver.cc:763] failed to allocate 2.86G (3068002304 bytes) from device: CUDA_ERROR_OUT_OF_MEMORY: out of memory 2025-05-08 21:00:47.713397: W tensorflow/core/common_runtime/bfc_allocator.cc:245] Allocator (GPU_0_bfc) ran out of memory trying to allocate 2.06GiB with freed_by_count=0. The caller indicates that this is not a failure, but may mean that there could be performance gains if more memory were available. 2025-05-08 21:00:47.721695: I tensorflow/stream_executor/cuda/cuda_driver.cc:763] failed to allocate 2.86G (3068002304 bytes) from device: CUDA_ERROR_OUT_OF_MEMORY: out of memory 2025-05-08 21:00:47.721721: W tensorflow/core/common_runtime/bfc_allocator.cc:245] Allocator (GPU_0_bfc) ran out of memory trying to allocate 243.25MiB with freed_by_count=0. The caller indicates that this is not a failure, but may mean that there could be performance gains if more memory were available. 2025-05-08 21:00:47.722309: I tensorflow/stream_executor/cuda/cuda_driver.cc:763] failed to allocate 2.86G (3068002304 bytes) from device: CUDA_ERROR_OUT_OF_MEMORY: out of memory 2025-05-08 21:00:47.722325: W tensorflow/core/common_runtime/bfc_allocator.cc:245] Allocator (GPU_0_bfc) ran out of memory trying to allocate 243.25MiB with freed_by_count=0. The caller indicates that this is not a failure, but may mean that there could be performance gains if more memory were available. 2025-05-08 21:00:47.783893: I tensorflow/stream_executor/cuda/cuda_driver.cc:763] failed to allocate 2.86G (3068002304 bytes) from device: CUDA_ERROR_OUT_OF_MEMORY: out of memory 2025-05-08 21:00:47.784647: I tensorflow/stream_executor/cuda/cuda_driver.cc:763] failed to allocate 2.86G (3068002304 bytes) from device: CUDA_ERROR_OUT_OF_MEMORY: out of memory 2025-05-08 21:00:47.788025: I tensorflow/stream_executor/cuda/cuda_driver.cc:763] failed to allocate 2.86G (3068002304 bytes) from device: CUDA_ERROR_OUT_OF_MEMORY: out of memory 2025-05-08 21:00:47.788683: I tensorflow/stream_executor/cuda/cuda_driver.cc:763] failed to allocate 2.86G (3068002304 bytes) from device: CUDA_ERROR_OUT_OF_MEMORY: out of memory 2025-05-08 21:00:47.845821: I tensorflow/stream_executor/cuda/cuda_driver.cc:763] failed to allocate 2.86G (3068002304 bytes) from device: CUDA_ERROR_OUT_OF_MEMORY: out of memory 2025-05-08 21:00:47.846528: I tensorflow/stream_executor/cuda/cuda_driver.cc:763] failed to allocate 2.86G (3068002304 bytes) from device: CUDA_ERROR_OUT_OF_MEMORY: out of memory 2025-05-08 21:00:47.849749: I tensorflow/stream_executor/cuda/cuda_driver.cc:763] failed to allocate 2.86G (3068002304 bytes) from device: CUDA_ERROR_OUT_OF_MEMORY: out of memory 2025-05-08 21:00:47.850366: I tensorflow/stream_executor/cuda/cuda_driver.cc:763] failed to allocate 2.86G (3068002304 bytes) from device: CUDA_ERROR_OUT_OF_MEMORY: out of memory 2025-05-08 21:00:47.889076: I tensorflow/stream_executor/cuda/cuda_driver.cc:763] failed to allocate 2.86G (3068002304 bytes) from device: CUDA_ERROR_OUT_OF_MEMORY: out of memory 2025-05-08 21:00:47.890007: I tensorflow/stream_executor/cuda/cuda_driver.cc:763] failed to allocate 2.86G (3068002304 bytes) from device: CUDA_ERROR_OUT_OF_MEMORY: out of memory 2025-05-08 21:00:47.892638: I tensorflow/stream_executor/cuda/cuda_driver.cc:763] failed to allocate 2.86G (3068002304 bytes) from device: CUDA_ERROR_OUT_OF_MEMORY: out of memory 2025-05-08 21:00:47.893477: I tensorflow/stream_executor/cuda/cuda_driver.cc:763] failed to allocate 2.86G (3068002304 bytes) from device: CUDA_ERROR_OUT_OF_MEMORY: out of memory 2025-05-08 21:00:47.900181: I tensorflow/stream_executor/cuda/cuda_driver.cc:763] failed to allocate 2.86G (3068002304 bytes) from device: CUDA_ERROR_OUT_OF_MEMORY: out of memory 2025-05-08 21:00:47.900833: I tensorflow/stream_executor/cuda/cuda_driver.cc:763] failed to allocate 2.86G (3068002304 bytes) from device: CUDA_ERROR_OUT_OF_MEMORY: out of memory 2025-05-08 21:00:47.903489: I tensorflow/stream_executor/cuda/cuda_driver.cc:763] failed to allocate 2.86G (3068002304 bytes) from device: CUDA_ERROR_OUT_OF_MEMORY: out of memory 2025-05-08 21:00:47.904094: I tensorflow/stream_executor/cuda/cuda_driver.cc:763] failed to allocate 2.86G (3068002304 bytes) from device: CUDA_ERROR_OUT_OF_MEMORY: out of memory 2025-05-08 21:00:47.912953: I tensorflow/stream_executor/cuda/cuda_driver.cc:763] failed to allocate 2.86G (3068002304 bytes) from device: CUDA_ERROR_OUT_OF_MEMORY: out of memory 2025-05-08 21:00:47.913691: I tensorflow/stream_executor/cuda/cuda_driver.cc:763] failed to allocate 2.86G (3068002304 bytes) from device: CUDA_ERROR_OUT_OF_MEMORY: out of memory 2025-05-08 21:00:47.915668: I tensorflow/stream_executor/cuda/cuda_driver.cc:763] failed to allocate 2.86G (3068002304 bytes) from device: CUDA_ERROR_OUT_OF_MEMORY: out of memory 2025-05-08 21:00:47.916419: I tensorflow/stream_executor/cuda/cuda_driver.cc:763] failed to allocate 2.86G (3068002304 bytes) from device: CUDA_ERROR_OUT_OF_MEMORY: out of memory 2025-05-08 21:00:47.952147: I tensorflow/stream_executor/cuda/cuda_driver.cc:763] failed to allocate 2.86G (3068002304 bytes) from device: CUDA_ERROR_OUT_OF_MEMORY: out of memory 2025-05-08 21:00:47.953109: I tensorflow/stream_executor/cuda/cuda_driver.cc:763] failed to allocate 2.86G (3068002304 bytes) from device: CUDA_ERROR_OUT_OF_MEMORY: out of memory 2025-05-08 21:00:47.954167: I tensorflow/stream_executor/cuda/cuda_driver.cc:763] failed to allocate 2.86G (3068002304 bytes) from device: CUDA_ERROR_OUT_OF_MEMORY: out of memory 2025-05-08 21:00:47.955084: I tensorflow/stream_executor/cuda/cuda_driver.cc:763] failed to allocate 2.86G (3068002304 bytes) from device: CUDA_ERROR_OUT_OF_MEMORY: out of memory 2025-05-08 21:00:47.958928: I tensorflow/stream_executor/cuda/cuda_driver.cc:763] failed to allocate 2.86G (3068002304 bytes) from device: CUDA_ERROR_OUT_OF_MEMORY: out of memory 2025-05-08 21:00:47.959534: I tensorflow/stream_executor/cuda/cuda_driver.cc:763] failed to allocate 2.86G (3068002304 bytes) from device: CUDA_ERROR_OUT_OF_MEMORY: out of memory 2025-05-08 21:00:47.975859: I tensorflow/stream_executor/cuda/cuda_driver.cc:763] failed to allocate 2.86G (3068002304 bytes) from device: CUDA_ERROR_OUT_OF_MEMORY: out of memory 2025-05-08 21:00:47.976469: I tensorflow/stream_executor/cuda/cuda_driver.cc:763] failed to allocate 2.86G (3068002304 bytes) from device: CUDA_ERROR_OUT_OF_MEMORY: out of memory 2025-05-08 21:00:47.977063: I tensorflow/stream_executor/cuda/cuda_driver.cc:763] failed to allocate 2.86G (3068002304 bytes) from device: CUDA_ERROR_OUT_OF_MEMORY: out of memory 2025-05-08 21:00:47.977654: I tensorflow/stream_executor/cuda/cuda_driver.cc:763] failed to allocate 2.86G (3068002304 bytes) from device: CUDA_ERROR_OUT_OF_MEMORY: out of memory 2025-05-08 21:00:47.990670: I tensorflow/stream_executor/cuda/cuda_driver.cc:763] failed to allocate 2.86G (3068002304 bytes) from device: CUDA_ERROR_OUT_OF_MEMORY: out of memory 2025-05-08 21:00:47.991690: I tensorflow/stream_executor/cuda/cuda_driver.cc:763] failed to allocate 2.86G (3068002304 bytes) from device: CUDA_ERROR_OUT_OF_MEMORY: out of memory 2025-05-08 21:00:47.992311: I tensorflow/stream_executor/cuda/cuda_driver.cc:763] failed to allocate 2.86G (3068002304 bytes) from device: CUDA_ERROR_OUT_OF_MEMORY: out of memory 2025-05-08 21:00:47.992924: I tensorflow/stream_executor/cuda/cuda_driver.cc:763] failed to allocate 2.86G (3068002304 bytes) from device: CUDA_ERROR_OUT_OF_MEMORY: out of memory 2025-05-08 21:00:47.998604: I tensorflow/stream_executor/cuda/cuda_driver.cc:763] failed to allocate 2.86G (3068002304 bytes) from device: CUDA_ERROR_OUT_OF_MEMORY: out of memory 2025-05-08 21:00:47.999191: I tensorflow/stream_executor/cuda/cuda_driver.cc:763] failed to allocate 2.86G (3068002304 bytes) from device: CUDA_ERROR_OUT_OF_MEMORY: out of memory 2025-05-08 21:00:48.004863: I tensorflow/stream_executor/cuda/cuda_driver.cc:763] failed to allocate 2.86G (3068002304 bytes) from device: CUDA_ERROR_OUT_OF_MEMORY: out of memory 2025-05-08 21:00:48.005438: I tensorflow/stream_executor/cuda/cuda_driver.cc:763] failed to allocate 2.86G (3068002304 bytes) from device: CUDA_ERROR_OUT_OF_MEMORY: out of memory 2025-05-08 21:00:48.033930: E tensorflow/stream_executor/cuda/cuda_driver.cc:910] failed to synchronize the stop event: CUDA_ERROR_ILLEGAL_ADDRESS: an illegal memory access was encountered 2025-05-08 21:00:48.033970: E tensorflow/stream_executor/gpu/gpu_timer.cc:55] Internal: Error destroying CUDA event: CUDA_ERROR_ILLEGAL_ADDRESS: an illegal memory access was encountered 2025-05-08 21:00:48.033983: E tensorflow/stream_executor/gpu/gpu_timer.cc:60] Internal: Error destroying CUDA event: CUDA_ERROR_ILLEGAL_ADDRESS: an illegal memory access was encountered 2025-05-08 21:00:48.034007: I tensorflow/stream_executor/cuda/cuda_driver.cc:763] failed to allocate 8B (8 bytes) from device: CUDA_ERROR_ILLEGAL_ADDRESS: an illegal memory access was encountered 2025-05-08 21:00:48.034021: E tensorflow/stream_executor/stream.cc:5485] Internal: Failed to enqueue async memset operation: CUDA_ERROR_ILLEGAL_ADDRESS: an illegal memory access was encountered 2025-05-08 21:00:48.034040: W tensorflow/core/kernels/gpu_utils.cc:69] Failed to check cudnn convolutions for out-of-bounds reads and writes with an error message: 'Failed to load in-memory CUBIN: CUDA_ERROR_ILLEGAL_ADDRESS: an illegal memory access was encountered'; skipping this check. This only means that we won't check cudnn for out-of-bounds reads and writes. This message will only be printed once. 2025-05-08 21:00:48.034053: I tensorflow/stream_executor/cuda/cuda_driver.cc:763] failed to allocate 8B (8 bytes) from device: CUDA_ERROR_ILLEGAL_ADDRESS: an illegal memory access was encountered 2025-05-08 21:00:48.034070: I tensorflow/stream_executor/stream.cc:4963] [stream=0x178d8150,impl=0x178d7140] did not memzero GPU location; source: 0x7f26667fa020 2025-05-08 21:00:48.034478: F ./tensorflow/core/kernels/conv_2d_gpu.h:665] Non-OK-status: GpuLaunchKernel( SwapDimension1And2InTensor3UsingTiles, total_tiles_count, NumThreads, 0, d.stream(), input, input_dims, output) status: Internal: an illegal memory access was encountered max_time_sub_proc : 3600 Catched exception ! Connect or reconnect ! in case -12 caffe_path_current : About to save ! 2 After save, about to update current ! 11.69user 8.93system 1:00:07elapsed 0%CPU (0avgtext+0avgdata 2640052maxresident)k 1568368inputs+9136outputs (17662major+786202minor)pagefaults 0swaps