Release 2.19.3 notes
------------------

yCrash Server - Features and Fixes:


+ Implemented logic to detect memory leaks in the metaspace memory region.
+ Excluded the hot.jar script from the codebase.
+ Discontinued the highlighting of log statements containing error/exception keywords, even when the log level was DEBUG or WARN, to prevent false reporting.
+ Resolved the issue of duplicate error reporting in thread dump analysis.
+ Omitted the reporting of Max GC time in the GC log analysis report when parsing jstat log output, as the jstat log output does not contain Max GC pause time metrics.
+ Addressed various bug fixes in yCrash reports.
+ When uploading logs from cooltools web applications or individual uploads, filenames will now be displayed as tags.
+ Log Error Detection Settings: The application log file records various events, errors, and information during application execution. 
The yCrash agent monitors the application log for critical errors. When critical errors are reported in the application log, the yCrash agent captures 360° troubleshooting artifacts from the application stack (GC log, thread dump, top, netstat, vmstat, dmesg...) and sends them to the yCrash server for analysis. 
By default, Stackoverflowerror and OutofMemoryError have been added to global settings in log error settings to capture 360-degree data whenever an error related to Stackoverflowerror or OutofMemoryError occurs.
+ Resolved the issue of redundant waiting thread error/warning messages in the RCA report.