**Found in** * 134.0a1 (2024-10-29) **Affected versions** * 134.0a1 (2024-10-29) **Tested platforms** * Affected platforms: Windows 10x64, Windows 11 * Unaffected platforms: macOS, Ubuntu 24, **Preconditions** * Download the DLP test assets from https://drive.google.com/file/d/1yjqVRuxdKV3WnO7D2wzMgDXBuYBxUgVw/view * Create a distribution folder inside the Firefox folder and paste the policies-2.json to it and then rename it to policies.json * run the DLP agent in CMD using: .\content_analysis_sdk_agent.exe --user --toblock=.*\d{3}-\d{2}-\d{4}.* --towarn=.*warn.* --delays=10 **Steps to reproduce** 1. Copy a random string from one Wikipedia page to another. **Expected result** * The total scanning time is 10 seconds as stated in preconditions. **Actual result** * The total scanning time is 20 seconds. The are two scans happening inside the agent. **Regression range** * I cannot reproduce this issue with 133.0b1, so this likely happens after bug 1915351. **Additional notes** * Attached a screen recording.
Bug 1927766 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
**Found in** * 134.0a1 (2024-10-29) **Affected versions** * 134.0a1 (2024-10-29) **Tested platforms** * Affected platforms: Windows 10x64, Windows 11 * Unaffected platforms: macOS, Ubuntu 24, **Preconditions** * Download the DLP test assets from https://drive.google.com/file/d/1yjqVRuxdKV3WnO7D2wzMgDXBuYBxUgVw/view * Create a distribution folder inside the Firefox folder and paste the policies-1.json to it and then rename it to policies.json * run the DLP agent in CMD using: .\content_analysis_sdk_agent.exe --user --toblock=.*\d{3}-\d{2}-\d{4}.* --towarn=.*warn.* --delays=10 **Steps to reproduce** 1. Copy a random string from one Wikipedia page to another. **Expected result** * The total scanning time is 10 seconds as stated in preconditions. **Actual result** * The total scanning time is 20 seconds. The are two scans happening inside the agent. **Regression range** * I cannot reproduce this issue with 133.0b1, so this likely happens after bug 1915351. **Additional notes** * Attached a screen recording.