News:

NOTICE: This forum is mostly an archive, though new posts are allowed. Registration may require manual admin activation. After registering visit https://bitsum.com/contact/ to request account activation.

Main Menu

'Error clearing log file. Sharing violation?'

Started by gman68w, April 24, 2013, 10:26:36 AM

Previous topic - Next topic

gman68w

This is the message I get when trying to clear the log. It started appearing after the last update. It sounds like it's a problem with Windows, and I'm pretty sure it is because PL isn't the only program lately that won't let me clear away files that shouldn't be in use (for example uTorrent and clearing away .torrent files from recently finished downloads,  which are no longer in the list of active downloads/uploads). I've got UAC turned off, so I don't think it's a security/permissions issue.

BenYeeHua

Anti-virus?
It can be anti-virus or other software that scanning the file. :)

edkiefer

I get same error (error  clearing log file ,shared violation ),when trying to clear log .
after the message box closes it first looks like logs are cleared but after restart they didn't .
Bitsum QA Engineer

gman68w

yeah, if i click on either the 'Threads' or 'Modules' tab, then back on the 'Actions' tab, the whole log I meant to clear is still there.

BenYeeHua

Just tested awhile, yes, I also got the same error.
So this is Process Lasso New log system bug.
5:10:54.8159141 PM ProcessLasso.exe 5636 CreateFile C:\Users\**** NAME COLLISION Desired Access: Read Data/List Directory, Synchronize, Disposition: Create, Options: Directory, Synchronous IO Non-Alert, Open For Backup, Open Reparse Point, Attributes: N, ShareMode: Read, Write, AllocationSize: 0
5:10:54.8162569 PM ProcessLasso.exe 5636 QueryOpen C:\Users\**** SUCCESS CreationTime: 11/11/2012 10:23:48 AM, LastAccessTime: 20/4/2013 6:40:51 AM, LastWriteTime: 20/4/2013 6:40:51 AM, ChangeTime: 20/4/2013 6:40:51 AM, AllocationSize: 8,192, EndOfFile: 8,192, FileAttributes: D
5:10:54.8163488 PM ProcessLasso.exe 5636 CreateFile C:\Users\****\AppData\Roaming NAME COLLISION Desired Access: Read Data/List Directory, Synchronize, Disposition: Create, Options: Directory, Synchronous IO Non-Alert, Open For Backup, Open Reparse Point, Attributes: N, ShareMode: Read, Write, AllocationSize: 0
5:10:54.8165442 PM ProcessLasso.exe 5636 QueryOpen C:\Users\****\AppData\Roaming SUCCESS CreationTime: 11/11/2012 10:23:49 AM, LastAccessTime: 25/3/2013 1:42:20 PM, LastWriteTime: 25/3/2013 1:42:20 PM, ChangeTime: 25/3/2013 1:42:20 PM, AllocationSize: 16,384, EndOfFile: 16,384, FileAttributes: D
5:10:54.8166181 PM ProcessLasso.exe 5636 CreateFile C:\Users\****\AppData\Roaming NAME COLLISION Desired Access: Read Data/List Directory, Synchronize, Disposition: Create, Options: Directory, Synchronous IO Non-Alert, Open For Backup, Open Reparse Point, Attributes: N, ShareMode: Read, Write, AllocationSize: 0
5:10:54.8168107 PM ProcessLasso.exe 5636 CreateFile C:\Users\****\AppData\Roaming\ProcessLasso NAME COLLISION Desired Access: Read Data/List Directory, Synchronize, Disposition: Create, Options: Directory, Synchronous IO Non-Alert, Open For Backup, Open Reparse Point, Attributes: N, ShareMode: Read, Write, AllocationSize: 0
5:10:54.8170061 PM ProcessLasso.exe 5636 CreateFile C:\Users\****\AppData\Roaming\ProcessLasso\logs NAME COLLISION Desired Access: Read Data/List Directory, Synchronize, Disposition: Create, Options: Directory, Synchronous IO Non-Alert, Open For Backup, Open Reparse Point, Attributes: N, ShareMode: Read, Write, AllocationSize: 0
5:10:54.8171900 PM ProcessLasso.exe 5636 CreateFile C:\Users\****\AppData\Roaming\ProcessLasso\logs\prolasso.ini\ProcessLasso\prolasso.log PATH NOT FOUND Desired Access: Read Attributes, Delete, Disposition: Open, Options: Non-Directory File, Open For Backup, Open Reparse Point, Attributes: n/a, ShareMode: Read, Write, Delete, AllocationSize: n/a
5:10:54.8172762 PM ProcessLasso.exe 5636 QueryOpen C:\Users\****\AppData\Roaming\ProcessLasso\logs\prolasso.ini\ProcessLasso\prolasso.log.0 PATH NOT FOUND
5:10:55.6818149 PM ProcessLasso.exe 5636 CreateFile C:\Users\****\AppData\Roaming\ProcessLasso\logs\prolasso.log SUCCESS Desired Access: Generic Read, Disposition: OpenIf, Options: Synchronous IO Non-Alert, Non-Directory File, Attributes: NT, ShareMode: Read, AllocationSize: 0, OpenResult: Opened
5:10:55.6820375 PM ProcessLasso.exe 5636 QueryStandardInformationFile C:\Users\****\AppData\Roaming\ProcessLasso\logs\prolasso.log SUCCESS AllocationSize: 3,432,448, EndOfFile: 3,430,336, NumberOfLinks: 1, DeletePending: False, Directory: False
5:10:55.6820551 PM ProcessLasso.exe 5636 CloseFile C:\Users\****\AppData\Roaming\ProcessLasso\logs\prolasso.log SUCCESS

Jeremy Collake

Software Engineer. Bitsum LLC.

edkiefer

while the error message is gone, it still doesn't permanently clear log .
What I mean is it does clear log in window but it is only temporary, as soon as another action happens or you restart PL the whole log is loaded .

PS, power profile error still remains, I see in changelog work on energy profile but app power profile is not working (not sure you looked at it yet but mention just in case) .
Bitsum QA Engineer


Jeremy Collake

Yes, I see this. I'll fix it up later today.
Software Engineer. Bitsum LLC.

Jeremy Collake

#9
This (the log clear) is now properly fixed in internal builds. Sorry for the slip-up, all this new code simply is taking some time to flesh out. I obviously hadn't even tested the change in the last beta. The end result of all this work will be very positive, to say the least. It is long overdue. While the GUI hasn't changed much, yet, the internals are being aggressively refactored into a more ideal and efficient design.

Anyway, next beta all will function properly, guaranteed.
Software Engineer. Bitsum LLC.