Chapter 10. Debugging and Troubleshooting
We are finally at the last chapter. We started with an empty directory and built a full application. We will not be adding anything else to the application. We will investigate how to debug and find memory leaks in our code. Here is what we will cover in this chapter:
- Inspecting requests
- How to set debug breakpoints in our codebase
- CPU profiling
- Heap snapshots to help track down memory leaks
Node packages
This will be a completely separate, new application. We will need to create a new root directory. We are going to purposefully create issues so that we can investigate them. We are going to introduce two Node packages, node-inspector and webkit-devtools-agent. Add these two packages to our new package.json ...
Get Building Scalable Apps with Redis and Node.js now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
