Release 2.18 notes ------------------ yCrash Server ------------- Features and Fixes: + Introduce a new feature called My patterns in thread report. This feature will let the user add their custom pattern to matched in the thread dump. If they are matched, then it will be flagged as alert. + Introduce new settings in app settings page (Parallel Parsing, Only Troubleshooting report, only Performance report) + Time filtering GC log files was in beta version in the last release. Made several bug fixes and strengthened its implementation to handle complex cases. + Major enhancements and bug fixes in the M3. a) Not Triggering incident during Cooling Period b) At the very first time agent will create the first incident in the calendar. c) Transient Problems tripping m3 d) Bug fixes in UI. e) Changed throughput chart to memory usage chart in M3 dashboard. + Added capability to upload dump files from the individual report itself directly. + Strengthen upload heap dump validation in HeapHero. + Strengthen implementation of -DonlyTroubleshootingReport and -DonlyPerformanceReport properties in HeapHero. + Renamed dominator tree section to largest objects. + Changed the UI design of the heap report page. By default, it displays only the overview, leak suspect, and largest objects section in the troubleshooting report. The performance report will be collapsed by default. + Added support for read heap dump files which are compressed in '.tar.gz' file format. + Made several Bug fixed in HeapHero + FastThread tool wasn’t processing certain types of hs_err_pid log. Now it has been fixed + Added Potential solutions for hs_err_pid log. + Enhancements in Divide & Conquer Panel yCrash Agent: ------------- Features and Fixes: + Adjusted M3 Frequency to align with the complete 360-degree artifact capture cycle. – Previously, the capture cycle wasn't aligned with the "m3Frequency" settings, resulting in captures occurring only after 5 minutes if the frequency was set for intervals shorter than 5 minutes. During other frequency intervals, it exclusively captured GC logs and TOP data, omitting a comprehensive artifact collection. This adjustment ensures a complete capture cycle within the specified m3Frequency settings. + Agent versioning will now synchronize with the Server release cycle. + Avoiding full GC in the application while capturing heap substitute data from the application.