292005 - Files somtimes remain locked after uploading through forms.

Status: RESOLVED DUPLICATE of bug 183689

(Core :: Layout: Form Controls, defect)

Description

[Robert Chapin]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.7) Gecko/20050414 Firefox/1.0.3
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.7) Gecko/20050414 Firefox/1.0.3

I am having this problem specifically with the cPanel File Manager, which allows
webmasters to upload files to a virtual host using HTTP.

On random intervals, approximatley every 5-10 tries, the files remain locked
after uploading.  Symptoms:  #1 If file is open in an editor it cannot be saved
or overwritten.  #2 File cannot be deleted using Windows Explorer.

Problem is always resolved after closing the FireFox window that includes the
cPanel tab.  It is not necessary to close any other windows.  File lock is
released even if FireFox process is still running.

Reproducible: Sometimes

Steps to Reproduce:
1.  Upload a file using an HTTP form.
2.  Try to modify or delete that file.
3.  Rinse and repeat.
Actual Results:  
On about 10-20% of attempts the uploaded file remains read-locked by FireFox.

Expected Results:  
Read locks should be released immediately after upload, or sooner!

I can't think of any system settings that would affect this bug.

I am rating this bug "Critical" because it will lead to data loss in other
applications unless the user takes specific actions to correct it.

Comment 1

[Robert Chapin]

Closing the tab also resolves the problem.  It is not necessary to close the
window.  Next time I encounter this problem I will also try navigating away from
the page and see what happens.

-- Miqro

Comment 2

[Robert Chapin]

Further testing reveals this problem cannot be resolved by navigating away from
the page.  Also, if the page is loaded into the last (only) tab, then closing
that tab also has no effect.  At that point it is necessary to close the window
to release the affected file.

Comment 3

[Steve Chapel]

*** This bug has been marked as a duplicate of 183689 ***