Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Exception: "an exception occured at line 641" #1

Open
neon5d opened this issue Feb 8, 2022 · 3 comments
Open

Exception: "an exception occured at line 641" #1

neon5d opened this issue Feb 8, 2022 · 3 comments

Comments

@neon5d
Copy link

neon5d commented Feb 8, 2022

Hello,

I observed the exception "an exception occured at line 641" while running the program.
Initially, there are no exceptions but it happens more frequently while running the program although the program can still run.
What are the root causes and how can I avoid this exception?
I tried to adjust the parameters(num_bigchunkloaders, interval_resched, and maxlength_queue_smallchunk), but it didn't work.

@amirakbarnejad
Copy link
Owner

Hi neon5,
The exception occurs when a bigchunk is removed from memory and the the bigchunk's queue of smallchunks is being collected before removing the bigchunk.
A quick fix is to set the dataloader argument flag_grabqueue_onunsched to False. Note that this is not a good practice for SlidingWindowDL, but should be fine when, e.g., training a machine learning model.
After printing "an exception occured at line 641", pydmed prints more information about the exception. Could you please provide here the additional information that pydmed prints?

@neon5d
Copy link
Author

neon5d commented Feb 9, 2022

Thank you for your quick reply.
In my case,
print(str(e)) does not show any messages (It seems only has the next line)
If you give any updates, I can try to catch the message.

After setting flag_grabqueue_onunsched to be False, no more the exception.
Thank you for your help.

@amirakbarnejad
Copy link
Owner

It turned out that even when that line fails, all smallchunks are correctly collected.
So I changed the error to a warning:

print("Warning: Some smallchunks may have lost. If not, you can safely ignore this warning.")

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants