Mod Delete Delete

[Stella Kreuter]

Iwent in search of how to do this early this morning but found nothing. I went the to forum to search and came across the information in one thread after searching through a number of different threads. Some of the access dates were as recent as May. When I went to the help menu to search for "empty trash" and other variations of phrasing, I kept getting the same threads I had already seen. So, I created a thread for the answer that I found in case anyone else comes along looking.

And I expect there might be more people looking to do so since Dropbox is changing so much of how users, especially free account holders, can use their accounts. I know several people who have recently deleted their accounts because it feels like DB is slowly forcing users into having access to less and less unless one holds a Pro account (i.e. one that pays DB money).

As for Dropbox making users have access to less and less in a way to force them to buy a Pro account, they have actually gone more the other way recently - shared folder permissions used to be Pro only, now they are available to Basic users as well. One example out of loads I can think of.

The command list with "permanently delete" doesn't come up for me. Instead a pop up box with the file name and an option to restore comes up. I tried two different computers. I am not part of an enterprise or on a business plan with Dropbox. So there is no admin to remove my ability to permanently delete files. I was on the basic plan, but upgraded to pro thinking that might help. But it's still the same. I tried contacting support and just got a generic form answer that had nothing to do with the problem.... Any ideas how I can get this fixed?

Did this post not resolve your issue? If so please give us some more information so we can try and help - please remember we cannot see over your shoulder so be as descriptive as possible!

This is an A/B test running through March 25th, testing an update that removes the ability for users to delete their own stories from the story feed. This is in support of the idea to make the story feed a more reliable source of truth for all Asana users.

Thanks for sharing your feedback and use case, @Sarah_L! As Phil mentioned, this is currently an A/B test and it will run for another few weeks. I will pass your feedback to our product team so they can consider it when analysing the results of this test and deciding any iteration.

Important note: To help us resolve your issue as quickly as possible, please ensure to fill out all the sections below. Do not share any private information such as email addresses or phone numbers - This is a public Forum!

I also vote to restore the ability to delete my own activity log entries in the activity logs at tasks, this is especially relevant when we use template tasks that are then duplicated for e.g. new launches etc.

Individual task duplication also happens frequently and starting clean is best.

I've been trying to find out what is taking space in my Dropbox. When I go to Manage account it says I have 11.8 GBs of Backups out of 15 GB. However I cannot actually find out what backup this is nor delete it.

All the steps I've checked on the site talks about installing a Desktop App then going to Sync and Backup. However there's no such thing. I'm using the latest Dropbox app downloaded from Dropbox website and running on Windows 11.

Also if I go to Dropbox app in the taskbar and then click on my account name then go to Preferences there's an option for the tab called Backups. However this tab opens up just the folders however I've not selected any folders to be backed up. There's no way to actually delete backups.

I've tried unlinking all devices from my account, deleting all files in the directories and still there's this 11GB just missing. Why can't Dropbox app just show what is taking the space and have an option to delete it?

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 recently accidentally clicked yes to backing up to Dropbox a USB with a lot of photos and some videos on it. It has taken up all my storage, which I don't want to do. I want to delete it, but it is not showing up on my list of files on my computer. Can anyone advise me how to find the file so it can be deleted?

Heap memory allocator must know the size of bytes allocated and using sizeof(Type) its possible to find no of elements and to call appropriate no of destructors for an array to prevent resource leaks.

Does the pointer being deleted point to a single object or to an array of objects? The only way for delete to know is for you to tell it. If you don't use brackets in your use of delete, delete assumes a single object is pointed to.

Also, the memory allocator might allocate more space that required to store your objects and in this case dividing the size of the memory block returned by the size of each object won't work.

Depending on the platform, the _msize (windows), malloc_usable_size (linux) or malloc_size (osx) functions will tell you the real length of the block that was allocated. This information can be exploited when designing growing containers.

Another reason why it won't work is that Foo* foo = new Foo[10] calls operator new[] to allocate the memory. Then delete [] foo; calls operator delete[] to deallocate the memory. As those operators can be overloaded, you have to adhere to the convention otherwise delete foo; calls operator delete which may have an incompatible implementation with operator delete []. It's a matter of semantics, not just keeping track of the number of allocated object to later issue the right number of destructor calls.

Long answer: The run-time system stores the number of objects, n, somewhere where it can be retrieved if you only know the pointer, p. There are two popular techniques that do this. Both these techniques are in use by commercial-grade compilers, both have tradeoffs, and neither is perfect. These techniques are:

Plain delete isn't required to handle both individual objects an arrays. This avoids complicating the common case of allocating and deallocating individual objects. It also avoids encumbering individual objects with information necessary for array deallocation.

Exactly how arrays and individual objects are allocated is implementation-dependent. Therefore, different implementations will react differently to incorrect uses of the delete and delete[] operators. In simple and uninteresting cases like the previous one, a compiler can detect the problem, but generally something nasty will happen at run time.

The main reason why it was decided to keep separate delete and delete[] is that these two entities are not as similar as it might seem at the first sight. For a naive observer they might seem to be almost the same: just destruct and deallocate, with the only difference in the potential number of objects to process. In reality, the difference is much more significant.

The most important difference between the two is that delete might perform polymorphic deletion of objects, i.e. the static type of the object in question might be different from its dynamic type. delete[] on the other hand must deal with strictly non-polymorphic deletion of arrays. So, internally these two entities implement logic that is significantly different and non-intersecting between the two. Because of the possibility of polymorphic deletion, the functionality of delete is not even remotely the same as the functionality of delete[] on an array of 1 element, as a naive observer might incorrectly assume initially.

Contrary to the strange claims made in some other answers, it is, of course, perfectly possible to replace delete and delete[] with just a single construct that would branch at the very early stage, i.e. it would determine the type of the memory block (array or not) using the household information that would be stored by new/new[], and then jump to the appropriate functionality, equivalent to either delete or delete[]. However, this would be a rather poor design decision, since, once again, the functionality of the two is too different. Forcing both into a single construct would be akin to creating a Swiss Army Knife of a deallocation function. Also, in order to be able to tell an array from a non-array we'd have to introduce an additional piece of household information even into a single-object memory allocations done with plain new. This might easily result in notable memory overhead in single object allocations.

3a8082e126