Matlab 2020b Update 6 creating dig folder

Running Matlab 2020b for the last year and it just started creating a "dig" folder in whatever directory I am running an m-script from. What needs reset to correct this?

[Walter Roberson]

https://www.mathworks.com/matlabcentral/answers/684778-dig-folder-blob-storage-cache

[dpb]

I've also been (and am) running R2020b-6 and so far haven't seen any sign of this...

[Walter Roberson]

I think it is Simulink related

[dpb]

ahhh...no have Simulink. Missed seeing that connection.

[Robert MCNAULL]

It just started doing it this week and have been running it for 6+ months on this computer.

Started 2 days ago when testing a simulink model running data through it and calling it via an m-script.

This also continued when processing data with only an m-script. So may be simulink related, but is doing it now for standalone m-script. Wondering if there is a reset of preferences or reference data that would clear this issue?

Walter - thanks for the response, but also read that thrread earlier and really provided no information on solving the issue.

[Robert MCNAULL]

It also generates the files/folders on opening matlab.

[dpb]

I'd say it qualifies for bug report/official support request. Support has been able to point to how to delete a preferences file in the past to fix similar issues about other strange things I've observed with what appeared to be editor-created backup files. They know where the magic pieces are hidden that can get rid of to start w/ fresh that aren't documented.

[Walter Roberson]

I would check startup.m

[Robert MCNAULL]

Hi Walter - I have nothing in my startup.m

When I have a chance later today I'll ping matlab support directly.

[Kory]

I was experiencing this problem on 2020b Update 6 as well and resolved it by clearing C:\Users\<USERID>\AppData\Local\Temp

[bo peng]

so great

[Robert MCNAULL]

I failed to folow up here - Matlab support followed up rather quickly at the time, this was a known bug with 2020a - 2021b. This was resolved by installing Update 7 for the version I was running (2020b).

Answer 1

[Steven Lord]

I believe this is Bug Report 2419782 which indicates it is fixed in the general release of R2022a and in updates for several other releases.