我如何解决;JavaScript内存不足;?
当我运行“纱线测试测试/screens/Home/Home.js”时, 我遇到了“javascript内存泄漏”错误。 然后创建这个文件。 文件名为“report.20191007.162344.626.0.001.json” 我能做什么我如何解决;JavaScript内存不足;?,javascript,typescript,react-native,memory-leaks,jestjs,Javascript,Typescript,React Native,Memory Leaks,Jestjs,当我运行“纱线测试测试/screens/Home/Home.js”时, 我遇到了“javascript内存泄漏”错误。 然后创建这个文件。 文件名为“report.20191007.162344.626.0.001.json” 我能做什么 { "header": { "event": "Allocation failed - JavaScript heap out of memory", "trigger": "FatalError", "filename": "r
{
"header": {
"event": "Allocation failed - JavaScript heap out of memory",
"trigger": "FatalError",
"filename": "report.20191007.162344.626.0.001.json",
"dumpEventTime": "2019-10-07T16:23:44Z",
"dumpEventTimeStamp": "1570433024575",
"processId": 626,
"commandLine": [
"/usr/local/bin/node",
"/my app path~/node_modules/.bin/jest",
"__tests__/screens/Home/Home.test.js"
],
"nodejsVersion": "v12.5.0",
"wordSize": 64,
"arch": "x64",
"platform": "darwin",
"componentVersions": {
"node": "12.5.0",
"v8": "7.5.288.22-node.14",
"uv": "1.29.1",
"zlib": "1.2.11",
"brotli": "1.0.7",
"ares": "1.15.0",
"modules": "72",
"nghttp2": "1.38.0",
"napi": "4",
"llhttp": "1.1.4",
"http_parser": "2.8.0",
"openssl": "1.1.1c",
"cldr": "35.1",
"icu": "64.2",
"tz": "2019a",
"unicode": "12.1"
},
}
Home.test.js
import React from 'react';
import renderer from 'react-test-renderer';
import Home from '../../../src/screens/Home/Home';
import configureStore from '../../../src/store/configureStore'
const store = configureStore();
test('renders correctly', () => {
const tree = renderer.create(<Home store={store} />).toJSON();
expect(tree).toMatchSnapshot();
});
从“React”导入React;
从“反应测试渲染器”导入渲染器;
从“../../src/screens/Home/Home”导入主页;
从“../../src/store/configureStore”导入configureStore
const store=configureStore();
测试('正确呈现',()=>{
const tree=renderer.create().toJSON();
expect(tree.toMatchSnapshot();
});
此代码是已创建文件的一部分。Home.test.js
中似乎存在内存问题。也许它分配了太多的内存,或者可能有一个无限循环somewhere@apokryfos使用相同的代码在另一个文件上运行测试效果很好。java内存泄漏与javascript有什么关系?您已经展示了测试任何内容的代码,但是您还没有展示正在测试的代码——问题可能在于正在测试的代码,而不是测试代码本身