You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: NEWS.rst
+27Lines changed: 27 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,6 +8,33 @@ Changelog
8
8
9
9
.. towncrier release notes start
10
10
11
+
memray 1.19.1 (2025-09-29)
12
+
--------------------------
13
+
14
+
- Fix a bug that caused Memray to refuse to produce stack traces for ``pymalloc`` allocations when ``--trace-python-allocators`` was used. (#832)
15
+
16
+
17
+
memray 1.19.0 (2025-09-26)
18
+
--------------------------
19
+
20
+
Features
21
+
~~~~~~~~
22
+
23
+
- Add a mode that can be used in Python 3.13.3 and newer where Memray will track Python object creation and destruction events, which can be used to find leaked objects (ones that were created during a tracking session and not destroyed before the end of that tracking session). (#752)
24
+
- Added ``--no-web`` flag to ``flamegraph`` and ``table`` commands for offline HTML report generation. When this flag is specified, memray bundles all external dependencies (Bootstrap, jQuery, D3, DataTables, Plotly.js) directly into the generated HTML files instead of loading them from CDNs. This enables memray to generate fully functional HTML reports on airgapped systems without internet connectivity. (#790)
25
+
- Reduced memory profiling overhead and capture file size by changing how
26
+
Python code locations are recorded. This makes allocation tracking
27
+
faster, produces smaller capture files, and improves the accuracy of
28
+
reports that group allocations by source location. (#801)
29
+
30
+
31
+
Bug Fixes
32
+
~~~~~~~~~
33
+
34
+
- Fix a crash that could occur if tracking was started in one thread while another thread was inside of a trace function installed with ``sys.settrace``. This crash wasn't possible to hit with ``memray run``, but could happen when using ``pytest-memray`` and ``pytest-cov`` together. (#823)
35
+
- Fix timestamps on the heap usage line chart when Memray is run on a 32-bit platform. (#826)
0 commit comments