Bug #96

on windows, the iocoChecker run out of memory when testing fwgc/s4 against itself

Added by Axel Belinfante over 11 years ago. Updated over 10 years ago.

Status:ResolvedStart date:11 Jun 2009
Priority:NormalDue date:
Assignee:-% Done:

100%

Category:-
Target version:1.3.0

Related issues

Related to JTorX - Bug #102: iocoChecker takes too long, and also preparing results fo... Closed 11 Jun 2009
Related to JTorX - Bug #270: uncaught out-of-memory error in IocoCheckerWrapper.getFai... Closed 13 Jan 2010

History

#1 Updated by Axel Belinfante over 10 years ago

  • Status changed from New to Resolved
  • Target version set to 1.3.0
  • % Done changed from 0 to 100

most likely this is fixed by the same changes that fix the 'related issues'.

Also available in: Atom PDF