Comments on: 2005-11-11 Branch respin (Firefox 1.5 RC3)

By: Hank Roberts

Hank Roberts — Thu, 01 Dec 2005 16:18:54 +0000

A thought –

I often have both Firefox and Camino
open at the same time — could this cause a problem with TalkBack working?

(Why two browsers at once, you may ask? Camino is much faster on my G3/900mhz Powerbook — with it, I can look at several pages I like to check, while Firefox is working at loading a different site. But Camino doesn’t have AdBlock, Aardvark, or NoScript, so I don’t use it on pages I don’t already know I can stand. It has a less capable crapfilter (or one I don’t yet understand well enough to take proper advantabe of).)

By: Hank Roberts

Hank Roberts — Mon, 28 Nov 2005 04:28:34 +0000

I’m not sure if this is a “stack trace” –
OS Version: 10.3.9 (Build 7W98)
… Command: firefox-bin
Path: /Users/hank/Applications/Firefox.app/Contents/MacOS/firefox-bin
Version: 1.5 (1.5)
PID: 22966
Thread: 0

Exception: EXC_BAD_ACCESS (0×0001)
Codes: KERN_PROTECTION_FAILURE (0×0002) at 0×00000000

Thread 0 Crashed:
0 > 0×00000000 0 + 0
1 libmozjs.dylib 0×06003544 JS_InitClass + 0×190
2 libmozjs.dylib 0×06040004 js_InitObjectClass + 0×98
3 libmozjs.dylib 0×06002464 JS_SetGlobalObject + 0×118
4 libmozjs.dylib 0×06002a10 JS_ResolveStandardClass + 0×270
5 org.mozilla.firefox 0×000866c4 nsXPConnect::InitClasses(JSContext*, JSObject*) + 0xf4
eam*) + 0×68
…
34 org.mozilla.firefox 0×00693f18 nsMacMessagePump::GetEvent(EventRecord&) + 0×74
35 org.mozilla.firefox 0×00693e74 nsMacMessagePump::DoMessagePump() + 0×30
36 org.mozilla.firefox 0×00300014 nsAppShell::Run() + 0×38
37 org.mozilla.firefox 0×0039fe3c nsAppStartup::Run() + 0×3c
38 org.mozilla.firefox 0×00014338 XRE_main + 0xed0
39 org.mozilla.firefox 0×0000f6a8 start + 0×1b0
40 org.mozilla.firefox 0×0000f528 start + 0×30
(that’s the end of Thread 0) …

Whole thing available to anyone who wants it, but I gather these usually aren’t helpful. If there’s any particular chunk that would indicate why Talkback failed to notice Firefox crashing, I’d guess that’s what’s more important than the crash itself.

By: Jesse Ruderman

Jesse Ruderman — Mon, 28 Nov 2005 01:05:18 +0000

You can’t manually add an OSX crash log to Talkback, but you can paste the first few lines of a stack trace here, or file a bug, or search Bugzilla or Talkback using the first line of the stack trace. If you end up filing a new bug, paste the first few lines of the stack trace into the bug report and upload the entire crash report as a text/plain attachment.

By: Hank Roberts

Hank Roberts — Sun, 27 Nov 2005 17:01:02 +0000

I just had an unexpected quit with Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8) Gecko/20051126 Firefox/1.5

Talkback was open — and didn’t record anything. It didn’t quit, just missed the event completely.

I have an OSX crash log for the event — is there a way to manually put it into Talkback, that I’m missing here?

By: Hank Roberts

Hank Roberts — Sat, 26 Nov 2005 17:00:35 +0000

Daniel DeVaney — Which “this build” were using when your system got screwed up?
What OS/platform, and what build date?

By: peakshysteria

peakshysteria — Sat, 26 Nov 2005 15:02:27 +0000

For those complaining over high memory loss, check this out; http://primates.ximian.com/~federico/news-2005-11.html#moz-images

Its a proposal for linux thou……Not interesting for myself since my FF mem. is ok. But DeVaney i’m getting back to you later tonight (since my OS also is acting up…)……….Been nice to now something about your themes and extensions an FF vers offcourse. And do you run 64Bit system (linux or Win)??