0.11.0

Release Notes for 0.11.0

The real stack trace on memory_limit violations

• The memory profiling mode now can capture the real stack trace on memory_limit violations
• See the documentation and #384 for more detail

Improved the documentation for the memory profiling mode

• The document of the memory profiler now includes useful snippets for analyzing the output, examples of diagnosing memory issues in the wild, and more.

Command line options for the memory profiler is changed

before	after
--stop-process=1 or --stop-process=0	--stop-process or --no-stop-process
--pretty-print=1 or --pretty-print=0	--pretty-print or --no-pretty-print

0.11.0

• Total issues resolved: 0
• Total pull requests resolved: 5
• Total contributors: 1

bug

• 390: Fix the bug that filename or lineno of internal function call are set incorrectly thanks to @sj-i
• 389: Fix the bug that memory_limit violations in class methods or closures are not working thanks to @sj-i

documentation

• 388: Fix README.md thanks to @sj-i
• 387: Improve the document a bit thanks to @sj-i

enhancement

• 384: Add an ability to get the real stack trace on memory_limit violations thanks to @sj-i