190093 - "Bad Image" when starting mozilla! complains about CustomImages.dll is not a valid windows image

Status: VERIFIED WORKSFORME

(Core Graveyard :: Talkback Client, defect)

Description

[Henrik Gemal]

CustomImages.dll is not a valid windows image

Comment 1

[Henrik Gemal]

Attachment: screenshot

Comment 2

[Adam Becevello]

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3b) Gecko/20030122

I'm seeing this as well.  It just started when I downloaded this build.  Mozilla
does start up if you press the OK button.

Comment 3

[Matthias Versen [:Matti]]

wfm with a 1h old CVS trunk build on win2k ?
Possible packing problem ?

Comment 4

[Tracy Walker [:tracy]]

This was a build issue where the file in question was checked in as a text file
instead of as binary.  It has been fixed.  

Henrik, please try reinstalling the build.  It should launch without that error.

marking fixed

Comment 5

[Tracy Walker [:tracy]]

hmnmm. sorry all. It's not fixed as expected

reopening

please reassign to shiva or jpatel

Comment 6

[Jan Carpenter]

Taking this one.

Comment 7

[Henrik Gemal]

also in 2003012210

Comment 8

[Matthew Kerr]

Also seen in nightly builds 20030119 through 20030122, on Windows XP SP1.

Comment 9

[Mel Reyes]

With the latest Moz/GRE builds the 1/22 ones, you'll get this sometimes on
startup and/or shutdown and (almost) always when you go to about:plugins.  Good
Luck ;)

Comment 10

[Skewer]

Temporary workaround (if this drives you insane): Shut down Mozilla and rename
components/CustomImages.dll -> AAACustomImages.dll (I chose the filename so it
would be easy to find later). The browser seems to work normally without it.
This will get rid of the error message until this bug is fixed.

Comment 11

[Skewer]

However, running the browser with this bug (whether or not you renamed
CustomImages.dll) will not be very useful. It appears that as a direct result of
this bug I am getting a crash 100% of the time at <http://www.buy.com/>.

Comment 12

[parish]

Opening CustomImages.dll in Dependency Walker (Win2000 Support Tools) reports:

Error: At least one file was not a 32-bit or 64-bit Windows module

and

No PE signature found. This file appears to be a 16-bit DOS module.

Could it be that the file was linked with the wrong flags?

Comment 13

[Justin Scott]

I am having this bug on 2003012308, Windows 2000, as well, but I am not getting
crashes on buy.com (have not noticed any problems as a result of this bug, other
than annoyance!)

Comment 14

[Kevin Neely]

Running 2003012215 on winXP, SP1.  I get this bug when starting, and the browser
crashes every time I go to http://bu.edu

Comment 15

[Bedeox]

Could someone just axe this file from build?

It doesn't seem to be needed.
If somebody knows what it's supposed to do, then answer.

I haven't had any crash with or without this file, no missing functionality,
nothing.

Comment 16

[Justin Scott]

Seems fixed (at least it doesn't complain anymore?) in 2003012315. I just
downloaded this build so I haven't tested much beyond a little bit of browsing
and closing/restarting Moz, but all seems good for this bug.

Comment 17

[Andreas Kunz]

I can confirm WFM with 2003012315.
Earlier that alert reliably came up on startup and when entering 'about:profiles'. 
Now it doesn't.

Comment 18

[James Ross]

Using 2003012315, CustomImages.dll isn't there (so no error about that), but
instead I get a fatal exception.

According to Delphi 7, the exception is occuring in "zlib.inflate_blocks", where
it's trying to read memory address 0xFFFFFFF1.

Comment 19

[Jari Ahonen]

Build 2003012315 works for me (as in it does not crash) but I am missing some
icons in mail client. Maybe these are in the missing DLL file ?

Steps to reproduce:
- Open mailnews
- Click on an account name on the folder list window. Don't select a folder but
an account.
- You should get a page that has options for the account like "read messages",
"settings" etc. but instead you get a blank page.

Comment 20

[Jason Bassford]

> instead I get a fatal exception

Same here.  Finally, the Win32 stub installer has been fixed (bug 190309), and I
can actually install Mozilla again, but launching it just produces this error. 
Is the fatal error related to this bug?

Comment 21

[James Ross]

Jason: I think I've found the bug you've got (and I've got) - bug 190460. I
think it's unrelated to this bug.

Comment 22

[Jason Bassford]

Cheers.

Comment 23

[Garfield Chong]

In addition, mozilla won't load webpages and or not respond to some links.
Talkback also not working and was not triggered.
In the latest build 20030123 onwards, all downloads not working and download
manager does not appear.
Also it also causes some strange high cpu load (100% to itself or to zonealarm)
causing the system to hang most of the time.
Nothing to do with build appending, cos i del everyting and reinstall for a few
times and nothing solved.
i will now 1.3a until this bug is fixed completely

Comment 24

[Owen Marshall (Not reading bugmail)]

Can we _please_ keep this bug focused towards the "Bad Image" error. There are
several other new bugs that are showing up as topcrash. Look at 190459, 190000,
190001, 190460, 189068 and many others. Look at the bottom of the list here:

http://bugzilla.mozilla.org/buglist.cgi?keywords=topcrash&order=bugs.bug_id

This isn't the only crash bug out there. Don't post "Also, feature foo dosen't
work!" unless you can prove the problem is caused by this bug.

QA --> chofmann (default Talkback QA)

Comment 25

[Skewer]

Checked with builds 2003012315, 2003012508:

Neither gives me the error message about CustomImages.dll nor do I experience
the related buy.com crash.

Marking FIXED. Please report any other issues in a new bug.

Comment 26

[Matthias Versen [:Matti]]

NOT FIXED since no patch is attached

Comment 27

[Matthias Versen [:Matti]]

-> wfm

Comment 28

[Matthias Versen [:Matti]]

*** Bug 190870 has been marked as a duplicate of this bug. ***

Comment 29

[Henrik Gemal]

v wfm

Comment 30

[Owen Marshall (Not reading bugmail)]

janc, jpatel, et al.

I still see this bug in 2003012908. I am not reopening, as it is seen with
sloppy install behavior (installing the nightly build over a previously
installed nightly). Without clobbering my old directory, however, I can
reproduce this error on "about:plugins" and during the install of a plugin
approximately 100% of the time.

Will this be a problem for any user who did _not_ install inside the "totally
horked nightly" window (say, Jan 21 to Jan 25) and who did _not_ install to a
fresh directory?

Just curious. If the answer to that question is a "no", I guess this isn't a
problem. If it is a "yes"...

Comment 31

[Jay Patel [:jay]]

Owen:  The answer is NO.  If you never installed a build that included the
CustomImages.dll, then you will not see this problem.  We backed out the changes
that added that file to the install...and are currently working on fixing it. 
Just wipe out your old installation and do a clean install.  The problem was
with the actuall CustomImages.dll file...and if you don't delete the entire
components dir, the file will remain on your system and cause problems.