Ticket #1340 (closed)

Opened 10 years ago

Last modified 5 years ago

Crash when cancelling an algorithm that's writing into a ManagedWorkspace

Reported by: Russell Taylor Owned by: Martyn Gigg
Priority: major Milestone: Iteration 24
Component: Keywords:
Cc: Blocked By:
Blocking: Tester: Roman Tolchenov

Description

If you try to cancel an algorithm where the output's gone managed (in my example the input workspace was an in-memory one) then you get a crash. This happened for CropWorkspace and Plus, but it's probably a general problem because a quick look in the debugger said it had something to do with progress notifications.

Change History

comment:1 Changed 10 years ago by Nick Draper

  • Owner set to Martyn Gigg
  • Status changed from new to assigned

comment:2 Changed 10 years ago by Martyn Gigg

  • Status changed from assigned to accepted

comment:3 Changed 10 years ago by Martyn Gigg

  • Status changed from accepted to verify

I can't seem to reproduce this so I think whatever was causing it must have been inadvertently fixed. I was using the script below to test it. You may have to up to number of loops if you have a fancy big machine. 

for i in range(0,2):
	LoadRaw(Filename="C:/Mantid/trunk/Test/Data/GEM38370.raw",OutputWorkspace="w_" + str(i))

for i in range(0,2):
	CropWorkspace(InputWorkspace="w_1",OutputWorkspace="w_1cut" + str(i),StartWorkspaceIndex="1",EndWorkspaceIndex="5000")

comment:4 Changed 10 years ago by Roman Tolchenov

  • Status changed from verify to verifying
  • Tester set to Roman Tolchenov

comment:5 Changed 10 years ago by Roman Tolchenov

  • Status changed from verifying to closed

comment:6 Changed 5 years ago by Stuart Campbell

This ticket has been transferred to github issue ​2187

Note: See TracTickets for help on using tickets.