1957349 - Canceling an ongoing operation and performing a new one will wait for the previous operations to complete before scanning the current one

Status: RESOLVED DUPLICATE of bug 1956629

(Firefox :: Data Loss Prevention, defect)

Description

[Alexandru Trif, Desktop Test Engineering [:atrif]]

Attachment: dlp_agent.gif

Found in

• 138.0a1 (2025-03-30)

Affected versions

• 138.0a1 (2025-03-30)
• 137.0

Tested platforms

• Affected platforms: Windows 10x64, Windows 11
• Unaffected platforms: Ubuntu 24, macOS

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
• DLP Agent is running: .\content_analysis_sdk_agent.exe --user --toblock=.*\d{3}-?\d{2}-?\d{4}.* --towarn=.*warn.* --delays=10

Steps to reproduce

1. Upload a folder with multiple files.
2. Cancel the scanning.
3. Perform a clipboard paste on the Wikipedia page.

Expected result

• The action from step 3 is scanned, and the action from step 1 is canceled.

Actual result

• The actions from step 1 are not canceled inside the DLP Agent; once completed, the action from comment 1 is scanned.

Regression range

• Not a regression.

Additional notes

• Attached a screen recording.
• This was filed for tracking purposes. Engineering announced to us that the demo DLP agent cannot cancel an ongoing operation, and this issue should not happen with a real agent.

Comment 1

[David Parks [:handyman]]

(In reply to Alexandru Trif, Desktop Test Engineering [:atrif] from comment #0)

• This was filed for tracking purposes. Engineering announced to us that the demo DLP agent cannot cancel an ongoing operation, and this issue should not happen with a real agent.

This is potentially true but hasn't been confirmed with a non-demo agent. Also, we have a fix for it that is nearly ready in bug 1956629. We do, however, expect that this is not as dramatic outside of test cases, so we don't consider it a blocker for the feature.