Closed
Bug 105946
Opened 25 years ago
Closed 23 years ago
screen turns completely black when using mozilla
Categories
(SeaMonkey :: General, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
mozilla1.5alpha
People
(Reporter: quan_tony, Assigned: sfraser_bugs)
References
Details
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Macintosh; U; PPC; en-US; rv:0.9.5) Gecko/20011011
BuildID: 2001101117
when using mozilla, the screen occasionally turns completely black. i'm unable
to use mozilla or any other mac applications after that point and must reboot to
get a normal desktop display again. Moving the mouse, clicking, et cetera have
no effect
Reproducible: Sometimes
Steps to Reproduce:
1. browse a random selection of pages with mozilla
2. screen turns completely black
3.
Actual Results: screen turns black, unable to interact with mozilla or any
other mac applications after that point
Expected Results: mozilla should continue displaying normally
Reporter, that's a very odd problem. I've been running the same build as you,
0.9.5, without any such problems.
What's your hardware configuration? (CPU, Video card)
Have you tried booting under the "Mac OS 9 (All)" extension set?
Comment 2•25 years ago
|
||
tquan@spamcop.net - can we please have some more information, as requested in
the previous comment?
Gerv
system is a power computing power wave 604, with an ATI video card. Changing
the extension set to the default set as suggested has no effect (the problem
still happens eventually)
Comment 4•24 years ago
|
||
What do you have to do after the 'screen turns black'?
force restart? Turn completely off, then back on?
It almost sounds like a hardware problem, something starting to fail.
Does this happen 'eventually' with other applications?
Try leaving the machine on overnight running something else.
If it happens eventually with any app left in the foreground,
then I predict your video card is failing
and/or if the screen flickers a little more
than it used to, then it's probably
the transformer on your MonitorCRT.
after this happens, you can't see anything on the screen, so your only choices
are to use the hardware reset switch, or power off and on.
this problem only happens when mozilla is running. I've run my mac for days
with other applications and it never occurs unless mozilla is running.
BTW, when this occurs, the screen is not completely black--it is black except
for the outline of the mouse pointer. so I don't think it's the kind of
hardware problem you describe.
Comment 6•24 years ago
|
||
bizarre!
When the screen goes black, yet you can still see the highlight edge of the
cursor's arrow...
Can you move the cursor, or is the machine locked-up?
Meanwhile
Let's fill in the Profile,
What version of MacOS9 are you running?
How Much RAM hardware, and what is
your virtual Memory setting?
How much free space on the 'blessed' system folder volume?
(macs need at least 100mb free on the startup volume or they get fussy)
Comment 7•24 years ago
|
||
any mac folks know what to do with this bug?
| Assignee | ||
Comment 8•24 years ago
|
||
Sounds like bug 104781.
| Reporter | ||
Comment 10•24 years ago
|
||
I don't see the problem in 0.9.6. Something has changed enough to make it go
away it appears. Looks like the bug can be closed...
Comment 11•24 years ago
|
||
Resolving WorksForMe per Reporter. tquan, should you encounter this problem
again in the future, please reopen this bug.
Status: UNCONFIRMED → RESOLVED
Closed: 24 years ago
Resolution: --- → WORKSFORME
Comment 12•24 years ago
|
||
I'm seeing the same problem, with 0.9.6, so I'd like to re-open the bug.
I didn't see the problem with 0.9.5.
I'm using a Power Computing PowerWave 604/150. (I know this is slower than the
recommended configuration for Mozilla. Mozilla is slightly sluggish, but still
usable, except when this bug triggers.) I'm pretty sure I've got an ATI
graphics card, and I'm running MacOS 9.0. All disks have a reasonable amount of
disk space free. Mozilla is running from the startup disk.
Generally, after browsing a few pages with Mozilla 0.9.6, the screen goes
completely black, except that the mouse pointer is still visible.
The mouse pointer still moves normally in response to the mouse, and it changes
its shape (arrow, I-beam, etc.) as I'd expect it to as it moves around the
screen.
The keyboard also seems to be working, at least insofar as I get significant
disk action after hitting command-Q, of the sort I'd expect for quitting
Mozilla.
I wasn't able to sucessfully mouse around to execute any menu commands with any
visible effect. I'm not sure if this was because the commands weren't working,
or because I wasn't able to position the cursor successfully on anything with an
obvious effect. (I was trying to hit "restart" or "shut down" in the Finder,
though of course I'm not sure that the Finder ended up being the top application
after quitting Mozilla.)
I have to power-cycle the computer to get it back.
I hope this information is helpful. My guess would be that this *is* related to
bug 104781, and somehow my color map is getting set to all-black?
Status: RESOLVED → UNCONFIRMED
Resolution: WORKSFORME → ---
| Assignee | ||
Comment 13•24 years ago
|
||
Mine
Assignee: asa → sfraser
Status: UNCONFIRMED → NEW
Ever confirmed: true
Comment 14•24 years ago
|
||
| Assignee | ||
Comment 16•24 years ago
|
||
Should be fixed by fix for bug 113480.
Status: ASSIGNED → RESOLVED
Closed: 24 years ago → 24 years ago
Resolution: --- → FIXED
Comment 17•24 years ago
|
||
Still happening for me with Mozilla 0.9.8. Same setup as before.
With 0.9.7 it happened after browsing only 3 or 4 pages; now it didn't happen
for half an hour or so. So that's progress...
Is there anything I could do to either a) get my screen back, or b) try to debug
what's going on, that would help diagnose the problem?
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Comment 18•24 years ago
|
||
Another interesting point -- I don't know if this will be useful or relevant,
but it's interesting.
After the bug triggered the latest time, I blindly changed my screen depth (I
think to 8-bit black and white) from the control strip, in hopes that it would
restore things. It didn't, but it did change the whole screen to *white*,
instead of bl
Comment 19•24 years ago
|
||
(Somehow that got truncated.)
Another interesting point -- I don't know if this will be useful or relevant,
but it's interesting.
After the bug triggered the latest time, I blindly changed my screen depth (I
think to 8-bit black and white) from the control strip, in hopes that it would
restore things. It didn't, but it did change the whole screen to *white*,
instead of black.
Maybe this gives useful information to figure out what's going on?
Also, another point which I sort of mentioned earlier, but I can confirm now,
and which may be useful. I'm definitely able to quit from Mozilla after the bug
triggers, but the symptom persists. So something global is getting smashe
Comment 20•24 years ago
|
||
(I don't know what's happening there ... maybe a new bugzilla bug? Sorry for
spamming your e-mail boxes.)
"...is getting smashed."
Another note, in comparison with bug 113480. This is *not* begin triggered by
opening a new window. I'm just doing ordinary page-to-page browsing, in a
single window.
It's always triggered when I've moved to a new page, I'm pretty sure. I don't
remember if it ever happened as a result of hitting "back"; it's definitely
happened after I clicked on a link. I've always been actively using Mozilla,
though.
With 0.9.7, it triggered once when I was manipulating the Preferences window;
this hasn't happened with 0.9.
| Assignee | ||
Comment 21•24 years ago
|
||
There's a slim chance this may be caused by double delete bug 124517. If that's
the case, then this bug should never happen as long as mozilla doesn't throw up
any modal dialogs (including the profile picker).
Comment 22•24 years ago
|
||
No, I don't believe I ever had any modal dialogs thrown up during the crashing
sessions. (Certainly not during all of them.) I only have a single profile
configured.
| Assignee | ||
Comment 23•24 years ago
|
||
Assigning to later milestone, since away on sabbatical.
Target Milestone: --- → mozilla1.2alpha
Comment 24•23 years ago
|
||
*** Bug 132886 has been marked as a duplicate of this bug. ***
Comment 25•23 years ago
|
||
Hi,
I can confirm everything Jonathan Lennox wrote for Mozilla 0.9.x and for:
(Mozilla/5.0 (Macintosh; U; PPC; en-US; rv:1.2.1) Gecko/20021130,
Now and then the screens gets dark, while the mouse pointer stays visible (or
its outline). That really just happens when I do "normal" surfing with Mozilla,
and may occur after several hours or after a few minutes.
Keyboard input seems to be still active, but I have to wait for the next
blackout to confirm that.
I use an old G3-upgraded-PPC 7500@233MHz, 224MB RAM and two internal HDs (2/4
GB) with an "ATI Xclaim GA" (an old mach64-based videoboard, 4 MB VRAM) and
MacOS 9.1.
I remember that I got the dark screen more often before I replaced the PPC7500's
original CPU-card (601@100MHz) by the upgrade-card. But then Mozilla wasn't
sometimes starting at all, displaying the startup-screen forever, but that's
probably another story ....
I had used Mozilla on an even more ancient G3-upgraded PPC 6100 before (with a
4MB HPV-Videocard in its PDS-Slot, MacOS 8.6 and 9.0.4). I had never got any
similar behaviour on that PPC 6100.
Best Regards,
Markus
Comment 26•23 years ago
|
||
*** Bug 177159 has been marked as a duplicate of this bug. ***
| Assignee | ||
Updated•23 years ago
|
Target Milestone: mozilla1.2alpha → mozilla1.5alpha
| Assignee | ||
Comment 27•23 years ago
|
||
Mac OS 9 is no longer supported.
Status: REOPENED → RESOLVED
Closed: 24 years ago → 23 years ago
Resolution: --- → WONTFIX
Comment 28•23 years ago
|
||
Sad sad sad ... "MacOS 9 no longer supported", before everybody dumps his/her
fully functional, but not-MacOSX-capable PowerPC, he/she might
install Linux for PPC (Yellowdoglinux or DebianPPC), Mozilla > 1.3 runs great there.
For those who would like to keep MacOS9 and Mozilla 1.2.1: the screen blackening
error might be somehow related to ATI's mach64-based video cards (or its driver,
look at the other comments, ATI video hardware seems to be involved there, too),
because it never occured on my very ancient (but G3-upgraded) PPC6100, so trying
a different video card/onboardvideo could be a good idea.
Updated•21 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•