[Browser test] console.log weirdness

[jeremymeng]

I added some console.log() calls in one storage-file-share test FileClient.ts, namely

• console.log("# beforeEach"); in beforeEach()
• console.log("# afterEach"); in afterEach()
• console.log("# uploadRange with progress event"); in the corresponding test case.

when running browser tests. A log of \\ got dumped onto the screen

At the end I got V8 out-of-memory error

<--- Last few GCs --->

[22704:000002BBC5FDCF70] 111008 ms: Mark-sweep 1373.7 (1431.2) -> 1373.7 (1436.7) MB, 71.1 / 0.0 ms (average mu = 0.110, current mu = 0.027) allocation failure scavenge might not succeed
[22704:000002BBC5FDCF70] 111085 ms: Mark-sweep 1377.0 (1436.7) -> 1376.9 (1437.2) MB, 73.0 / 0.0 ms (average mu = 0.082, current mu = 0.053) allocation failure scavenge might not succeed

<--- JS stacktrace --->

==== JS stack trace =========================================

0: ExitFrame [pc: 000002A1F2EDC5C1]

Security context: 0x03ab0391e6e9
1: toString [000001AB9B81ED59] [buffer.js:645] [bytecode=0000012C53250811 offset=31](this=0x03eb0460ffe1 ,encoding=0x0029c0a026f1 ,start=0x0029c0a026f1 ,end=0x0029c0a026f1 )
2: arguments adaptor frame: 0->3
3: StubFrame [pc: 000002A1F2E94111]
4: StubFrame [pc: 000002A1F2EDE...

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
1: 00007FF68FA4F04A v8::internal::GCIdleTimeHandler::GCIdleTimeHandler+5114
2: 00007FF68FA2A0C6 node::MakeCallback+4518
3: 00007FF68FA2AA30 node_module_register+2032
4: 00007FF68FCB20EE v8::internal::FatalProcessOutOfMemory+846
5: 00007FF68FCB201F v8::internal::FatalProcessOutOfMemory+639
6: 00007FF6901D2BC4 v8::internal::Heap::MaxHeapGrowingFactor+9556
7: 00007FF6901C9C46 v8::internal::ScavengeJob::operator=+24310
8: 00007FF6901C829C v8::internal::ScavengeJob::operator=+17740
9: 00007FF6901D0F87 v8::internal::Heap::MaxHeapGrowingFactor+2327
10: 00007FF6901D1006 v8::internal::Heap::MaxHeapGrowingFactor+2454
11: 00007FF68FD8CA3B v8::internal::Factory::AllocateRawWithImmortalMap+59
12: 00007FF68FD8F3AD v8::internal::Factory::NewRawOneByteString+77
13: 00007FF68FD8E519 v8::internal::Factory::NewStringFromOneByte+121
14: 00007FF68FD8E5FA v8::internal::Factory::NewStringFromUtf8+106
15: 00007FF68FCCD8FB v8::String::NewFromUtf8+363
16: 00007FF68FA184C1 node::Buffer::New+24225
17: 00007FF69022C122 v8::internal::OptimizingCompileDispatcher::Unblock+59890
18: 00007FF69022D5AD v8::internal::OptimizingCompileDispatcher::Unblock+65149
19: 00007FF69022C606 v8::internal::OptimizingCompileDispatcher::Unblock+61142
20: 00007FF69022C4EB v8::internal::OptimizingCompileDispatcher::Unblock+60859
21: 000002A1F2EDC5C1
npm ERR! code ELIFECYCLE
npm ERR! errno 134
npm ERR! @azure/storage-file-share@12.0.0 integration-test:browser: karma start --single-run
npm ERR! Exit status 134
npm ERR!
npm ERR! Failed at the @azure/storage-file-share@12.0.0 integration-test:browser script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\yumeng\AppData\Roaming\npm-cache_logs\2019-12-09T20_25_40_818Z-debug.log
The script failed with exit code 134