You're reading from Tools and Skills for .NET 8 Get the career you want with good practices and patterns to design, debug, and test your solutions 

Product type Paperback

Published in Jul 2024

Publisher Packt

ISBN-13 9781837635207

Length 778 pages

Edition 1st Edition

Languages

Tools

.NET

Concepts

Cloud Native

Author (1):

Mark J. Price

View More author details

Table of Contents (22) Chapters

Preface

1. Introducing Tools and Skills for .NET

2. Making the Most of the Tools in Your Code Editor FREE CHAPTER

3. Source Code Management Using Git

4. Debugging and Memory Troubleshooting

5. Logging, Tracing, and Metrics for Observability

6. Documenting Your Code, APIs, and Services

7. Observing and Modifying Code Execution Dynamically

8. Protecting Data and Apps Using Cryptography

9. Building an LLM-Based Chat Service

10. Dependency Injection, Containers, and Service Lifetime

11. Unit Testing and Mocking

12. Integration and Security Testing

13. Benchmarking Performance, Load, and Stress Testing

14. Functional and End-to-End Testing of Websites and Services

15. Containerization Using Docker

16. Cloud-Native Development Using .NET Aspire

17. Design Patterns and Principles

18. Software and Solution Architecture Foundations

19. Your Career, Teamwork, and Interviews

20. Epilogue

21. Index

Understanding stack and heap memory

One of the most common issues with programming is managing memory. To troubleshoot memory issues, you need to start with a deep understanding of how memory is used in .NET projects.

There are two categories of memory: stack memory and heap memory. Stack memory is faster to work with but limited in size. It is fast because it is managed directly by the CPU and it uses a last-in, first-out mechanism, so it is more likely to have data in its L1 or L2 cache. Heap memory is slower but much more plentiful.

On Windows, for ARM64, x86, and x64 machines, the default stack size is 1 MB. It is 8 MB on a typical modern Linux-based operating system. For example, in a macOS or Linux Terminal, I can enter the command ulimit -a to discover that the stack size is limited to 8,192 KB and that other memory is “unlimited.” This limited amount of stack memory is why it is so easy to fill it up and get a “stack overflow.”

Which...