actionscript 3 - mxmlc - Warning: Failed to parse corrupt data - once project reaches certain size? -


i have long running project compiled modules release, test suite potentially runs tests every module.

the project quite large - around 1250 tests cases (classes), , pulling in around 4000 classes in total. it's asunit3 project test cases listed in 1 alltests.as file.

obviously don't run tests time - suite takes minutes run, of time i'm running focussed tests couple of times day run full suite includes integration tests , on.

as of last few hours of work, i'm no longer able build , run whole suite. have script allows filter tests using package name or class name, can testpackage['modules'] or testpackage['com'] etc. can exclude packages - testallexcept['utils'] , on.

i'm able run , subsets of tests, if try test whole set, get:

warning: failed parse corrupt data. 

if filter out few classes i'm able swf compile , open, it's white box , doesn't run tests. if filter few more fine. doesn't appear matter ones filter - long take around 15 test cases out, fine (though haven't found exact number line between ok / not ok.)

i'm compiling -benchmark , following output:

initial setup: 34ms start loading swcs 7ms running total: 41ms loaded 45 swcs: 253ms precompile: 456ms files: 4013 time: 16087ms linking... 91ms swf encoding... 833ms /users/me/documents/clients/project/bin/projectshellrunner.swf (4888318 bytes) postcompile: 927ms total time: 17312ms peak memory usage: 413 mb (heap: 343, non-heap: 70)  mxmlc finished compiling bin/projectshellrunner.swf in 18 seconds 

as peak memory usage on default heap in mxmlc, increased to

vmargs="-xmx1024m -dsun.io.usecanoncaches=false "  

this doesn't appear have helped.

the way asunit3 , projectsprouts set pulls tests in 1 single alltests.as file. on 2500 lines long , imports 1250 test cases.

is there i'm missing in terms of hard limits on number of classes, class length, number of imports in 1 class, etc? or settings i'm able change other vm heap java? i'm using flex 4.2 mxmlc compiler.

obviously can work around via script run series of subsets instead of 1 single suite, i'd understand why happening.

any clues?


some info based on qs twitter:

  • i'm running mac os x 10.8.5
  • mxmlc running via command line
  • i've tried forcing use 32 bit runtime - no change
  • i've switched mxmlc use headless mode, no change


Comments

Popular posts from this blog

IF statement in MySQL trigger -

c++ - What does MSC in "// appease MSC" comments mean? -

javascript - Blogger related post gadget image Resize s72-c [ Need Expert Help ] -