Additional data...
In the course of work I attempted to open Acrobat by double-clicking on a PDF file. Acrobat is currently stuck at 104 KB of memory allocated (CPU usage is hovering around 30%, and 78% of physical memory is in use).
Curiously, I was able to start the Semagic and Evernote applications "the usual way" after Acrobat choked, so it's not as if the application-starting mechanism has been impaired to the extent I've seen previously, but at least it's a data point.
And as a matter of fact, I do recall that on Saturday, one of the few apps that I did invoke soon after my system booted up was Acrobat, and that the "unable-to-start-apps" problem cropped up very soon thereafter (within 10 minutes of bootup).
That said, I probably should avoid jumping to any premature conclusions regarding the cause of this chronic problem.
Cheers...
Curiously, I was able to start the Semagic and Evernote applications "the usual way" after Acrobat choked, so it's not as if the application-starting mechanism has been impaired to the extent I've seen previously, but at least it's a data point.
And as a matter of fact, I do recall that on Saturday, one of the few apps that I did invoke soon after my system booted up was Acrobat, and that the "unable-to-start-apps" problem cropped up very soon thereafter (within 10 minutes of bootup).
That said, I probably should avoid jumping to any premature conclusions regarding the cause of this chronic problem.
Cheers...