Where do these point to?
 

Hi,
I'm currently trying to troubleshoot a firefox session that's basically frozen. It gives you the outline of the firefox window but no output. I straced it and it gave me the following:

gettimeofday({1160114070, 821503}, NULL) = 0
gettimeofday({1160114070, 822416}, NULL) = 0
gettimeofday({1160114070, 823256}, NULL) = 0
write(71, "\372", 1) = 1
read(67, 0xbfc046f7, 1) = -1 EAGAIN (Resource temporarily unavailable)
read(19, 0xbfc046c7, 1) = -1 EAGAIN (Resource temporarily unavailable)
read(5, 0xbfc04697, 1) = -1 EAGAIN (Resource temporarily unavailable)

over and over again. So it looks like it's waiting for the resource at fd's 67, 19, and 5. I went to /proc/12899/fd and ran ls -l on these fd's and all I get is:

user@linux:/proc/12599/fd$ ls -l 67
lr-x------ 1 user user 64 2006-10-06 08:49 67 -> pipe:[550525]
user@linux:/proc/12599/fd$ ls -l 19
lr-x------ 1 user user 64 2006-10-06 08:49 19 -> pipe:[550519]
user@linux:/proc/12599/fd$ ls -l 5
lr-x------ 1 user user 64 2006-10-06 08:44 5 -> pipe:[290529]

So what are these really pointing to? Any ideas on how to proceed? Thanks for your help.

PS. I ran ulimit -a to see the limits of the user account and basically everything is unlimited. Here are the details:

core file size (blocks, -c) 0
data seg size (kbytes, -d) unlimited
file size (blocks, -f) unlimited
pending signals (-i) unlimited
max locked memory (kbytes, -l) unlimited
max memory size (kbytes, -m) unlimited
open files (-n) 1024
pipe size (512 bytes, -p) 8
POSIX message queues (bytes, -q) unlimited
stack size (kbytes, -s) 8192
cpu time (seconds, -t) unlimited
max user processes (-u) unlimited
virtual memory (kbytes, -v) unlimited
file locks (-x) unlimited

Looks like a flash page that didn't load. Try moving the flashplugin out of the plugins folder temporarily. Gosh dang I hope flash 9 comes out on schedule.

Thanks fozner. I was forced to kill the firefox session. Anyway, what makes you think that it was a flash page that didn't load?

Well, that was just a wild guess. In all my years of using it, Flash is the only thing that I have been able to crash Firefox with, well that and extraordinarily long lines of text (but those crash X as well, because of proprietary nVidia driver, which is probably already fixed in the latest version as I digress)...