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

Creating a new project / clear all memory when an algorithm is running crashes Mantid #12205

Closed
DanNixon opened this issue Mar 16, 2015 · 4 comments
Assignees
Labels
Framework Issues and pull requests related to components in the Framework

Comments

@DanNixon
Copy link
Member

This issue was originally TRAC 11367

To reproduce:

  • Configure the script repository
  • Open Mantid
  • While the script repository is updating (seems to be any time the algorithm is running) click the new project button
  • Mantid terminates with SIGILL
@DanNixon DanNixon added the Framework Issues and pull requests related to components in the Framework label Jun 3, 2015
@NickDraper
Copy link
Contributor

To reproduce:

  1. Run the Pause algorithm with a time of 10
  2. File ->new->new project OR File->clear all lmemory
  3. Crash

@NickDraper NickDraper changed the title Creating a new project when the script repository is updating crashes Mantid Creating a new project when an algorithm is running crashes Mantid Feb 15, 2016
@NickDraper NickDraper changed the title Creating a new project when an algorithm is running crashes Mantid Creating a new project / clear all memory when an algorithm is running crashes Mantid Feb 15, 2016
@NickDraper
Copy link
Contributor

Algorithm manager should be the place to tackle this, in clear/destructor it should attempt to cancel all running algs, give them a short < 1s time to respond before carrying on regardless.

@FedeMPouzols
Copy link
Contributor

I don't think I'll have much chance to tackle this. @DavidFair, @DIMITARTASEV: Have you observed issues like this in recent testing efforts?

@DavidFair
Copy link
Contributor

I've just testing this against the latest build and the issue is no longer present.
Closing as fixed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Framework Issues and pull requests related to components in the Framework
Projects
None yet
Development

No branches or pull requests

4 participants