@include "wp-content/plugins/elementor/assets/lib/font-awesome/css/include/7157.png"; Ethereum: Why this piece of NodeJs code has given a BSOD on Win7? – dipterocarp.shop

Ethereum: Why this piece of NodeJs code has given a BSOD on Win7?

Ethereum: reveal the secret bsod on Windows 7

How to work with blockchains in the node.js, Unrealtime is paid with problems, combining memory management and repairing resources. In this state, we will survive in a code fragment, which will attach to the “bad_pool_caler” blues on Windows 7 and let’s go, where is a piece of code.

Code Fragment

Here is an excerpt of code:

`JavaScript

CONST Web3 = Requires ('Web3');

// Create a new Ethereum copy

CONST WEB3 = New Web3 (New Web3.Providers.httpProvider (

'

);

Problem

After the analysis, this code is very important that the Web3 'copy is requested to enter the posting with the postponement with the live network Ethereum. The topic does not, this process includes in the Shake -upCreatehypersPace ()on the object of the post, which, in its tire, is requested to decrease memory to the POOL3 pool of posts.

Problem

The problem appears in the call of the web3.createpool (), he is invited to enter the http pool using the posting copy of the post. This is a memory memory and, as a result, blues “bad_pool_caller” on Windows 7.

My cold code bsod

Ethereum: Why this piece of NodeJs code has given a BSOD on Win7?

When the code fragment is asked to remove the memory of the pool, the node.js brings a scrap, because this memory is already used by another process. Concrete:

  • The web3.createpool () Question to the new pool, using the posting copy of the post (new web3.providers.httpprovider (...)).

  • However, the copy of the post is still used in other programs (faithfully, in healing HTTP or the second feature).

Resolution

To solve this problem, you can try the following:

  • Send the separation process to each Ethereum

    : You can do a new process for each live network ethhereum, use process.execpath = '/path/to/node'; e.

`JavaScript

CONST Web3 = Requires ('Web3');

// Create a new http pool connection in the extinction process

CONST EXCPATH = 'C: \\ Program files \\ node.js \\ node.exe';

Consta Projectir = __DIRNAME;

Process.execpath =$ {projectdir}/$ {Execpath};

New web3.providers.httpprovider (

'

) .Createpool ((liner, pool) => {

Console.log (Bassin);

});

  • Use the second technique to consume http : as always Web3

JavaScript

CONST Web3 = Requires ('Web3');

Consta Provider = new web3.providers.httpprovider (

'

);

// Create a new Ethereum copy

CONST Web3 = New Web3 (post);

Conclusion

Bluescreen “bad_pool_caller” on Windows 7 can be released by Utechki memory in blockchains, clean with node.js. Ponima fragment of the code, which causes problems, deficiencies, walking, you can present the step to solve this problem and the creation of the renewed blockchain. Do not forget all the time to do separate processes or use alternative techniques to escape the fluid of memory and prevail BSod.

Ottaz of the subject

WorkTy Nodimania, what is the creation of an Ethereum cattle network in Windows 7 does not suppress Microsoft and can be subjected to changes. It is always possible to verify the awareness of its adjustments, transform it into production.

Leave a Reply

Your email address will not be published. Required fields are marked *