javascript breaks firefox and safari in 10.4.11?

installed update to osx, firefox crashed repeatedly trying to load eoff and livejournal, it loaded gmail okay though, which is weird because gmail is all about javascript.

but anyways, I turned javascript off, nothing changed, but when I restarted firefox obviously it did not crash on eoff.

safari crashed on whatever its homepage is set to be. I have no clue what that is.
Camino didn't care either way, which is what made me think it might be javascript.

but you know, I'm not for sure! I sent stu a couple of screen shots and maybe he saved them, but I dunno.

*talking about Macs never crashing* *hum* :tongue:

Sorry, haven't got a clue.

Install 10.5. :p

You could try downgrading Safari. I Googled a bit and it seems like people have gotten the same problem quite a lot. Unfortunately it seems that each person fixed it differently. Try rebooting, disabling RSS, reapplying the update, applying this update (if that's not what you already did and if you have a PPC processor :p) or disabling/uninstalling PicLens.

Yeah, install 10.5. :p

I don't feel like buying it! or pirating it!

I don't use safari, mike. I just opened it to make sure it wasn't a just-firefox thing.

What other programs were running when Firefox/Safari were running?

Maybe there was a conflict?

the same ones as always! finder kvirc adium and quicksilver.

It's weird. I reenabled javascript and it decided not to crash anymore. . .so far. WHATEVER YOU GUYS JUST BE WEIRD.

here's one of the error messages plus terminal debug window from when safari decided to take a break.
http://www.snowy-day.net/stuff/safaricrash.png

SnowCat: Rubah have you tried completely removing and re-installing Firefox?
SnowCat: As according to the terminal window that is the issue...

no I haven't, do you mean reinstall safari? x.x;

No I meant re-install Firefox as that's what OSX was referencing when the crash occurred.

By that terminal output, it's trying to access memory outside of the base and limit registers assigned to Safari. That pretty much means that when you started Safari, it was allocated a chunk of memory and then tried to access some memory address outside of that chunk. It crashes because the OS can't allow that to happen, since Safari could be haxoring any piece of data that needs to remain in memory.

It could be something to do with that /Users/rubahness/375 file. If it tried to read a specific number of bytes from the file and made an explicit memory reference based upon that. Of course it's probably not that. :p

I don't know how to fix whatever was causing your problem though. :p

well, see, there is no file there! (not even a hidden one)

It could be that whatever process is trying to create that file doesn't have permission to create it. If it happens again, try doing this at a terminal:

Code:

---

touch /Users/rubahness/375 && chmod 755 /Users/rubahness/375

---

or try executing the offending browser as root. If either of those work you have a permissions problem. :p

it started it up again >:[

terminal didn't really say anything one way or another about that snippit mikeface:o

Why did no-one take me seriously when I said re-install firefox?

What's the output of this code?

Code:

---

ls -l /Users/rubahness/375

---

Did you try executing the browser as superuser?

Code:

---

su -c 'safari http://www.eyesonff.com'

---

-rwxr-xr-x 1 rubahnes rubahnes 0 Nov 20 01:14 /Users/rubahness/375

it wasn't there yesterday :O

it said 'sorry' on that mike.

baloki, we're fixing safari first :p

I suspect Safari is crashing because of a problem with Firefox and it's alterations to your java plugin.

frankly I think it was the sneak update to safari 3 included in 10.4.11!

Can you post a log of the error? Like a full stack trace? I presume you can get one by clicking "Report" when it happens. I'd like to see the other threads that are dying and the reasons. :p

Edit: I found this. It suggests that SafariButtons is the culprit. It also suggests that you need to run the uninstaller rather than deleting the plist.

Edit 2: You can get the uninstaller here :p