Adobe Bridge 2027 (17.0.0.92) – Repeated freezes caused by thread deadlock
- 1 reply
- 36 views
- Translate
Application: Adobe Bridge 2027
Version: 17.0.0.92
Operating system: Windows 11
Build timestamp: October 23, 2026
Problem description
Adobe Bridge 2027 repeatedly becomes completely unresponsive, either shortly after startup or during normal operation.
The application may initially launch and display folder contents correctly, but subsequently freezes when performing basic operations, such as:
-
Switching between folders
-
Opening Preferences
-
Changing thumbnail size
-
Restoring the previously opened folder after restarting Bridge
Once the problem occurs, Bridge displays "Not Responding" and must be terminated using Windows Task Manager.
The issue occurs with both local drives and mapped network drives. Initially, I suspected a connection problem with a mapped network drive (X:), but the same behavior was subsequently reproduced on a local drive (E:).
Troubleshooting already performed
The following troubleshooting steps were tested:
-
Resetting Bridge preferences by renaming the user configuration folder under
%AppData%\Adobe. -
Starting Bridge with the Ctrl+Alt+Shift keyboard shortcut.
-
Disabling all startup scripts.
-
Re-enabling startup scripts selectively to identify a possible conflict.
-
Disabling the Adobe InDesign 2027 startup script.
-
Testing Bridge with both original and newly generated preference files.
-
Testing startup and folder navigation on local and network drives.
Disabling the InDesign startup script initially appeared to resolve the problem, but subsequent tests demonstrated that Bridge could still freeze with that script disabled.
Similarly, resetting preferences occasionally allowed Bridge to work temporarily, but the problem returned.
None of these measures provided a reliable solution.
Adobe Bridge Beta also exhibited similar freezing symptoms, although it has not been confirmed whether the underlying cause is identical.
Windows Wait Chain Analysis
While Adobe Bridge was frozen, I used the Windows Task Manager's Analyze Wait Chain feature.
It revealed a circular dependency between two threads within the Adobe Bridge process:
-
Thread ID 13528 (hexadecimal
0x34D8) -
Thread ID 29776 (hexadecimal
0x7450)
Thread 13528 was waiting for thread 29776, while thread 29776 was waiting for thread 13528.
This indicates a deadlock.
WinDbg analysis
I created an approximately 2.5 GB process memory dump while Adobe Bridge was unresponsive and analyzed it using Microsoft WinDbg.
The command !analyze -hang reported:
PROCESS_NAME: Adobe Bridge.exe
MODULE_NAME: Adobe_Bridge
IMAGE_NAME: Adobe Bridge.exe
FAILURE_BUCKET_ID: APPLICATION_HANG_cfffffff_Adobe_Bridge.exe!UnknownFurther analysis using !cs -l identified two locked critical sections:
Critical section 1
Critical section = 0x0000028a3ee04640
OwningThread = 0x34d8
RecursionCount = 0x1Critical section 2
Critical section = 0x0000028a930e7230
OwningThread = 0x7450
RecursionCount = 0x2The call stacks of both threads show that they are blocked while attempting to enter critical sections:
ntdll!NtWaitForAlertByThreadId
ntdll!RtlpWaitOnCriticalSection
ntdll!RtlpEnterCriticalSectionContended
ntdll!RtlEnterCriticalSection
Adobe_Bridge!...Both threads have very similar call stacks involving internal functions of Adobe Bridge.exe.
The available symbols are export symbols only, so the exact internal functions responsible for the deadlock could not be identified.
Conclusion and request
The diagnostics strongly indicate that Adobe Bridge becomes unresponsive due to a deadlock involving two threads within its own process.
The underlying trigger remains unknown. The issue may involve an internal synchronization defect or an interaction with another component.
Could the Adobe engineering team please investigate this behavior, particularly the synchronization between the two identified threads?
I have retained the complete process memory dump (Adobe Bridge.DMP, approximately 2.5 GB) and can provide it through an appropriate secure support channel if required.
I can also provide the WinDbg thread stack traces and Bridge application logs.
Thank you for your assistance.
