Version 15.0.2.432 (but the issue is present in prior versions)

I am using a very high-end machine, and Bridge performs well when connected to the internet. However, I am often offline for days at a time in the field while taking and processing photos. Bridge is effectively unusable when there is no internet connection. Once I'm back online, the issue disappears. To be specific, the issue involves extreme lag when adding/removing labels, ratings, navigating thumbnails, viewing "high quality preview" and opening images into Camera Raw. I would imagine that many other actions are impacted by the issue, but these are the actions I most often perform when culling images in the field while offline.

I am 100% certain that Bridge is attempting web calls on nearly every single user action (presumably for Adobe's own internal user analytics), and it is doing so in a terribly inefficient manner that renders the software inoperable with repeated crashes and/or unnecessarily long wait times between actions. When the lag becomes too bad for me to continue, the app will not close (presumably because so many background web calls are queued). I have to force quit the application and then try and do a small batch of other reviews before the lag returns and I have to repeat the cycle by force quitting the app again until my patience expires and I have to wait until I'm back online. Every.single.time when I'm back online, Bridge goes right back to performing decently well.

As a user that relies on software in the field while offline, it is a completely debilitating issue that will end my use of Adobe products if it is not fixed in short order, unfortunately. I'm a long time fan of the products, but this issue came up at least a year ago and has become too much of a burden as someone that must operate in an offline environment for a few days at a time on a regular basis.

Bridge can (and should) disable these constant web calls when no connectivity is present. It should not check for internet on every single user action. Instead, Bridge should conduct the connectivity check at launch, and if no connectivity is present then Bridge should fully disable all web calls until a subsequent re-launch of the app reconnects to the internet.

The flaw is incredibly disruptive to an important part of my workflow. Please correct the issue.