getspecstory

```markdown
**Title:** Fix Memory Leak in User Authentication Service

**Description:**
During a debugging session in VS Code, we identified a memory leak in the `/api/auth` endpoint that occurs when handling concurrent login requests. The issue was first noticed when the service crashed after 5,000 active users, with the following error in the logs:

```
Error: Heap out of memory
    at /app/src/auth/service.js:42:15
    at processTicksAndRejections (node:internal:339:5)
```

**Steps to Reproduce:**
1. Deploy the service with the latest `auth-service` image (v2.1.4).
2. Simulate 5,000 concurrent login requests using `autocannon -c 5000 -d 60 http://localhost:3000/api/auth`.
3. Monitor memory usage in Grafana. The service crashes within 2 minutes.

**Code Snippet:**
```javascript
// auth/service.js:42
const authService = async (req, res) => {
  const token = jwt.sign({ userId: req.user.id }, process.env.JWT_SECRET, {
    expiresIn: '1h',
  });
  // Memory leak occurs here due to unclosed streams
  const stream = fs.createReadStream('/tmp/cache');
  stream.pipe(res);
  // Missing stream.on('end', () => stream.close());
};
```

**Suggested Solutions:**
1. Close the stream after piping: `stream.on('end', () => stream.close());`
2. Implement a connection pool for file streams.
3. Add memory monitoring to alert on leaks.

**Tags:** #backend #memory-leak #critical
**Assignee:** @dev-team-lead
**Priority:** P1
```