fix(core): default stack trace size adds unnecessary overhead

[rix0rrr]

By default, the CDK library captures the largest possible stack trace whenever stack traces are captured. Capturing the default stack trace size (10 frames) configured using --stack-trace-limit saves ~50% of the time spent in stack trace collection.

This saves ~200ms on ~8500 constructs in one sample application, while leaving the user in control.

---

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license

[github-actions]

⚠️ This pull request description does not follow the correct template structure.

PRs without a linked issue will receive lower priority for review and merging. Please update the description to follow the PR template and include a line like Closes #123 in the Issue section. If no existing issue matches your change, create one first.

[mrgrain]

I think this is good, but one question for clarification:

Q: This only happens when --debug is enabled, correct?

[rix0rrr]

Q: This only happens when --debug is enabled, correct?

Not entirely. Construct creation is always traced, even without --debug. Property mutations are only traced when --debug is set.

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[mergify]

Merge Queue Status

• ✅ Entered queue — 2026-05-13 11:53 UTC · Rule: default-squash
• ✅ Checks passed · in-place
• ✅ Merged — 2026-05-13 12:40 UTC · at 3c3e8864b1928773ae6bc40c4d091456c58e336e · squash

This pull request spent 47 minutes 28 seconds in the queue, including 47 minutes 2 seconds running CI.

Required conditions to merge

• #approved-reviews-by >= 1 [🛡 GitHub branch protection]
  • fix(core): default stack trace size adds unnecessary overhead #37827
• #changes-requested-reviews-by = 0 [🛡 GitHub branch protection]
  • fix(core): default stack trace size adds unnecessary overhead #37827
• any of [🛡 GitHub branch protection]:
  • check-success = validate-pr
  • check-neutral = validate-pr
  • check-skipped = validate-pr
• any of [🛡 GitHub branch protection]:
  • check-success = build
  • check-neutral = build
  • check-skipped = build

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[github-actions]

Comments on closed issues and PRs are hard for our team to see.
If you need help, please open a new issue that references this one.