This release is recommended for all users.

Improvements

• Fixed an issue where a sampling policy could cause a retention policy to stop running until restart.

• Fixed populating empty pages of CRDBs when objects are deleted.

• Fixed a crash when processing the tail aggregate on an empty derived attribute.

• Stricter hostname validation for incoming requests against a regular expression set in coronerd.conf’s .httpd.valid_hostname. The default is to not validate hostnames.

• Security improvements to frontend parameter validation.

• Increased object attribute limit in multipart uploads of error reports to 256 attributes from 128.

• Allow “.map” as sourcemap extension in symbol_extractor.

• Fixed guest access to various configuration elements.

• Fixed crashes in certain DWARF elements.

• Fixed bug in sourcemap deobfuscation using library rather than path. This bug was introduced in 1.61 and only affected the debugger view, and not fingerprints themselves.

• Support running coronerd with gimli or coresnapd for tracing crashes. The default is to retain gimli.

• Fixed minor inconsistencies in sampling and the sampling status output.

• Add several iOS libraries and frameworks to the minidump ignore rules. This may change existing fingerprints if reprocessing.

• Fix ingesting json-format errors with boolean attributes.

• dump_syms_mac: Optimize conversion time by up to 50% for large archives.

• Improve edge cases in C++ demangling.

• Fix inline function rendering when marshalling json-format error reports.

• Improve cleanup of unmapped symbol files.

• Several security improvements to fix information leaks.

• Several improvements to module and missing symbol handling.

• Improvements to sourcemap/proguard deobfuscation support.

• Add ability to generate missing symbol events for sourcemap and proguard deobfuscation files, to support symbold automatically downloading from appropriately configured symbol servers.

• Support adding security headers to HTTP responses from coronerd.conf.

• Fix watchdog timeouts from excessively large deletion requests.

• Apply /api/login rate limiting to /api/reset.

Other changes

• This release adds the following distros to the supported list:
  • Ubuntu 24.04 (Noble Numbat)
• This release drops the following distros from the supported list:
  • el/7, CentOS 7: due to June 2024 EOL

• The backtrace-coronerd-workflow package has been deprecated and is be replaced by backtrace-workflow > 2.0. The latter implements a standalone service to manage workflows.

  • Not all workflows implemented by backtrace-coronerd-workflow are implemented by backtrace-workflow; see the release notes of the latter for details.

  • coronerd 1.61 releases also support backtrace-workflows.

• Issue states will no longer be automatically transitioned by coronerd. In particular, issues are no longer created in in-progress state. Issue state is instead managed by the backtrace-workflows service.

• The scheduled reports implementation has been moved from coronerd to a new backtrace-scheduled-reports service.

  • coronerd 1.61 releases also support backtrace-scheduled-reports.

• Removed support for the _mod_log query parameter when submitting objects to coronerd. A detailed callstack log can be retrieved through the existing /api/callback endpoint instead.

• Removed support for synchronous delete in /api/delete.

• Removed support for missing symbol jlog journals and associated configuration items related to symbold: .symbold.json_enable, .symbold.flush_frequency, and .symbold.max_journal_entries. The functionality is implemented by missing symbol events instead.

• (Experimental) Support throttling compression. A new feature flag object:throttle_compression can be enabled to throttle compression on busy hosts. This is configurable by setting .compresion.throttle_time_ms (default 10ms) and .compression.throttle_num_blocks (default 128 blocks) in coronerd.conf. This feature is slated to be removed in 1.63.