Alexander Markov

Still failing: ``` ../../runtime/vm/profiler.cc: 141: error: expected: sample_buffer_ != nullptr ===== CRASH ===== si_signo=Segmentation fault(11), si_code=SEGV_MAPERR(1), si_addr=0xababb303 Aborting reentrant request for stack trace. -- BEGIN REPRODUCE -- DART SDK REVISION:...

Crashed once again: ``` ../../runtime/vm/profiler.cc: 150: error: expected: sample_buffer_ != nullptr ===== CRASH ===== si_signo=Segmentation fault(11), si_code=SEGV_MAPERR(1), si_addr=0xababb1ab Aborting reentrant request for stack trace. -- BEGIN REPRODUCE -- DART SDK...

Still failing: ``` ../../runtime/vm/profiler.cc: 150: error: expected: sample_buffer_ != nullptr ===== CRASH ===== si_signo=Segmentation fault(11), si_code=SEGV_MAPERR(1), si_addr=0xababb1a3 Aborting reentrant request for stack trace. -- BEGIN REPRODUCE -- DART SDK REVISION:...

Still failing: [log](https://logs.chromium.org/logs/dart/buildbucket/cr-buildbucket/8700249321578528769/+/u/collect_shards/dartfuzz_-_generated_programs_shard_42/task_stdout_stderr:_dartfuzz_-_generated_programs_shard_42)

I don't think we need to have a strict definition of huge methods in the documentation. It could be just a recommendation to avoid _unreasonably large_ methods and avoid repeated...