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

reduced effectiveness of raising fatal errors (RMGLog::fatal) in multithreaded runs #200

Open
ManuelHu opened this issue Dec 17, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@ManuelHu
Copy link
Collaborator

  • RMGLog::Out(RMGLog::fatal, ...) is does not terminate the application when called on a worker thread.
  • G4RunManager::GetRunManager()->AbortRun() is also of no use to abort the whole run, if used in any BeginOfRunAction
  • ...also it only works only for the local thread, and not for all threads together.
  • --> there is no clean way to check prerequisites on a worker, and to abort if they are not met

see #198 for a related issue

@ManuelHu ManuelHu changed the title investigate fatal errors in multithreaded context investigate effectiveness of raising fatal errors in multithreaded context Dec 19, 2024
@ManuelHu
Copy link
Collaborator Author

reworded: this is not about fatal errors raised in MT mode, but about our own raising of fatal errors in MT mode, which might not do what we want and expect

@ManuelHu ManuelHu added the bug Something isn't working label Dec 19, 2024
@ManuelHu ManuelHu changed the title investigate effectiveness of raising fatal errors in multithreaded context reduced effectiveness of raising fatal errors (RMGLog::fatal) in multithreaded runs Dec 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant