Closed
Bug 113785
Opened 23 years ago
Closed 23 years ago
locks when stat() fails
Categories
(Core Graveyard :: File Handling, defect)
Tracking
(Not tracked)
VERIFIED
WONTFIX
Future
People
(Reporter: markus, Assigned: bryner)
Details
I wanted to upload some file through HTTP POST. I click on browse, it opens a
file selection dialog box. when I tried to change to /mnt/ mozilla seems to be
stuck. (Doesn't update screen, mozilla-bin is <defun>). /mnt has some smb and
nfs file shares in it. One or more of them must have died, some console
application stated: 'stat on /mnt/entwicklung failed'. Just a guess: mozilla
doesn't react properly to stat failures. I haven't looked further into this issue.
Comment 1•23 years ago
|
||
Reporter: Please always include the "Build ID", as well as which Linux distro
you're using. Thank you.
Reporter | ||
Comment 2•23 years ago
|
||
Linux Redhat 7.1 / Ximian GNOME 1.4 all updates applied
buildid: 2001120521
Sorry.
![]() |
||
Comment 3•23 years ago
|
||
ccing bryner, since this is filepicker...
Markus, what happens if you run 'ls -l' on that directory?
Reporter | ||
Comment 4•23 years ago
|
||
Well...
I mounted a nfs share as /mnt/ibistest, shut down the nfs server. ls -l shows no
output, runs forever (5min). Seems to be some not mozilla specific issue...
I tried to reboot, and my box locked at the point where it tried to unmount
/mnt/ibistest. Had to reset. Weird.
![]() |
||
Comment 5•23 years ago
|
||
Sounds like the standard remote filesystem timeout thing is happening....
bryner, is there any way we can avoid freezing the entire UI in these
circumstances? Running filepicker file access on a separate thread or something?
Assignee: law → bryner
Status: UNCONFIRMED → NEW
Ever confirmed: true
Assignee | ||
Comment 6•23 years ago
|
||
I don't think we should take the overhead of running on a separate thread just
to catch this edge case.
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → WONTFIX
Target Milestone: --- → Future
Updated•9 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•