I napped out last night with the machine running.
10/4-38, Photoshop, Saverlab and Itunes were open.
Only sites open were Verizon webmail, and a Lowes shopping cart.
10/4-38 was running just fine since I installed it a few hours earlier.
Woke up a few hours later to hear the fans running full blast and a frozen screen with what looked like Console data superimposed over everything.
Last line was Kernal something...
I should have taken a photo of the screen!
I rebooted and relaunched 10/4-38 alone.
Visited Verizon Webmail and got another freezeup.
Force quit, rebooted, got it again.
Switched back to 10/4-31, runs OK.
Then I relauncched 10/4-38 and it's working OK so far.
( I'm making this entry from it )
Frank, although I sympathize, without some steps to reproduce it
reliably on a test system I don't have any suggestions for you.
This message is being typed on a 1GHz iMac G4, and I use a Quad
G5 daily, and neither have demonstrated any similar issues. Please
also be aware that a beta test always occurs before jumping to the
next version, and no similar issues were reported.
However, if you keep getting kernel panics (like you reported in comment 1) and now app crashes I would suspect a hardware problem. This is definitely not normal, and TFF is most likely not the cause. Maybe it's the app that triggers it because it's uses a lot of RAM and other resources. But there must be an underlying issue.
The first thing I'd do is the full Apple Hardware Test (it's on the install DVD for your PowerBook). Then a check of the startup volume using Disk Utility or fsck -fy when the Mac is started in single user mode. Also remove half of the installed RAM, then swap it for the other half to see if one of the RAM modules is failing or the modules are incorrectly seated.
So much for hardware. There's a lot you can do on the software side, e.g. resetting TFF, running TFF with a new OS X user, removing system haxies, re-installing the OS etc. But first make sure your hardware is ok.
Thanks Chris for the link. I'll give 31.8 a shot and see if it makes a difference.
I wasn't the person who reported a "kernel problem" in comment 1... I've been happy with the access tenfourfox has given me with my older computer, and thanks for that. It's just the recent 38.02 that is giving me some trouble. Let's hope for the best. Thanks again.
Mike, I would still advise a hardware check. 38.2 does work your
system much harder than 31 does to achieve its current levels of
performance. You should also make sure you're not using things like
haxies or other low-level system add-ons, as Chris suggested, as
these can unpredictably interfere.
Cameron/Chris: I'm also throwing my hat into this thread, as I reported on the other thread about 38.2 being "slow" . . . today, just trying to get a Yahoo email to open, was not working after several minutes. I tried to click on another tab to get back to Gmail, wouldn't respond . . . then after clicking on Yahoo links to try to get something to happen . . . an "unresponsive script" error window dropped down . . . clicking on "stop script" did nothing . . . essentially TFF was frozen . . . error window would not relinquish "control" . . . Apple menu was non-responsive . . . tried to FQ, also un-responsive. Then it sounded like the machine powered down, screen went black . . . I hit the space bar and it "woke up" . . . then I could use key board to FQ TFF . . . . I have reverted to 31-8. This is PM Sawtooth running 10.4.11 TFF 7400. Let me know when 38-3 or -4 is ready for testing, sorry this one ain't working.
I'm typing this in 31-8 and, it's more or less fine.
I don't mean to be rude, but I'm not working on any such "fix"
for 38.3. None of the issues you report have ever turned up on any
of the test systems.
If you'd like to try to figure it out, and possibly consider the
possibility it's something on your machine that's marginal and that
38.2 is stressing out, we'll try to help you. But if you're waiting
for a "fix" for those problems, as of this moment unless whatever
underlying cause resolves itself, it's not going to happen. You are
of course welcome to use 31.8 for as long as it serves you.
I don't mean to be rude . . . either, but you can see that several other people on this thread, and I reported a problem on another thread that someone else started, so that would indicate that your testing might not be "thorough." It's up to you, right now I'm in ToriOS FF and . . . it ain't lightning, but it's working and no wacky "crashes" . . . .
You can see that over the years I've been using TFF I've reported a few problems and gone through the drill with you or Chris to help work it out. That would help me, but also to help you guys keep TFF a viable browser for PPC. In the past issues I might have tried rolling back one time, usually the problem "got fixed" and I was able to "keep up" . . . this is now such a problem that unfortunately it renders your fine browser not useable as it is. Perhaps I could try to download it again, but, indeed 31-8 is working; I have done my due diligence by reporting that there are problems with 38-2. But, as past behavior is repeating I won't hold my breath, I'm "exhaling."
Your "bedside manner" continues to be less than professional. I've taken my time to report that I share problems that others are apparently having with 38-2, to help you with your project, and this is your very typical response . . . "rude" to use your parlance. Why don't you grow up and realize that people are trying to help you, by using this forum to share problems. By reporting the problem I'm indicating that I am willing to participate in the process, but, it is very tired when each time there is an issue you act like it's a hardware problem. It IS a hardware problem for those of us trying to keep PPC machines going . . . that IS the problem, and TFF ***offered*** a way to help PPC users keep going. I mentioned ToriOS as a way of letting you know that the problem is ***not reproduced*** outside of 38-2. You can do what you want with it; I'm back in 31.8 until something else comes along in PPC. If you want to start over and work with me, I'm here--like I said, not holding my breath because you appear to not have the capacity to understand anything other than your own brilliance.
What is the difference between Resetting my Profile and Refreshing TenFourFox?
I've also been having some odd experiences with the browser since this last update, but I'll take first the path of (more or less) "least resistance", in trying to isolate and fix the problem. I will add that even running 38.2 with all add-ons disabled, the browser still locked up. I've saved some screenshots if it later seems worth sending them your way. I'm on G5 11,2.
I asked your question over on another forum and got this response:
"The refresh (previously known as reset) firefox feature in newer FF is
basically creating a new profile and importing select items from the old
profile over. I guess with the move to the 38.x codebase we've inherited
the reset feature.
Creating a new profile by hand is old school, yo."