Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

High memory consumption with typesafe-actions

See original GitHub issue

TypeScript Version: 3.5.1 (also with next)

Search Terms: typescript tsc out of memory high memory usage

Code

Please extract code from https://drive.google.com/open?id=1nO3g0yoedOG6syTLn2QGeCh4KXopKtoe. It is a simple code but contains many files not suitable to inline here. Project uses only single dependency: typesafe-actions. Could be related to https://github.com/piotrwitek/typesafe-actions/issues/158.

npm i
node --max-old-space-size=8192 ./node_modules/typescript/lib/tsc.js --diagnostics

Expected behavior:

Compilation should complete in couple of seconds.

Actual behavior:

Compilation fails with out of memory after couple of minutes. Tried with node 10 and node 12.

Issue Analytics

State:
Created 4 years ago
Reactions:3
Comments:8 (1 by maintainers)

Top GitHub Comments

1reaction

liaoyinglongcommented, Aug 15, 2019

@sven-strothoff

in my project typesafe-action 4.4.2 still have problem.

But I tried 5.0.0-3, it solve the memory problem for me

0reactions

sven-strothoffcommented, Aug 15, 2019

Actually the author of typesafe-actions has fixed something on his end. At least for me this solved the memory issues: https://github.com/piotrwitek/typesafe-actions/issues/164

Have you tried a recent version of typesafe-actions?

Top Results From Across the Web

piotrwitek/typesafe-actions: High memory consumption. #168

Description. Cmpiling application with couple of reducers ( 20) and action creators ( 200) takes 2 GB RAM and requires passing --max-old-space-size to...

Best practices for JVM memory issues - IBM

Memory patterns that show that a single instance or object type is consuming large amounts of high memory may warrant further investigation. However,...

Memory Consumption Related to Transactional Problems

High memory consumption can be caused by problems with transactions. In some cases, high memory consumption is caused by wait situations, which can...

Classloader-Releated Memory Issues - Dynatrace

A class is an object and consumes memory. Depending on the number of fields and class constants, the needed memory varies. Too many...

Overview of memory management - Android Developers

So, paired allocations and deallocations of large chunks should result in reclaiming all (or nearly all) the physical memory used. However, ...