Junction Point Loop Windows 7

Submitted by GreedyAssistant on Tue, 03/27/2018 - 15:47
Forums: 
Support
Forum tags: 
bug

Hello,

I believe there is a potential bug in BleachBit.

Windows 7 has a junction point in the AppData folder which basically refers to itself. This is causing infinite recursions to occur of that folder.
For example, I am seeing things like:
Delete 0 C:\Users\***MY_USER_NAME***\AppData\Local\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Microsoft\Feeds\WebSlices~

As you can see, it is recursing into Application Data over and over again, when each subfolder is actually pointing to the same folder.
This is a well known problem: https://answers.microsoft.com/en-us/windows/forum/windows_7-files/window...

Someone needs to have bleachbit exclude the Application Data junction point in the AppData\Local folder to prevent this infinite recursion.

Your operating system: 
Windows 7

andrew

Tue, 03/27/2018 - 21:26

Hmm, I have not noticed that on any other systems. Are you using BleachBit 2.0 or another version? Do you know which single option (checkbox) this is related to? Do you have any special configuration on your system related to the junction point?

---
Andrew, lead developer

GreedyAssistant

Wed, 03/28/2018 - 09:40

I believe it is related to the "Deep Scan"

I am using BleachBit 2.0. I don't have any customization of that junction point to my knowledge. I do know that that problem has been known for some time, however. If you Google people trying to use robocopy, you'll see posts from people running into this issue. The solution is to exclude that junction.

Bleachbit doesn't seem to get stuck into an infinite recursion though. There must be some limit on the depth it searches, because eventually after maybe 5-10 minutes it will back out of that folder and finish the clean correctly. So, it is not stopping proper execution for me, it is just slowing things down. I think it is repeatedly scanning that folder over and over again as it descends that junction point. Like I said, there must be a path limit or something where it stops, because it does eventually move on.

I've never messed around with that junction point, so I assume it is all the default settings for it.

andrew

Sat, 03/31/2018 - 21:23

On a Windows 7 system I tried to reproduce this, but I could not. I tried starting BleachBit in two modes: administrative privileges and without. In both cases, BleachBit scanned C:\Users\***MY_USER_NAME***\AppData\Local\ but not Application Data under it. I turned on extra logging to check.

Would you mind trying something? Open the Windows file browser (explorer) and navigate to the Local directory. Then try to open the Application Data. Does it open? On mine I get the popup error Access Denied. I wonder whether yours is different

---
Andrew, lead developer

GreedyAssistant

Thu, 04/05/2018 - 10:52

Thanks for your reply.
I didn't see the Application Data folder at first, because I guess it is marked as a system folder. Once I went in and set view system folders, it appeared. Then, when I clicked it, it opened. I didn't get an error.
I right clicked and went into the properties and looked under security. It has my account listed as having "Full Control" (all boxes checked).
For "everyone" it only has "read and execute", "list folder contents", and "read" permissions.
Perhaps that's what the problem is? I've never messed with this junction point before and didn't even know it existed. Maybe some software on my system changed its permissions or something?

andrew

Sun, 04/08/2018 - 08:07

Yes, maybe some software on your computer changed it.

Try this solution: In BleachBit open the preferences. Then add this folder to the whitelist.

---
Andrew, lead developer

GreedyAssistant

Tue, 04/24/2018 - 21:40

Thanks for the response.
Adding that junction point to the whitelist doesn't fix it.
Now, instead of deleting things within that folder, BleachBit just skips them, but stills recurses in the junction point.

Skip 0 C:\Users\***USERNAME***\AppData\Local\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Google\Chrome\User Data\Default\Bookmarks.bak
Skip 0 C:\Users\***USERNAME***\AppData\Local\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Microsoft\Office\16.0\Lync\Tracing\Lync-16.0.9126.2116-Office-x86ship-U.etl.bak
Skip 0 C:\Users\***USERNAME***\AppData\Local\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Microsoft\Office\16.0\Lync\Tracing\Lync-16.0.9126.2152-Office-x86ship-U.etl.bak
Skip 0 C:\Users\***USERNAME***\AppData\Local\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Microsoft\Office\16.0\Lync\Tracing\Lync-AppSharingMediaProvider-0.AppSharingMediaProviderlog.bak
Skip 0 C:\Users\***USERNAME***\AppData\Local\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Microsoft\Office\16.0\Lync\Tracing\Lync-UccApi-0.UccApilog.bak
Skip 0 C:\Users\***USERNAME***\AppData\Local\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Google\Chrome\User Data\Default\Bookmarks.bak
Skip 0 C:\Users\***USERNAME***\AppData\Local\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Microsoft\Feeds\{5588ACFD-6436-411B-A5CE-666AE6A92D3D}~\WebSlices~
Skip 0 C:\Users\***USERNAME***\AppData\Local\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Microsoft\Office\16.0\Lync\Tracing\Lync-16.0.9126.2116-Office-x86ship-U.etl.bak
Skip 0 C:\Users\***USERNAME***\AppData\Local\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Microsoft\Office\16.0\Lync\Tracing\Lync-16.0.9126.2152-Office-x86ship-U.etl.bak
Skip 0 C:\Users\***USERNAME***\AppData\Local\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Microsoft\Office\16.0\Lync\Tracing\Lync-AppSharingMediaProvider-0.AppSharingMediaProviderlog.bak
Skip 0 C:\Users\***USERNAME***\AppData\Local\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Microsoft\Office\16.0\Lync\Tracing\Lync-UccApi-0.UccApilog.bak
Skip 0 C:\Users\***USERNAME***\AppData\Local\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Microsoft\Office\16.0\Lync\Tracing\WPPMedia\lync_MediaStack-6.0.8968.450-releases_CL2016_R18-x86fre-U.etl.bak
Skip 0 C:\Users\***USERNAME***\AppData\Local\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Application Data\Microsoft\Office\16.0\Lync\Tracing\WPPMedia\lync_MediaStackETW-6.0.8968.450-releases_CL2016_R18-x86fre-U.etl.bak