88671 - Program reciveed signal SIGPIPE,Broken pipe. 0x40582b94 in __libc_write () from /lib/i686/libc.so.6 GLIBC 2.2.3

Status: VERIFIED DUPLICATE of bug 85542

(Core Graveyard :: Plug-ins, defect)

Description

[Knut J]

Could not open file
/home/knutjbj/.mozilla/knutjbj/qf98bq9o.slt/NewCache/A2874ECEd01
/home/knutjbj/.mozilla/knutjbj/qf98bq9o.slt/NewCache/A2874ECEd01
/home/knutjbj/.mozilla/knutjbj/qf98bq9o.slt/NewCache/A2874ECEd01
/home/knutjbj/.mozilla/knutjbj/qf98bq9o.slt/NewCache/A2874ECEd01
/home/knutjbj/.mozilla/knutjbj/qf98bq9o.slt/NewCache/A2874ECEd01
/home/knutjbj/.mozilla/knutjbj/qf98bq9o.slt/NewCache/A2874ECEd01
/home/knutjbj/.mozilla/knutjbj/qf98bq9o.slt/NewCache/A2874ECEd01
/home/knutjbj/.mozilla/knutjbj/qf98bq9o.slt/NewCache/A2874ECEd01
/home/knutjbj/.mozilla/knutjbj/qf98bq9o.slt/NewCache/A2874ECEd01
/home/knutjbj/.mozilla/knutjbj/qf98bq9o.slt/NewCache/A2874ECEd01
/home/knutjbj/.mozilla/knutjbj/qf98bq9o.slt/NewCache/A2874ECEd01

Program received signal SIGPIPE, Broken pipe.
[Switching to Thread 1024 (LWP 1666)]
0x40582b94 in __libc_write () from /lib/i686/libc.so.6
Problem with plugger and midi files








Program received signal SIGPIPE, Broken pipe.
[Switching to Thread 1024 (LWP 1666)]
0x40582b94 in __libc_write () from /lib/i686/libc.so.6

Comment 1

[R.K.Aa.]

Please always include the build ID in bug-reports.

Comment 2

[Knut J]

Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.2) Gecko/20010630
full backtrace from gdb
Could not open file /root/.mozilla/knutjbj/bv8uw5sw.slt/NewCache/55E4B117d01
/root/.mozilla/knutjbj/bv8uw5sw.slt/NewCache/55E4B117d01
/root/.mozilla/knutjbj/bv8uw5sw.slt/NewCache/55E4B117d01
/root/.mozilla/knutjbj/bv8uw5sw.slt/NewCache/55E4B117d01
/root/.mozilla/knutjbj/bv8uw5sw.slt/NewCache/55E4B117d01
/root/.mozilla/knutjbj/bv8uw5sw.slt/NewCache/55E4B117d01
/root/.mozilla/knutjbj/bv8uw5sw.slt/NewCache/55E4B117d01
/root/.mozilla/knutjbj/bv8uw5sw.slt/NewCache/55E4B117d01
/root/.mozilla/knutjbj/bv8uw5sw.slt/NewCache/55E4B117d01
/root/.mozilla/knutjbj/bv8uw5sw.slt/NewCache/55E4B117d01
/root/.mozilla/knutjbj/bv8uw5sw.slt/NewCache/55E4B117d01
Xlib: unexpected async reply (sequence 0x2bc7)!
Gdk-ERROR **: BadIDChoice (invalid resource ID chosen for this connection)
  serial 11158 error_code 14 request_code 53 minor_code 0
Using pending wait status for LWP 2468.

Program received signal SIGINT, Interrupt.
[Switching to Thread 2051 (LWP 2468)]
0x404d5ff5 in __sigsuspend (set=0x40ce08cc) at
../sysdeps/unix/sysv/linux/sigsuspend.c:45
(gdb) frame 1
#1  0x401ea269 in __pthread_wait_for_restart_signal (self=0x40ce0be0) at
pthread.c:942
	in pthread.c
(gdb) frame 0
#0  0x404d5ff5 in __sigsuspend (set=0x40ce08cc) at
../sysdeps/unix/sysv/linux/sigsuspend.c:45
	in ../sysdeps/unix/sysv/linux/sigsuspend.c
(gdb) frame 9
#9  0x401e7e6f in pthread_start_thread_event (arg=0x40ce0be0) at manager.c:298
	in manager.c

Comment 3

[Chris Hiner]

See these other bugs with plugger: bug 74080 with a similar stack to your first
one, and bug 85542 similar to the second.

Comment 4

[Keyser Sose]

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

Comment 5

[Jay Farrell]

I just wanted to note that I got the following gdk-error on 2 OpenVMS systems
running with a build from 20011205. I was running test last Friday when access
to the Front-end test suite at www.mozilla.org was lost, from what I assume was
an issue with mozilla.org, since I could get to other web sites. I left mozilla
running, with the error pop-up window saying that I couldn't connect to
mozilla.org and when I came in on Monday, mozilla was no longer running and
I saw the following:

CSWS4> @sys$common:[cswb]mozilla 
Starting mozilla-bin... 
Xlib: resource ID allocation space exhausted! 
Gdk-ERROR **: BadIDChoice (invalid resource ID chosen for this connection) 
  serial 26956114 error_code 14 request_code 55 minor_code 0 
Gdk-ERROR **: BadGC (invalid GC parameter) 
  serial 26956115 error_code 13 request_code 62 minor_code 0 
  
  
  (same on CSWS1, except serial numbers were 27032323 and 27032324) 


 I have been able to restart Mozilla, and will continue with testing. I don't
 know if the info regarding what was going on when this problem occured will
 help in tracking down it's source, but I figured it couldn't hurt! Added the
 info to this bug, since it mentions a similar GDK-Error message. 

Comment 6

[Jay Farrell]

 I got the following error again when running the image test
http://www.mozilla.org/quality/browser/front-end/testcases/imaging/img-anim-
stability/img-anim-stability-desc.html

 The test says this should run for 24 hrs, but I kicked it off around 5:30 PM
 and it was dead when I went back to the lab around 8:30 am the next morning.

 I saw this error on 2 OpenVMS machines, and I've just started the test on a 
 Linux machine to see if its a problem there. (Won't know til tomorrow, 
 probably)


CSWS4> @sys$common:[cswb]mozilla 
Starting mozilla-bin... 
Xlib: resource ID allocation space exhausted! 
Gdk-ERROR **: BadIDChoice (invalid resource ID chosen for this connection) 
  serial 15517413 error_code 14 request_code 55 minor_code 0 
Gdk-ERROR **: BadGC (invalid GC parameter) 
  serial 15517414 error_code 13 request_code 57 minor_code 0 

 (same on csws1 with serial ids: 15893280 and 15893281) 

  

Comment 7

[Colin Blake]

The following internal publication explains the problem for OpenVMS:
[reference decwindows 6286.3]

  Note 1725 explains some of the issues involved with running out of
  resource IDs.

  From the X11 R5 edition of "X Window System" by Scheifler and Gettys, page
  503:

        Resource IDs never have the top three bits set.  The client is not
        restricted to linear or contiguous allocation of resource IDs.
        Once an ID has been freed, it can be reused, but this should not be
        necessary.

  I'm not sure but I think the R6 version of Xlib reuses resource IDs.

OpenVMS is still at R5, and that implementation uses a finite number of resource 
IDs. It looks to me like this problem can't be solved by Mozilla. OpenVMS needs 
a newer and smarter MOTIF.

Comment 8

[shrirang khanzode]

mass duplicate verifications . For filtering purposes, pls use keywd
"massdupverification"