-5

I have a problem, the solution to which is not on the Internet. After painstakingly recalculating all combinations at a certain point this error pops up regardless of n _jobs. I am attaching the code below. Please advise, experts. This code is in a for loop.

print(f"\nTrying combinations with {group_size} features:")
feature_groups = combinations(all_feature_names, group_size)
gc.collect()
results.extend(
Parallel(n_jobs=-1)(delayed(process_feature_group)(fg) for fg in feature_groups)

The error contains the following text. "A worker process managed by the executor was unexpectedly terminated. This could be caused by a segmentation fault calling the function or bu an excessive memory usage causing the Operating System to kill the worker." I tried to change the number of jobs in the range : 3;-1.

If there is not enough input data, then write - I will attach. I will be grateful for answers.

New contributor
user30419177 is a new contributor to this site. Take care in asking for clarification, commenting, and answering. Check out our Code of Conduct.
7
  • Are you using itertool? Why did you prefer joblib when there is multiprocessing which is more efficient and a part of standard python library? Commented 7 hours ago
  • 1
    Can you paste the full error? I see a typo in the error, which suggests that you typed it by hand from memory. If you are able to reproduce the issue, then it would be very helpful if you can share the full error. Commented 7 hours ago
  • @suramuthu-r, I'm using the itertools. Joblib seemed to me like a simple library that implementing multiprocessing in python. Commented 6 hours ago
  • @lajos-arpad, I'm typed it from my screenshot. "The instruction at 0x00007FFECD784E3 referenced memory at 0xFFFFFFFFFFF. The memory cannot be read/written.' - this is text on windows contex window showed with this error. I can attach a full code if it will be useful. Commented 6 hours ago
  • @lajos-arpad, original text of Visual studio error:"A worker process managed by the executor was unexpectedly terminated. This could be caused by a segmentation fault while calling the function or by an excessive memory usage causing the Operating System to kill the worker." Commented 6 hours ago

0

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.