-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Playgrounds
-
None
-
3
-
Not Needed
-
Iteration Lobster, Iteration Quahog
When the worker encounters an error like the javascript runtime running out of memory, we currently fail silently and future runs of the playground also fail. In the language server logs it prints `extensionPath is not defined`. We should instead surface the error that occurred and make sure future playgrounds can still be run.
Here's an example playground to reproduce:
use('test'); const docs = []; const amountOfDocsToCreate = 10000000; const currentTime = new Date(); for(let i = 0; i < amountOfDocsToCreate; i++) { docs.push({ a: currentTime, b: Math.ceil(Math.random() * 100) }); } db.test10m.insertMany(docs);