Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Fixed code snippet to actually create a large strings in the heap snapshot article #2889

Merged
merged 1 commit into from
Oct 24, 2023
Merged

Fixed code snippet to actually create a large strings in the heap snapshot article #2889

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions microsoft-edge/devtools-guide-chromium/memory-problems/heap-snapshots.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -189,8 +189,8 @@ Name the functions, so that you can easily distinguish between closures in the s

```javascript
function createLargeClosure() {
var largeStr = new Array(1000000).join('x');
var lC = function() { // this is NOT a named function
var largeStr = 'x'.repeat(1000000).toLowerCase();
var lC = function() { // This is not a named function
return largeStr;
};
return lC;
Expand All @@ -201,8 +201,8 @@ The following code uses named functions, to easily distinguish between closures

```javascript
function createLargeClosure() {
var largeStr = new Array(1000000).join('x');
var lC = function lC() { // this IS a named function
var largeStr = 'x'.repeat(1000000).toLowerCase();
var lC = function lC() { // This is a named function
return largeStr;
};
return lC;
Expand Down
Loading