New issue
Advanced search Search tips

Issue 677305 link

Starred by 1 user

Issue metadata

Status: Archived
Owner: ----
Closed: Feb 2018
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

Permanent file handle on DirectShow device

Reported by stan...@gmail.com, Dec 28 2016

Issue description

UserAgent: Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.28 Safari/537.36

Steps to reproduce the problem:
 This is a bit more complex, it resolves around the program ShareX (http://getsharex.com) that uses https://github.com/rdp/screen-capture-recorder-to-video-windows-free/ that creates a DirectShow device to let you capture your screen
2. Chrome now finds/uses this DirectShow device and keeps a file handle on one of the DLL files
3. So when you try to update ShareX, InnoSetup detects that there is a file handle on the DLL, it can't replace it and closes Chrome.

What is the expected behavior?
Chrome should close the handle on the DirectShow device

What went wrong?
Chrome keeps a permanent handle on the DLL file.

Did this work before? No 

Chrome version: 56.0.2924.28  Channel: beta
OS Version: 6.3
Flash Version: Shockwave Flash 24.0 r0

ShareX Bug Report: https://github.com/ShareX/ShareX/issues/692
screen-capture-recorder Bug Report: https://github.com/rdp/screen-capture-recorder-to-video-windows-free/issues/58
 
Labels: TE-NeedsTriageHelp
Project Member

Comment 2 by sheriffbot@chromium.org, Feb 12 2018

Status: Archived (was: Unconfirmed)
Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Sign in to add a comment