Release 2.20 notes ------------------ yCrash Server - Features and Fixes: + Integrated a new mathematical model to detect instances of memory over-allocation in applications. Upon detection, the tool will recommend specific percentage reductions to optimize memory usage and enhance performance. + Added support for parsing thread dumps generated by jcmd 22 in text format, enabling more comprehensive analysis and troubleshooting. + Extended support to include parsing thread dumps generated by jcmd 22 in JSON format, improving the tool's versatility and usability. + Introduced a new system property -DlogLevel to control log verbosity. For instance, setting -DlogLevel=error will log only error messages. + Added a new threshold parameter, socketReadThreadsSize, to define the maximum allowable number of socket threads. If this threshold is exceeded, an error message will be generated, preventing excessive resource consumption and potential performance issues due to too many open socket connections. + Enhanced dashboard calendar loading performance by caching data into the database. + Added flexibility to create custom log4j configuration files. Specify the file path as a system property using: -Dlog4j.configurationFile=. + Implemented various bug fixes in the REST API. yCrash Agent - Features and Fixes: + Enhanced the appLogs logic in m3 mode to prevent uploading the entire file upon first encounter. + Updated m3 mode to support the storagePath argument.