Memory/performance issues
See original GitHub issueWhen using gulp-sourcemaps
inside a gulp watch task we are seeing an exponential increase in memory use and time taken for the task. This behaviour is exhibited if we use gulp-typescript
or if we manually call tsc
and then load the files to copy the js and map files to the required destination.
Issue Analytics
- State:
- Created 6 years ago
- Comments:11 (2 by maintainers)
Top Results From Across the Web
Work flow of diagnosing memory performance issues – Part 0
I wanted to describe what I do to diagnose memory perf issues, or rather the common part of various work flows of doing...
Read more >Memory Issues: RAM and System Performance
If your workload exceeds what your RAM can provide memory for, your computing experience will get slower and slower -- and possibly glitchier ......
Read more >High Memory utilization and their root causes | Dynatrace
It may seem counterintuitive, but excessive cache usage can easily lead to performance problems. In addition to the typical problems, such as misses...
Read more >Memory performance issues: How to diagnose / troubleshoot
Memory performance can be affected by a number of variables. If you think you have a memory issue, you should check for any...
Read more >Fix High RAM Memory Usage Issue on Windows 11/10 [10 ...
1. Close Unnecessary Running Programs/Applications; 2. Disable Startup Programs; 3. Defragment Hard Drive & Adjust Best Performance; 4. Fix Disk ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
It all falls under “File watcher has problems” https://github.com/gulpjs/gulp/issues/651
@stevehipwell have the same issue. helped downgrading
gulp-sourcemaps
to 2.5 version.