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

Crash The VSI #7282

Closed
OwenArnold opened this issue Jan 28, 2013 · 1 comment
Closed

Crash The VSI #7282

OwenArnold opened this issue Jan 28, 2013 · 1 comment
Assignees
Labels
High Priority An issue or pull request that if not addressed is severe enough to postponse a release. Vates
Milestone

Comments

@OwenArnold
Copy link
Contributor

It's possible to crash both the VSI and the Paraview-standalone via the Rebinning Plugin.

  • Open a MDEventWorkspace in the VSI
  • Select Rebin
  • Rebin the Workspace (hit Apply)
  • From the Thresholding selection choose 'Median and Below'
  • hit Apply -> Crash

I believe this issue has actually been sorted out on the PV 3.98 migration branch.

@OwenArnold
Copy link
Contributor Author

This issue was originally trac ticket 6436

@OwenArnold OwenArnold added High Priority An issue or pull request that if not addressed is severe enough to postponse a release. Vates labels Jun 3, 2015
@OwenArnold OwenArnold self-assigned this Jun 3, 2015
@OwenArnold OwenArnold added this to the Release 2.4 milestone Jun 3, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
High Priority An issue or pull request that if not addressed is severe enough to postponse a release. Vates
Projects
None yet
Development

No branches or pull requests

1 participant