Document

检测内存变化

\n \n \n\n\n\n```\n\n页面上有一个按钮用来开始函数调用，方便我们控制。点击按钮，每个200毫秒执行一次bind函数，即在全局监听click事件，循环次数为50次。\n\n在无法确定是否发生内存泄漏时，我们可以先使用Performance来录制一段页面加载的性能变化，先判断是否有内存泄漏发生。\n\n### Performance\n\n本次案例仅以Chrome浏览器展开描述，其他浏览器可能会有些许差异。首先我们鼠标右键选择检查或者直接F12进入DevTools页面，面板上选择`Performance`，选择后应该是如下页面：\n\n在开始之前，我们先点击一下`Collect garbage`和`clear`来保证内存干净，没有其他遗留内存的干扰。然后我们点击`Record`来开始录制，并且同时我们也要点击页面上的`开始`按钮，让我们的代码跑起来。等到代码结束后，我们再点击`Record`按钮以停止录制，录制的时间跟代码执行的时间相比会有出入，只要保证代码是完全执行完毕的即可。停止录制后，我们会得到如下的结果：\n\n`Performance`的内容很多，我们只需要关注内存的变化，由此图可见，内存这块区域的曲线是在一直升高的并且到达顶点后并没有回落，这就有可能发生了内存泄漏。因为正常的内存变化曲线应该是类似于“锯齿”，也就是有上有下，正常增长后会有一定的回落，但不一定回落到和初始值一样。而且我们还可以隐约看到程序运行结束后，内存从初始的6.2MB增加到了差不多351MB，这个数量级的增加还是挺明显的。我们只是执行了50次循环，如果执行的次数更多，将会耗尽浏览器的内存空间，导致页面卡死。\n\n虽然是有内存泄漏，但是如果我们想进一步看内存泄漏发生的地方，那么`Performance`就不够用了，这个时候我们就需要使用`Memory`面板。\n\n### Memory\n\nDevTools的Memory选项主要是用来录制堆内存的快照，为的是进一步分析内存泄漏的详细信息。有人可能会说，为啥不一开始就直接使用`Memory`呢，反而是先使用`Performance`。因为我们刚开始就说了，内存增长不表示就一定出现了内存泄漏，有可能是正常的增长，直接使用Memory来分析可能得不到正确的结果。\n\n我们先来看一下怎么使用`Memory`：\n\n首先选择`Memory`选项，然后清除缓存，在配置选项中选择堆内存快照。内存快照每次点击录制按钮都会记录当前的内存使用情况，我们可以在程序开始前点击一下记录初始的内存使用，代码结束后再点一下记录最终的内存使用，中间可以点击也可以不点击。最后在快照列表中至少可以得到两个内存记录：\n\n初始内存我们暂时不深究，我们选择列表的最后一条记录，然后在筛选下拉框选择最后一个，即第一个快照和第二个快照的差异。\n\n\n这里我们重点说一下`Shallow Size`和`Retained Size`的区别：\n\n* Shallow Size：对象自身占用的内存大小，一般来说字符串、数组的Shallow Size都会比较大\n* Retained Size：这个是对象自身占用的内存加上无法被GC释放的内存的大小，如果Retained Size和Shallow Size相差不大，基本上可以判定没有发生内存泄漏，但是**如果相差很大**，例如上图的`Object`，这就表明发生了内存泄漏。\n\n我们再来细看一下`Object`，任意展开一个对象，可以在树结构中发现每一个对象都有一个全局事件绑定，并且占用了较大的内存空间。解决本案例涉及的内存泄漏也比较简单，就是及时释放绑定的全局事件。\n\n关于`Performance`和`Memory`的详细使用可以参考：[手把手教你排查Javascript内存泄漏](https://link.juejin.cn?target=https%3A%2F%2Fzhuanlan.zhihu.com%2Fp%2F322356761 \"https://zhuanlan.zhihu.com/p/322356761\")\n",{"_58":901,"_181":152,"_182":152,"_183":152,"_184":152,"_185":152,"_186":152,"_187":152,"_188":152,"_189":152},"https://api.github.com/repos/pro-collection/interview-question/issues/155/reactions","https://api.github.com/repos/pro-collection/interview-question/issues/155/timeline",{"_58":904,"_60":61,"_62":905,"_64":906,"_66":907,"_68":908,"_70":909,"_72":910,"_74":911,"_76":912,"_78":913,"_111":914,"_131":132,"_133":24,"_134":-5,"_135":917,"_137":918,"_159":152,"_153":920,"_155":921,"_158":-5,"_162":163,"_106":-5,"_164":-5,"_165":922,"_170":923,"_176":924,"_178":925,"_190":927,"_192":-5,"_193":-5,"_194":195},"https://api.github.com/repos/pro-collection/interview-question/issues/154","https://api.github.com/repos/pro-collection/interview-question/issues/154/labels{/name}","https://api.github.com/repos/pro-collection/interview-question/issues/154/comments","https://api.github.com/repos/pro-collection/interview-question/issues/154/events","https://github.com/pro-collection/interview-question/issues/154",1640787490,"I_kwDOJGDC6c5hzG4i",154,"常见的前端内存泄露场景有哪些？",{"_80":81,"_70":82,"_72":83,"_84":85,"_86":28,"_58":87,"_68":88,"_89":90,"_91":92,"_93":94,"_95":96,"_97":98,"_99":100,"_101":102,"_66":103,"_104":105,"_106":107,"_108":109,"_110":24},[915,916],{"_70":114,"_72":115,"_58":116,"_117":118,"_119":120,"_121":24,"_122":123},{"_70":886,"_72":887,"_58":888,"_117":889,"_119":890,"_121":24,"_122":891},[],{"_58":258,"_68":259,"_62":260,"_70":261,"_72":262,"_74":263,"_76":264,"_122":265,"_147":919,"_149":267,"_151":152,"_131":132,"_153":268,"_155":269,"_157":-5,"_158":-5},{"_80":81,"_70":82,"_72":83,"_84":85,"_86":28,"_58":87,"_68":88,"_89":90,"_91":92,"_93":94,"_95":96,"_97":98,"_99":100,"_101":102,"_66":103,"_104":105,"_106":107,"_108":109,"_110":24},"2023-03-26T06:15:29Z","2023-03-26T06:15:30Z",{"_167":152,"_168":152,"_169":152},{"_172":152,"_173":152,"_174":152,"_175":152},"大多数情况下，垃圾回收器会帮我们及时释放内存，一般不会发生内存泄漏。但是有些场景是内存泄漏的高发区，我们在使用的时候一定要注意：\n\n* 我们在开发的时候经常会使用`console`在控制台打印信息，但这也会带来一个问题：被`console`使用的对象是不能被垃圾回收的，这就可能会导致内存泄漏。因此在生产环境中不建议使用`console.log()`的理由就又可以加上一条避免内存泄漏了。\n\n* 被全局变量、全局函数引用的对象，在Vue组件销毁时未清除，可能会导致内存泄漏\n\n ```js\n // Vue3\n \n \n ```\n\n* 定时器未及时在Vue组件销毁时清除，可能会导致内存泄漏\n\n ```js\n // Vue3\n \n \n ```\n\n `setTimeout`和`setInterval`两个定时器在使用时都应该注意是否需要清理定时器，特别是`setInterval`，一定要注意清除。\n\n* 绑定的事件未及时在Vue组件销毁时清除，可能会导致内存泄漏\n\n 绑定事件在实际开发中经常遇到，我们一般使用`addEventListener`来创建。\n\n ```js\n // Vue3\n \n \n ```\n\n* 被自定义事件引用，在Vue组件销毁时未清除，可能会导致内存泄漏\n\n 自定义事件通过`emit/on`来发起和监听，清除自定义事件和绑定事件差不多，不同的是需要调用`off`方法\n\n ```js\n // Vue3\n \n \n ```\n\n除了及时清除监听器、事件等，对于全局变量的引用，我们可以选择`WeakMap`、`WeakSet`等弱引用数据类型。这样的话，即使我们引用的对象数据要被垃圾回收，弱引用的全局变量并不会阻止GC。\n",{"_58":926,"_181":152,"_182":152,"_183":152,"_184":152,"_185":152,"_186":152,"_187":152,"_188":152,"_189":152},"https://api.github.com/repos/pro-collection/interview-question/issues/154/reactions","https://api.github.com/repos/pro-collection/interview-question/issues/154/timeline",{"_58":929,"_60":61,"_62":930,"_64":931,"_66":932,"_68":933,"_70":934,"_72":935,"_74":936,"_76":937,"_78":938,"_111":939,"_131":132,"_133":24,"_134":-5,"_135":941,"_137":942,"_159":195,"_153":944,"_155":945,"_158":-5,"_162":163,"_106":-5,"_164":-5,"_165":946,"_170":947,"_176":948,"_178":949,"_190":951,"_192":-5,"_193":-5,"_194":195},"https://api.github.com/repos/pro-collection/interview-question/issues/142","https://api.github.com/repos/pro-collection/interview-question/issues/142/labels{/name}","https://api.github.com/repos/pro-collection/interview-question/issues/142/comments","https://api.github.com/repos/pro-collection/interview-question/issues/142/events","https://github.com/pro-collection/interview-question/issues/142",1637802180,"I_kwDOJGDC6c5hnuDE",142,"事件循环原理?",{"_80":81,"_70":82,"_72":83,"_84":85,"_86":28,"_58":87,"_68":88,"_89":90,"_91":92,"_93":94,"_95":96,"_97":98,"_99":100,"_101":102,"_66":103,"_104":105,"_106":107,"_108":109,"_110":24},[940],{"_70":114,"_72":115,"_58":116,"_117":118,"_119":120,"_121":24,"_122":123},[],{"_58":258,"_68":259,"_62":260,"_70":261,"_72":262,"_74":263,"_76":264,"_122":265,"_147":943,"_149":267,"_151":152,"_131":132,"_153":268,"_155":269,"_157":-5,"_158":-5},{"_80":81,"_70":82,"_72":83,"_84":85,"_86":28,"_58":87,"_68":88,"_89":90,"_91":92,"_93":94,"_95":96,"_97":98,"_99":100,"_101":102,"_66":103,"_104":105,"_106":107,"_108":109,"_110":24},"2023-03-23T15:48:30Z","2023-03-23T15:50:30Z",{"_167":152,"_168":152,"_169":152},{"_172":152,"_173":152,"_174":152,"_175":152},"通过一道题进入浏览器事件循环原理：\r\n\r\n```arcade\r\nconsole.log('script start')\r\nsetTimeout(function () {\r\n console.log('setTimeout')\r\n}, 0);\r\nPromise.resolve().then(function () {\r\n console.log('promise1')\r\n}).then(function () {\r\n console.log('promise2')\r\n})\r\nconsole.log('script end')\r\n```\r\n\r\n可以先试一下，手写出执行结果，然后看完这篇文章以后，在运行一下这段代码，看结果和预期是否一样\r\n\r\n### 单线程\r\n\r\n#### 定义\r\n\r\n单线程意味着所有的任务需要排队，前一个任务结束，才能够执行后一个任务。如果前一个任务耗时很长，后面一个任务不得不一直等着。\r\n\r\n#### 原因\r\n\r\n`javascript`的单线程，与它的用途有关。作为浏览器脚本语言，`javascript`的主要用途是与用户互动，以及操作`DOM`。这决定了它只能是单线程，否则会带来很复杂的同步问题。比如，假定`javascript`同时有两个线程，一个在添加`DOM`节点，另外一个是删除`DOM`节点，那浏览器应该应该以哪个为准，如果在增加一个线程进行管理多个线程，虽然解决了问题，但是增加了复杂度，为什么不使用单线程呢，执行有个先后顺序，某个时间只执行单个事件。 \r\n为了利用多核`CPU`的计算能力，`HTML5`提出`Web Worker`标准，运行`javascript`创建多个线程，但是子线程完全受主线程控制，且不得操作`DOM`。所以，这个标准并没有改变`javascript`单线程的本质\r\n\r\n### 浏览器中的`Event Loop`\r\n\r\n事件循环这个名字来源于它往往这么实现:\r\n\r\n```cpp\r\nwhile(queue.waitForMessage()) {\r\n queue.processNextMessage();\r\n}\r\n```\r\n\r\n这个模型的优势在于它必须处理完一个消息(run to completion),才会处理下一个消息,使程序可追溯性更强。不像C语言可能随时从一个线程切换到另一个线程。但是缺点也在于此,若同步代码阻塞则会影响用户交互\r\n\r\n#### `macroTask`和`microTask`\r\n\r\n宏队列，`macroTask`也叫`tasks`。包含同步任务，和一些异步任务的回调会依次进入`macro task queue`中，`macroTask`包含:\r\n\r\n* script代码块\r\n* setTimeout\r\n* requestAnimationFrame\r\n* I/O\r\n* UI rendering\r\n\r\n微队列, `microtask`，也叫`jobs`。另外一些异步任务的回调会依次进入`micro task queue`，等待后续被调用，这些异步任务包含:\r\n\r\n* Promise.then\r\n* MutationObserver\r\n\r\n下面是`Event Loop`的示意图\r\n\r\n![](https://p1-jj.byteimg.com/tos-cn-i-t2oaga2asx/gold-user-assets/2019/10/24/16dfca86d30dc6d0~tplv-t2oaga2asx-zoom-in-crop-mark:3024:0:0:0.awebp)\r\n一段`javascript`执行的具体流程就是如下：\r\n1. 首先执行宏队列中取出第一个，一段`script`就是相当于一个`macrotask`,所以他先会执行同步代码，当遇到例如`setTimeout`的时候，就会把这个异步任务推送到宏队列队尾中。\r\n2. 当前`macrotask`执行完成以后，就会从微队列中取出位于头部的异步任务进行执行，然后微队列中任务的长度减一。\r\n3. 然后继续从微队列中取出任务，直到整个队列中没有任务。如果在执行微队列任务的过程中，又产生了`microtask`，那么会加入整个队列的队尾，也会在当前的周期中执行\r\n4. 当微队列的任务为空了，那么就需要执行下一个`macrotask`，执行完成以后再执行微队列，以此反复。 \r\n 总结下来就是不断从`task`队列中按顺序取`task`执行，每执行完一个`task`都会检查`microtask`是否为空，不让过不为空就执行队列中的所有`microtask`。然后在取下一个`task`以此循环\r\n\r\n#### 调用栈和任务队列\r\n\r\n调用栈是一个栈结构，函数调用会形成一个栈帧。栈帧：调用栈中每个实体被称为栈帧，帧中包含了当前执行函数的参数和局部变量等上下文信息，函数执行完成后，它的执行上下文会从栈中弹出。下面是调用栈和任务队列的关系:\r\n\r\n![](https://p1-jj.byteimg.com/tos-cn-i-t2oaga2asx/gold-user-assets/2019/10/25/16e01c44735fee30~tplv-t2oaga2asx-zoom-in-crop-mark:3024:0:0:0.awebp)\r\n分析文章开头的题目，可以通过在题目前面添加`debugger`，结合`chrome`的`call stack`进行分析:\r\n\r\n![](https://p1-jj.byteimg.com/tos-cn-i-t2oaga2asx/gold-user-assets/2019/10/25/16e01cbeaa6b1c05~tplv-t2oaga2asx-zoom-in-crop-mark:3024:0:0:0.awebp)\r\n(这里不知道怎么画动图，在晚上找的一张图，小伙伴们有好的工具，求分享); 下面借助三个数组来分析一下这段代码的执行流程，`call stack`表示调用栈，`macroTasks`表示宏队列，`microTasks`表示微队列：\r\n1. 首先代码执行之前都是三个队列都是空的:\r\n\r\n```apache\r\ncallStack: []\r\nmacroTasks: [main]\r\nmicroTasks: []\r\n```\r\n\r\n在前面提到，整个代码块就相当于一个`macroTask`，所以首先向`callStack`中压入`main()`，`main`相当于整个代码块 \r\n2. 执行`main`，输出同步代码结果:\r\n\r\n```apache\r\ncallStack: [main]\r\nmacroTasks: []\r\nmicroTasks: []\r\n```\r\n\r\n在遇到`setTimeout`和`promise`的时候会向`macroTasks`与`microTasks`中分别推入 \r\n3. 此时的三个队列分别是:\r\n\r\n```apache\r\ncallStack: [main]\r\nmacroTasks: [setTimeout]\r\nmicroTasks: [promise]\r\n```\r\n\r\n当这段代码执行完成以后，会输出:\r\n\r\n```applescript\r\nscript start\r\nscript end\r\n```\r\n\r\n4. 当`main`执行完成以后，会取`microTasks`中的任务，放入`callStack`中，此时的三个队列为:\r\n\r\n```apache\r\ncallStack: [promise]\r\nmacroTasks: [setTimeout]\r\nmicroTask: []\r\n```\r\n\r\n当这个`promise`执行完成后会输出\r\n\r\n```\r\npromise1\r\n```\r\n\r\n后面又有一个`then`，在前面提到如果还有`microtask`就在微队列队尾中加入这个任务，并且在当前`tick`执行。所以紧接着输出`promise2` \r\n5. 当前的`tick`也就完成了，最后在从`macroTasks`取出`task`，此时三个队列的状态如下：\r\n\r\n```apache\r\ncallStack: [setTimeout]\r\nmacroTasks: []\r\nmicroTask: []\r\n```\r\n\r\n最后输出的结果就是`setTimeout`。 \r\n所谓的事件循环就是从两个队列中不断取出事件，然后执行，反复循环就是事件循环。经过上面的示例，理解起来是不是比较简单\r\n\r\n",{"_58":950,"_181":263,"_182":263,"_183":152,"_184":152,"_185":152,"_186":152,"_187":152,"_188":152,"_189":152},"https://api.github.com/repos/pro-collection/interview-question/issues/142/reactions","https://api.github.com/repos/pro-collection/interview-question/issues/142/timeline",{"_58":953,"_60":61,"_62":954,"_64":955,"_66":956,"_68":957,"_70":958,"_72":959,"_74":960,"_76":961,"_78":962,"_111":963,"_131":132,"_133":24,"_134":-5,"_135":965,"_137":966,"_159":152,"_153":968,"_155":969,"_158":-5,"_162":163,"_106":-5,"_164":-5,"_165":970,"_170":971,"_176":972,"_178":973,"_190":975,"_192":-5,"_193":-5,"_194":195},"https://api.github.com/repos/pro-collection/interview-question/issues/127","https://api.github.com/repos/pro-collection/interview-question/issues/127/labels{/name}","https://api.github.com/repos/pro-collection/interview-question/issues/127/comments","https://api.github.com/repos/pro-collection/interview-question/issues/127/events","https://github.com/pro-collection/interview-question/issues/127",1630945649,"I_kwDOJGDC6c5hNkFx",127,"如何实现可过期的 localstorage 数据?",{"_80":81,"_70":82,"_72":83,"_84":85,"_86":28,"_58":87,"_68":88,"_89":90,"_91":92,"_93":94,"_95":96,"_97":98,"_99":100,"_101":102,"_66":103,"_104":105,"_106":107,"_108":109,"_110":24},[964],{"_70":114,"_72":115,"_58":116,"_117":118,"_119":120,"_121":24,"_122":123},[],{"_58":258,"_68":259,"_62":260,"_70":261,"_72":262,"_74":263,"_76":264,"_122":265,"_147":967,"_149":267,"_151":152,"_131":132,"_153":268,"_155":269,"_157":-5,"_158":-5},{"_80":81,"_70":82,"_72":83,"_84":85,"_86":28,"_58":87,"_68":88,"_89":90,"_91":92,"_93":94,"_95":96,"_97":98,"_99":100,"_101":102,"_66":103,"_104":105,"_106":107,"_108":109,"_110":24},"2023-03-19T13:36:22Z","2024-10-26T08:28:47Z",{"_167":152,"_168":152,"_169":152},{"_172":152,"_173":152,"_174":152,"_175":152},"以下是一个封装了支持过期时间的`localStorage`的示例代码：\r\n\r\n```javascript\r\nclass EnhancedLocalStorage {\r\n constructor() {\r\n this.prefix = 'enhanced_storage_';\r\n }\r\n\r\n setItem(key, value, expirationInSeconds) {\r\n const item = {\r\n value,\r\n expirationTime: expirationInSeconds? Date.now() + expirationInSeconds * 1000 : null\r\n };\r\n localStorage.setItem(this.prefix + key, JSON.stringify(item));\r\n }\r\n\r\n getItem(key) {\r\n const itemStr = localStorage.getItem(this.prefix + key);\r\n if (!itemStr) return null;\r\n const item = JSON.parse(itemStr);\r\n if (item.expirationTime && item.expirationTime < Date.now()) {\r\n localStorage.removeItem(this.prefix + key);\r\n return null;\r\n }\r\n return item.value;\r\n }\r\n\r\n removeItem(key) {\r\n localStorage.removeItem(this.prefix + key);\r\n }\r\n}\r\n\r\nconst enhancedStorage = new EnhancedLocalStorage();\r\nexport default enhancedStorage;\r\n```\r\n\r\n使用方法如下：\r\n\r\n```javascript\r\n// 设置带有过期时间的存储项\r\nenhancedStorage.setItem('myKey', 'myValue', 60); // 60 秒后过期\r\n\r\n// 获取存储项\r\nconst value = enhancedStorage.getItem('myKey');\r\nconsole.log(value);\r\n\r\n// 一段时间后，存储项过期\r\nsetTimeout(() => {\r\n const expiredValue = enhancedStorage.getItem('myKey');\r\n console.log(expiredValue); // null\r\n}, 65000);\r\n```\r\n\r\n在这个封装中，使用了一个自定义的前缀来避免与普通的`localStorage`键冲突。设置项时，会记录一个过期时间，如果有过期时间且当前时间超过了过期时间，在获取项时会返回`null`并自动删除该项。",{"_58":974,"_181":152,"_182":152,"_183":152,"_184":152,"_185":152,"_186":152,"_187":152,"_188":152,"_189":152},"https://api.github.com/repos/pro-collection/interview-question/issues/127/reactions","https://api.github.com/repos/pro-collection/interview-question/issues/127/timeline",{"_58":977,"_60":61,"_62":978,"_64":979,"_66":980,"_68":981,"_70":982,"_72":983,"_74":984,"_76":985,"_78":986,"_111":987,"_131":132,"_133":24,"_134":-5,"_135":989,"_137":990,"_159":152,"_153":992,"_155":993,"_158":-5,"_162":163,"_106":-5,"_164":-5,"_165":994,"_170":995,"_176":996,"_178":997,"_190":999,"_192":-5,"_193":-5,"_194":195},"https://api.github.com/repos/pro-collection/interview-question/issues/126","https://api.github.com/repos/pro-collection/interview-question/issues/126/labels{/name}","https://api.github.com/repos/pro-collection/interview-question/issues/126/comments","https://api.github.com/repos/pro-collection/interview-question/issues/126/events","https://github.com/pro-collection/interview-question/issues/126",1630945151,"I_kwDOJGDC6c5hNj9_",126,"es5 和 es6 使用 new 关键字实例化对象的流程是一样的吗？",{"_80":81,"_70":82,"_72":83,"_84":85,"_86":28,"_58":87,"_68":88,"_89":90,"_91":92,"_93":94,"_95":96,"_97":98,"_99":100,"_101":102,"_66":103,"_104":105,"_106":107,"_108":109,"_110":24},[988],{"_70":114,"_72":115,"_58":116,"_117":118,"_119":120,"_121":24,"_122":123},[],{"_58":258,"_68":259,"_62":260,"_70":261,"_72":262,"_74":263,"_76":264,"_122":265,"_147":991,"_149":267,"_151":152,"_131":132,"_153":268,"_155":269,"_157":-5,"_158":-5},{"_80":81,"_70":82,"_72":83,"_84":85,"_86":28,"_58":87,"_68":88,"_89":90,"_91":92,"_93":94,"_95":96,"_97":98,"_99":100,"_101":102,"_66":103,"_104":105,"_106":107,"_108":109,"_110":24},"2023-03-19T13:34:48Z","2023-03-19T13:34:49Z",{"_167":152,"_168":152,"_169":152},{"_172":152,"_173":152,"_174":152,"_175":152},"ES5 和 ES6 使用 `new` 关键字实例化对象的流程基本上是一样的，只是在细节上存在一些差异。\n\n在 ES5 中，当使用 `new` 关键字调用一个函数时，会创建一个新的对象，并将这个新对象的 `[[Prototype]]` 属性指向构造函数的 `prototype` 属性。此外，`new` 关键字还会将构造函数内部的 `this` 关键字绑定到新创建的对象上，从而允许我们在构造函数内部添加属性和方法。\n\n在 ES6 中，这些基本的流程也是相同的。但是，ES6 引入了类（class）的概念，从而为面向对象编程提供了更加便利的语法。使用类定义一个对象时，需要使用 `constructor` 方法作为构造函数，而不是普通的函数。类定义的语法糖实际上是对函数的封装，使用 `new` 关键字创建类的实例时，实际上也是在调用类的 `constructor` 方法。\n\n在 ES6 中，可以使用类的继承来创建更复杂的对象。当使用 `new` 关键字创建一个继承自另一个类的类的实例时，会先调用父类的 `constructor` 方法，再调用子类的 `constructor` 方法，从而完成对象实例的创建过程。\n\n需要注意的是，虽然 ES6 的类看起来像是其他面向对象语言中的类，但在 JavaScript 中，类仍然是基于原型继承的。在创建一个类的实例时，实际上是在创建一个新对象，并将这个新对象的原型指向类的原型。因此，实例化对象的流程与使用普通函数或类定义的对象的流程基本上是相同的。",{"_58":998,"_181":152,"_182":152,"_183":152,"_184":152,"_185":152,"_186":152,"_187":152,"_188":152,"_189":152},"https://api.github.com/repos/pro-collection/interview-question/issues/126/reactions","https://api.github.com/repos/pro-collection/interview-question/issues/126/timeline",{"_58":1001,"_60":61,"_62":1002,"_64":1003,"_66":1004,"_68":1005,"_70":1006,"_72":1007,"_74":1008,"_76":1009,"_78":1010,"_111":1011,"_131":132,"_133":24,"_134":-5,"_135":1013,"_137":1014,"_159":152,"_153":1016,"_155":1016,"_158":-5,"_162":163,"_106":-5,"_164":-5,"_165":1017,"_170":1018,"_176":1019,"_178":1020,"_190":1022,"_192":-5,"_193":-5,"_194":195},"https://api.github.com/repos/pro-collection/interview-question/issues/125","https://api.github.com/repos/pro-collection/interview-question/issues/125/labels{/name}","https://api.github.com/repos/pro-collection/interview-question/issues/125/comments","https://api.github.com/repos/pro-collection/interview-question/issues/125/events","https://github.com/pro-collection/interview-question/issues/125",1630942806,"I_kwDOJGDC6c5hNjZW",125,"当使用 new 关键字创建对象时, 会经历哪些步骤？",{"_80":81,"_70":82,"_72":83,"_84":85,"_86":28,"_58":87,"_68":88,"_89":90,"_91":92,"_93":94,"_95":96,"_97":98,"_99":100,"_101":102,"_66":103,"_104":105,"_106":107,"_108":109,"_110":24},[1012],{"_70":114,"_72":115,"_58":116,"_117":118,"_119":120,"_121":24,"_122":123},[],{"_58":258,"_68":259,"_62":260,"_70":261,"_72":262,"_74":263,"_76":264,"_122":265,"_147":1015,"_149":267,"_151":152,"_131":132,"_153":268,"_155":269,"_157":-5,"_158":-5},{"_80":81,"_70":82,"_72":83,"_84":85,"_86":28,"_58":87,"_68":88,"_89":90,"_91":92,"_93":94,"_95":96,"_97":98,"_99":100,"_101":102,"_66":103,"_104":105,"_106":107,"_108":109,"_110":24},"2023-03-19T13:30:24Z",{"_167":152,"_168":152,"_169":152},{"_172":152,"_173":152,"_174":152,"_175":152},"在 JavaScript 中，`new` 关键字用于创建一个对象实例。当使用 `new` 关键字创建对象时，会发生以下几个步骤：\n\n1. 创建一个空的对象。\n2. 将这个空对象的 `[[Prototype]]` 属性设置为构造函数的 `prototype` 属性。\n3. 将这个空对象赋值给构造函数内部的 `this` 关键字，用于初始化属性和方法。\n4. 如果构造函数返回一个对象，那么返回这个对象；否则，返回第一步创建的对象实例。\n\n以下是一个示例，演示如何使用 `new` 关键字创建一个对象实例：\n\n```javascript\nfunction Person(name, age) {\n this.name = name;\n this.age = age;\n}\n\nconst person = new Person(\"John\", 30);\nconsole.log(person.name); // \"John\"\nconsole.log(person.age); // 30\n```\n\n在上面的示例中，`new Person(\"John\", 30)` 会创建一个新的对象实例。在构造函数 `Person` 中，`this.name` 和 `this.age` 会被赋值为 `\"John\"` 和 `30`。最终，`new` 关键字会返回这个新的对象实例。\n\n需要注意的是，在 JavaScript 中，函数也是对象。因此，我们可以向对象一样定义属性和方法。当我们使用 `new` 关键字调用一个函数时，这个函数会被视为构造函数，从而创建一个新的对象实例。",{"_58":1021,"_181":152,"_182":152,"_183":152,"_184":152,"_185":152,"_186":152,"_187":152,"_188":152,"_189":152},"https://api.github.com/repos/pro-collection/interview-question/issues/125/reactions","https://api.github.com/repos/pro-collection/interview-question/issues/125/timeline","pagination",{"_1025":1026,"_167":1027},"value",5,7,"actionData","errors"]