I found an old T4F 38.10.0 version on my HD and devoted most of an afternoon on Facebook to annoy mindless humans I've never met with my pretense of exceptional wisdom while clicking on the superfluous links they've shared with the world to demonstrate their own "special" vapidity (it was only for testing purposes, mind you...)
That's a stable build - no crashes yet; hardware is fine.
I'm sorry, I cannot reproduce these crashes on Facebook at all. I use FB a lot, with TFF 45.x, of course. The last time it crashed according to my crash logs was in August 2016. We haven't had reports from other users about FB crashes with TFF 45.6 so far.
Can you describe in some more detail what you do on FB that makes the browser crash? I.e., what do you click on or which action you take that makes it crash reliably? From what you described so far, it seems very hard or impossible to fix the problem.
Thanks for the quick reply.
I'll relaunch 45.6 and try to note if there's anything in particular that causes crashing. It seemed random.
If this helps: over the years, T4F versions have occasionally (rarely) crashed on me, but each time a window would open advising me that it had "unexpectedly quit" with options to relaunch... this version simply vanishes, with no crash window, though system and other open apps are just fine.
FB and many web sites linked to posts busily load extraneous content (ads!) on the side; I suspected something there might have been the problem? Despite 4 quits in a few hours under 45.6, 38.10 hasn't quit at all in two days of use...
HOWEVER - as several cap fails (and replacements) were in the RAM section, and machine's initial fail symptoms suggested RAM failure, I was (am still) concerned that:
- a block of RAM may have been damaged, causing crashes when accessed by an app with high memory load.
- or that my soldering skills are off, and there's an intermittent cold joint there.
I have seen one kernel panic today (I think it was related to RAM) while I was streaming music and using T4F 38.10. Meanwhile, I'm looking for some memory and processor intensive things to put some stress on the machine to rule out hardware issues.
You could also try Apple's hardware test on the install CDs or DVD that came with the Mac originally. The RAM test takes ages but (from my limited experience) seems to find bad RAM modules pretty reliably. It also tests for motherboard integrity and other stuff that could cause your problems.
Despite no crash window, T4F logs were actually updated. Problems with both app and kp appear memory-related, but I've been unable to reliably reproduce a crash with T4F 38.10 running concurrent with any other RAM-intensive apps.
Bought used, so don't have cds (i've been recloning drives for ... ever).
I'm going with a "gut instinct," big dose of hope, and ordered new RAM - pretty cheap these days. I noticed the pair are different manufacture, maybe effected by cap damage differently? I'll repost once it's in and I've tested again.
Meanwhile, I have two other long-dead ppc imacs and a new set of tools ... thinking of taking a crack at them. Thanks, again, for the programming support that makes it a worthwhile effort!