Force Quit Mac
Luar Ehria
I cannot Force-quit brave. It is open always even though I try force quitting it. I cannot even put it in the trash. It is Open but not open at the same time. I know it sounds weird but it is the truth!
Setup a new user in Mac High Sierra. All works fine except Dropbox. I open it but no window appears. I try to delete it so I can set it up again but it won't move to the Trash because it says it's open. I have made sure it is not in Log0n Items and it doesn't appear in force quit.
Hi @Blain B., can you please see if the Dropbox process appears in the Activity Monitor. Just launch Spotlight search ([command] + [space bar]) and search for Activity Monitor. There in the Memory tab, you should find Dropbox process if it is running. Select the process, and click force quit. Then uninstall Dropbox and reinstall. If the problem persists try these steps -web/advanced-reinstall
Did this post help you? If so, give it a Like below to let us know.
Need help with something else? Ask me a question!
Find Tips & Tricks Discover more ways to use Dropbox here!
Interested in Community Groups? Click here to join!
These instructions do not help to remove Dropbox nor tell me how to uninstall since it says there are "plugins in use" when I tried to force quit Dropbox and move to the trash. I am using Macbook Air OS 10.10.5. Now I remember why I quit using Dropbox before. PLEASE HELP!
In order to fix this issue, you should open the 'Activity Monitor' utility on your computer, normally located under Applications > Utilities, and see if there are any other processes associated with Dropbox that may be preventing Dropbox from being removed from your device.
Did this post help you? If so, give it a Like below to let us know.
Need help with something else? Ask me a question!
Find Tips & Tricks Discover more ways to use Dropbox here!
Interested in Community Groups? Click here to join
I had the same problem. I followed the directions to use the Activity Monitor and force quit Dropbox. Still couldn't delete the app. Then I realized the dropbox things in the activity monitor that kept popping up were linked to Safari. I was in the Dropbox Support forum on Safari. I quit Safari. And was able to uninstall Dropbox...finally.
Like you, I normally just lock screen and close, so my MacBook had been running a long time since the last restart. Having restarted earlier as described, I just tried again. This time there was no hesitation or message.
Experimentally, I logged in to the Bitwarden app, then quit. In running processes (Activity Monitor - search bitwarden, sort by process) there was no evident difference. After quitting I clicked on the menu bar icon and Bitwarden came up immediately, open and logged in. Safari was open and its share extension logged in at the time.
Leaving aside that I need to explore to understand the above a little more, the fact it does not entirely quit is not a unilateral cause of the shutdown problem, or else everyone would encounter it. There is an interaction somewhere, either with App settings or with the Safari extension.
@raphant, the original problem raised by @Cy1 was that Bitwarden prevented shutdown. My options include minimising to menu bar on close, hence the fact Bitwarden does not actually quit. However, this does not prevent shutdown on my machine, as I tested again moments ago. Therefore the problem has more to it than setting that option.
I worked through the options in Settings paying attention to Close & Minimize to menu bar, if Close to menu bar is checked then Bitwarden does not quit. When un-checked, closing the Bitwarden window quits the application instead of closing the window.
Cy1, for a developer to look at it they will need unambiguous statements (and a bug report). I read your original problem as Bitwarden blocking shutdown. That Bitwarden does or does not quit in the circumstances of your last post is, to my knowledge and experience, expected behaviour. Further, we know from this thread that some people on both Intel and M chips do not experience the shutdown block.
While your communication style might come across as a bit unfriendly and patronizing, as a fellow developer, I appreciate your efforts to help narrow down the Bitwarden problem and assist the developers.
Raphael, the important thing is that @Cy1 submitted a bug report (for which I added a like on their post). I fully agree about characterising the problem which includes finding the correct causal sequence. The problem is that an unconditional statement that
is insufficient. I have tested repeatedly, and others supported, that routine shutdown can occur in the circumstances you describe, that Bitwarden acts normally on receipt of a kill message despite being set to Close to Menu Bar.
There is some additional condition or circumstance which combines with the Close to Menu Bar option but that condition is not present on all Macs or at all times, not a universal issue. It may be other software, some other condition of Bitwarden, or perhaps it is related to Apple silicon, the only recorded difference in our test environments. Developers need that additional characterisation, and I will wait on their responses. For me the rest would be speculation.
Bitwarden acts normally on receipt of a kill message despite being set to Close to Menu Bar.
There is some additional condition or circumstance which combines with the Close to Menu Bar option but that condition is not present on all Macs or at all times, not a universal issue
A smart maintenance app like CleanMyMac X has a problem of force quit on Mac covered. You can easily force quit a program on your Mac with its Menu app. To access it, click on a little iMac icon in the menu bar. It has a special Memory tab that allows to identify apps consuming too many resources and quit it with a click.
This helpful utility tool also helps you force quit hung applications. Direct access saves you time and allows to fix a frozen app in a matter of seconds. CleanMyMac also takes care of other performance issues, so if you want to get alerts when something goes wrong on your Mac, you can download its free version and give it a try. To use the Menu app, all you have to do is Enable Menu from CleanMyMac X Settings.
First of all, update an app to the latest version. App developers are constantly working on improvements, trying to deliver the best experience to users. The latest update may resolve all problems with the freezing app.
You may also try to delete an app and reinstall it. Usually, it resolves the problem of a frozen app. However, an easier way to do it is to reset an app using CleanMyMac X and the Uninstaller module that comes with this utility. It will bring the app you reset to the state it was in when you first installed it on your Mac, meaning that all the cache files will be deleted, and you will not have to reinstall it.
Is there an applescript term that I can use to Force-Quit a given application,
ie I would like it so when a script is run it Force-Quits say mail.app, not just normal quitting, but force-quitting it so it closes any open documents quickly. Is this possible?
Will this at as a Force-Quit, what I am looking to do is compile a script that I will set iCal to run at like 3AM that will Force_quit my Mail.app, Safari and iChat, the reason is, often I leve these applications open on accident and if iChat gets a message it prevets iChat from closing, and then stops my entire restart process and I am left in the morning with open windows open asking me if i want to save them. I just want everything closed automaticly.
I can't export my timeline anymore. I keep getting this error message after like an hour of exporting. It keeps saying The Force Quit Applications window pops open and says "Your system has run out of memory" and that Adobe Premiere is (paused).
I also had errors in my timeline. A sequence just completely stopped playing. Even if I copied and pasted it into the middle of my film (where the sequence belongs), the entire film would play but ultimately stop playing when it reached that part. I rectified this by going to each clip individually, and making a slight opacity change then back, to cause it to turn red in need of a re render. Once I rerendered, it played just fine.
(I realize when I opened my system settings, that my ram was listed as only 48 GB 1866 MHz DDR3. I cleaned it a month ago so I'll reinsert the ram and try to export again, don't think that would because this to be the issue do you?)
The fact that your System is mis-reading the amount of RAM it has installed is a pretty big red flag. There could be something corrupt with the RAM. Could be a simple fix of pull them out, blowing a bit and sticking them back in, or it could be something else. Is this third party RAM?
No the RAM isn't third party. I bought the full 64gb when the new Mac Pro came out. Do you thing since I've reseated it, and it now says 64gb instead of 48 that it's fine now? (I don't think this is the culprit anymore since it crashed on my MacBook Pro as well.)
Since you've identified a clip that has caused other problems in your sequence, I'd suggest deleting it, saving your project as a new file and then try export. See if it manages to complete without the file.
d3342ee215