97090 - X Error of failed request: BadAtom (invalid Atom parameter)

Status: RESOLVED INCOMPLETE

(Core :: XUL, defect)

Description

[Scott Davis]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:0.9.3+) Gecko/20010817
BuildID:    2001082610 but I think also earlier versions

X Error of failed request:  BadAtom (invalid Atom parameter)
  Major opcode of failed request:  18 (X_ChangeProperty)
  Atom id in failed request:  0x0
  Serial number of failed request:  262180
  Current serial number in output stream:  262182


I reported something like this a few months ago, but withdrew it as I couldn't
get it to happen again. It seems repeatable over the last few days at least.

The browser dies with a message as above. I have tried mozilla -g, but it is
deliberately exiting, so I can't get a stack trace. I tried "stop in exit" in
the debugger, which made it run a lot slower, but still didn't catch the error
before mozilla quit.


Reproducible: Sometimes
Steps to Reproduce:
I haven't been able to make this occur on demand.

It usually happens when I'm busy, not just browsing. I think it is related to
re-ordering windows, and Mozilla drawing to a non-visible part of a window
(obscured by other windows).

I tend to use it with a Mailnews window and several browser windows open,
overlaying each other. I think this is more likely to crash when I click on a
link, then immediatly push that window to the back to look at another window
while that one is loading.

Is there a Talkback build for Solaris that could catch this?

Solaris 8, Ultra-10 workstation, Creator graphics (24-bit mode)

Comment 1

[Scott Davis]

I can't work out how, but this seems to be related to wehether I am running
Citrix ICA client to reach a Windows Terminal server. If I'm not, then Mozilla
is stable for days. With the ICA client open, mozilla will crash a number of
times per hour. I'm running Citrix ICA Client for Solaris Version 3.00.85 

Comment 2

[Peter Trudelle]

no idea who should get this, ->pavlov, hope he does.

Comment 3

[Scott Davis]

Oops - wrong way round. It doesn't crash with the Citrix ICA client running - it
crashes with theX11 client (Windows 2000) running.

I still don't understand how one X11 program can be caused to crash by another.

Comment 4

[Keyser Sose]

Marking these all WORKSFORME sorry about lack of response but were very
overloaded here. Only reopen the bug if you can reproduce with the following steps:

1) Download the latest nightly (or 0.9.6 which should be out RSN)
2) Create a new profile
3) test the bug again

If it still occurs go ahead and reopen the bug. Again sorry about no response
were quite overloaded here and understaffed.

Comment 5

[Christopher Hoess (gone)]

reopening.

Comment 6

[Gervase Markham [:gerv]]

choess: why did you reopen this bug? No response from the reporter for two
months is sufficient grounds for closing a bug.

ksosez: if you are going to appeal for sympathy when closing bugs, at least
encourage people to pitch in and help ;-)

Gerv

Comment 7

[Christopher Hoess (gone)]

Closing INVALID, no response from reporter. Please reopen if you can still
reproduce this.

Comment 8

[Scott Davis]

What "response from reporter" have you waiting for two months for?

I confirm I still get this error message/crash with Mozilla 0.9.5 within a few
minutes of opening the X11 client of Windows Terminal Server.

This confirmation was done with the Gnome UI (1.4), rather than CDE, running on
Solaris 8.

Comment 9

[Christopher Hoess (gone)]

confirming bug.  pav?

Comment 10

[Scott Davis]

I have checked - it still crashes with nightly build 2001111110.

How do I "create a new profile"? What should I backup/copy/rename so that I can
get back all my existing settings after the test?

Comment 11

[Bob Atkins]

After reading the additional comments I believe this bug should be left open.

SunOS 5.8 Generic_108528-12 sun4u sparc SUNW,UltraSPARC-IIi-Engine
Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:0.9.7) Gecko/20011221, build
2001122204
X server: 11r6
OpenWindows: 6.4.1
glib & gtk+ v1.2.10

I have been experiencing occasional crashes of mozilla for no particular reason.
Today mozilla crashed while I was viewing an email. I had not been unable to get
it to start back up after over 40+ attempts. Each startup got to the point where
the navigator window just completes filling in the home page (which is a local
bookmarks file) and then it crashes. During these tests I changed the preference
as to whether or not to start mail or just navigator - no effect. I removed
(actually renamed) the XUL.mfasl, panacea.dat and localstore.rdf files in my
profile directory just to see if they would have an effect (they were the last
modified files prior to the first crash). I also tried a different - basically
virgin profile that already existed and it also had no effect. Each time mozilla
started up it would crash as soon as the window had completed filling in.

Here are several diagnostic messages:

X Error of failed request:  BadAtom (invalid Atom parameter)
  Major opcode of failed request:  17 (X_GetAtomName)
  Atom id in failed request:  0x0
  Serial number of failed request:  3317
  Current serial number in output stream:  3317
X Error of failed request:  BadAtom (invalid Atom parameter)
  Major opcode of failed request:  17 (X_GetAtomName)
  Atom id in failed request:  0x0
  Serial number of failed request:  3315
  Current serial number in output stream:  3315
X Error of failed request:  BadAtom (invalid Atom parameter)
  Major opcode of failed request:  17 (X_GetAtomName)
  Atom id in failed request:  0x0
  Serial number of failed request:  3460
  Current serial number in output stream:  3460


I don't have gdb in this system so I trussed it instead. After not starting for
at least 40+ times in a row - as soon as I trussed it it started successfully
and is now running... I have been able to re-start several times without
problem. I can't re-create it for the moment but I'm confident that it will
happen again.

Hope this info helps.

Comment 12

[Bob Atkins]

Attachment: Truss output from startup crash

OK, today I had the startup crash happen several times and I was able to
successfully truss mozilla. I don't have the full truss output from the startup

(failed to log my xterm session to disk...) but I have attached what I have to
this comment. I would suppose that the most interesting part will be towards
the end anyway.

Comment 13

[Jack Cummings]

This happens to me on a regular ( if random ) basis, as well. It seems to happen
whenever I'm doing window ops, like jumping workspaces with sawfish... 

X Error of failed request:  BadAtom (invalid Atom parameter)
  Major opcode of failed request:  18 (X_ChangeProperty)
  Atom id in failed request:  0x0
  Serial number of failed request:  12341
  Current serial number in output stream:  12343

I'm using build 2002072222 for SunOS 5.6. 

How can I debug this?

--Jack 

Comment 14

[Scott Davis]

I hadn't seen this bug for a long time, but after rechecking the history, I
started Citrix X11 client to a Windows Terminal Server, and sure enough Mozilla
crashed soon after, so it can at least be considered reproducible for me.

Any other background info which someone might find interesting or helpful:

I'm running Mozilla 1.0 binary download (build ID: 2002061103), Solaris 8, CDE.
I didn't switch workspaces after opening the WTS session before Mozilla crashed.
I do have a second monitor now, but didn't when this bug was first filed.
Mozilla (and WTS client) are using :0.0 on a Creator3D video card in 24-bit
mode. OS Patches include 108652-51, 108528-14, 108773-14, 108827-20, 108940-41,
109154-12

I accessed the windows terminal server with a shell alias which expands to:
rsh win-server x11 -color 256 -display $DISPLAY -mcookie `xauth list $DISPLAY |
cut -d\  -f5`

It opens a large window, but I have no problem using the ICA client with an
equally large window.

Comment 15

[Damien Chrisment]

The same problem is well described in the following bug
http://bugzilla.mozilla.org/show_bug.cgi?id=209013

Comment 16

[m.]

Don't know if its really related (I only think so based on the error output), but I'm experiencing lots of crashes with Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9a3pre) Gecko/20070319 Minefield/3.0a3pre, in fact the crashes are here for last couple of weeks..
The crashes happen when searching for text on the page by hitting the slash (/) and typing the text.
I did not get any text error in the terminal previously, but now I got one:

(Gecko:19379): Gdk-CRITICAL **: gdk_x11_atom_to_xatom_for_display: assertion `ATOM_TO_INDEX (atom) < virtual_atom_array->len' failed
The program 'Gecko' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAtom (invalid Atom parameter)'.
  (Details: serial 3118461 error_code 5 request_code 19 minor_code 0)

Comment 17

[Robert Kaiser]

This bug has no info about current software versions, please file a new bug for new issues or reopen this one with current info, including a crash signature if it still happens.