- Fixed a reentrancy bug that could cause profiling to fail with a BorrowMutError. (#485)
- Out-of-memory detection is disabled for now on macOS, since it is prone to false positives.
- Fix regression where source code would sometimes be missing from flamegraphs, most notably in Jupyter profiling. (#474)
- Added initial Python 3.11 support; unfortunately this increased performance overhead a little. (#381)
- If
/procis in unexpected format, try to keep running anyway. This can happen, for example, on very old versions of Linux. (#433)
- Complex flamegraphs should render faster. (#427)
- Hopefully fixed segfault on macOS, on Python 3.7 and perhaps other versions. (#412)
- Added wheels for ARM on Linux (
aarch64), useful for running native Docker images on ARM Macs. (#395)
- Stopped using
jemallocon Linux, for better compatibility with certain libraries. (#389) - Speed up rendering of flamegraphs in cases where there are many smaller allocations, by filtering out allocations smaller than 0.2% of total memory. Future releases may re-enable showing smaller allocations if a better fix can be found. (#390)
- Added wheels for macOS ARM/Silicon machines. (#383)
- Fix a number of potential deadlock scenarios when writing out reports. (#374, #365, #349)
- Give more accurate message when running in no-browser mode (thanks to Paul-Louis NECH). (#347)
- Don't include memory usage from NumPy imports in the profiling output. This is somewhat inaccurate, but is a reasonable short-term workaround. (#308)
- Added explanation of why error messages are printed on macOS when opening browser. (#334)
- The directories where reports are stored now avoid the characters ':' and '.', for better compatibility with other operating systems. (#336)
- Python 3.6 support was dropped. (#342)
- The jemalloc package used on Linux was unmaintained and old, and broke Conda-Forge builds; switched to a newer one. (#302)
- Reports now have a "open in new tab" button. Thanks to @petergaultney for the suggestion. (#298)
- Improved explanations in report of what it is that Fil tracks, and what a flamegraph tells you. (#185)
- Fix bad command name in the API documentation, thanks to @kdebrab. (#291)
- Work on versions of Linux with weird glibc versions. (#277)
- Build 3.10 wheels for macOS too. (#268)
- Added Python 3.10 support. (#242)
- Added back wheels for macOS Catalina (10.15). (#253)
- Fixed crashes on macOS Monterey. (#248)
- SIGUSR2 previously did not actually dump memory. Thanks to @gaspard-quenard for the bug report. (#237)
- Fix problem on macOS where certain subprocesses (e.g. from Homebrew) would fail to start from Python processes running under Fil. Thanks to @dreid for the bug report. (#230)
- Fix Apache Beam (and other libraries that depend on pickling
__main__module) when usingfilprofile run -m. (#202) - Fixed potential reentrancy bugs; unclear if this had any user-facing impacts, though. (#215)
- Fixed segfault on some Linux versions (regression in release 2021.7.0). (#208)
- Added a
--disable-oom-detectionto disable the out-of-memory detection heuristic. (#201)
- When using the Jupyter
%%filprofilemagic, locals defined in the cell are now stored in the Jupyter session as usual. (#167) - Emulate Python's module running code more faithfully, to enable profiling things like Apache Beam. (#202)
- Fixed bug where certain allocations went missing during thread creation and cleanup. (#179)
- Fixed race condition in threads that resulting in wrong allocation being removed in the tracking code. (#175)
- Major bugfix: mmap() was usually not added correctly on Linux, and when it was, munmap() was ignored. (#161)
- Added --no-browser option to disable automatically opening reports in a browser. (#59)
- Fixed bug where aligned_alloc()-created allocations were untracked when using pip packages with Conda; specifically this is relevant to libraries written in C++. (#152)
- Improved output in the rare case where allocations go missing. (#154)
- Fixed potential problem with threads noticing profiling is enabled. (#156)
- Fixed bug where reverse SVG sometimes was generated empty, e.g. if source code used tabs. (#150)
- Fil no longer blows up if checking cgroup memory is not possible, e.g. on CentOS 7. (#147)
- Try to ensure monospace font is used for reports. (#143)
- Number of allocations in the profiling results are now limited to 10,000. If there are more than this, they are all quite tiny, so probably less informative, and including massive number of tiny allocations makes report generation (and report display) extremely resource intensive. (#140)
- The out-of-memory detector should work more reliably on Linux. (#144)
- Improve error messages when using API in subprocesses, so it's clear it's not (yet) possible. (#133)
- On Linux, use a more robust method of preloading the shared library (requires glibc 2.30+, i.e. a Linux distribution released in 2020 or later). (#133)
- Fixed in regression in Fil v0.15 that made it unusable on macOS. (#135)
- Fewer spurious warnings about launching subprocesses. (#136)
- Fil now supports profiling individual functions in normal Python scripts; previously this was only possible in Jupyter. (#71)
- Fil now works better with subprocessses. It doesn't support memory tracking in subprocesses yet, but it doesn't break them either. (#117)
- Report memory stats when out-of-memory event is detected. (#114)
- Correctly handle bad data from cgroups about memory limits, fixing erroneous out-of-memory caused by Docker. (#113)
- Out-of-memory detection should work in many more cases than before. (#96)
- Fil now supports Python 3.9. (#83)
- Fil no longer uses a vast amount of memory to generate the SVG report. (#102)
- Fixed bug that would cause crashes when thread-local storage destructors allocated or freed memory. Thanks to @winash12 for reporting the issue. (#99)
- Allocations in C threads are now considered allocations by the Python code that launched the thread, to help give some sense of where they came from. (#72)
- It's now possible to run Fil by doing
python -m filprofilerin addition to running it asfil-profile. (#82) - Small performance improvements reducing overhead of malloc()/free() tracking. (#88 and #95)
- When running in Jupyter, NumPy/BLOSC/etc. thread pools are only limited to one thread when actually running a Fil profile. This means Fil's Jupyter kernel is even closer to running the way a normal Python 3 kernel would. (#72)
- When tracking large numbers of allocations, Fil now runs much faster, and has much less memory overhead. (#65)
- Added support for tracking allocations done using
posix_memalign(3). (#61)
- Fixed edge case for large allocations, where wrong number of bytes was recorded as freed. (#66)
- Switched to using jemalloc on Linux, which should deal better both in terms of memory usage and speed with many small allocations. It also simplifies the code. (#42)
- Further reduced memory overhead for tracking objects, at the cost of slightly lower resolution when tracking allocations >2GB. Large allocations >2GB will only be accurate to a resoluion of ~1MB, i.e. they might be off by approximately 0.05%. (#47)
- Significantly reduced the memory used to generate the SVG report. (#38)
- Reduced memory overhead of Fil somewhat, specifically when tracking large numbers of small allocations. (#43)
- Fix bug that prevented Fil from running on macOS Mojave and older. (#36)
- C++ allocations get tracked more reliably, especially on macOS. (#10)
- Validated that Fortran 90 allocations are tracked by Fil. (#11)
- Anonymous mmap()s are now tracked by Fil. (#29)
- macOS is now supported. (#15)
- Running
fil-profilewith no arguments now prints the help. (#21)
- Fil now helps debug out-of-memory crashes by dumping memory usage at the time of the crash to an SVG. This feature is experimental.
- Generating the report should run faster.
- Allocations from the
realloc()allocation API are now tracked by Fil.
- Fix a bug that corrupted the SVGs.
- Hovering over a frame now shows the relevant details on top, where it's visible.
- Command-line arguments after the script/module now work. To make it easier to implement, changed the code so you do
fil-profile run script.pyinstead offil-profile script.py.
- The flame graphs now include the actual code that was responsible for memory use.