> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/6.1-eol/addressed-issues-in-traps-agent-6.1.3.md). # Addressed Issues in Traps Agent 6.1.3 | Issue ID | Description | | -------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | CPATR-7635 | Fixed a memory leak that occurred on specific network hardware during event collection of network events. | | CPATR-7577 (Linux) | Fixed an issue where ESM environments migrating to Traps management service cloud-based environments could not install Traps agent version 6.1.2 on Linux endpoints. Now in version 6.1.3, you can create an Upgrade from ESM agent installation package for Linux in Traps management service, upload it to ESM, and send out to all your agents for upgrade. | | CPATR-7575 | Fixed a compatibility issue with Traps and MicrosoftAppV, which caused the endpoint to become unresponsive sometimes. | | CPATR-7545 | Fixed an issue in the Traps upgrade process on Linux endpoints, where you had to restart the agent after Traps upgrade in order for the new kernel module to be updated. | | CPATR-7509 (Windows) | Fixed an issue on Windows endpoints, where sometimes the Traps agent would time-out during certain file operations. | | CPATR-7420 | Fixed a performance issue that occurred when event-log messages were parsed without caching. | | CPATR-7419 (Linux) | Fixed an issue on Linux endpoints, where injecting into processes caused them to hang. | | CPATR-7408 (Windows) | Fixed an issue where Windows endpoints overloaded the endpoint kernel stack and became unresponsive if a large number of drivers, including Traps, attempted to load at the same time. | | CPATR-7402 | Fixed a performance issue that occurred due to redundant file calls when Traps tampering protection was enabled. | | CPATR-7397 | Fixed a compatibility issue where an agent running Traps version 6.1.2 could not connect to the Traps management service if the Palo Alto Networks firewall deployed in the environment was set to enable SSL Decryption. | | CPATR-7396 (macOS) | Fixed a performance issue of increased compilation times for users on Mac endpoints running Traps. | | CPATR-7360 | Fixed an issue where the digital signer of the file was missing in the security event details extracted from the Traps endpoint during a scan. | | CPATR-7342 (Windows) | Fixed an issue on Windows endpoints where ransomware security events queried relative files by the file name instead of the file path. | | CPATR-7311 (macOS) | Fixed an issue where after restating the endpoint, Traps became incompatible with the macOS running on the endpoint. | | CPATR-2436 | Fixed an issue where the Signer was not being reported back to Traps management service as part of the security event during the scanning of files on Traps endpoints. | --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://cortex-docs.paloaltonetworks.com/6.1-eol/addressed-issues-in-traps-agent-6.1.3.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.