275164 - Crash apparently caused by Google Suggest Extension

Status: RESOLVED WORKSFORME

(Firefox :: Search, defect)

Description

[John Liebson]

Using Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a6) Gecko/20041215
Firefox/1.0+, installer version, with WindowsXP Home.

I installed the Google Suggest plugin and the Google Suggest extension. Three
times, when using the extension, Firefox crashed while waiting for Google to
provide the suggestion list.

I don't have a Talkback number, as Talkback does not work for me, sorry.

Comment 1

[Bill Mason]

Crashes caused by an extension should be reported to the extension author, not
as browser bugs.

Comment 2

[John Liebson]

In reply to Comment #1, it was suggested to me by an active extension/program
participant on MozillaZine, after I posted a bug report in the thread started by
the extension author on MozillaZine, that I post a bug report here. That comment
on MozillaZine stated that the person making it could not see that the extension
was doing anything that should cause the crashes and, thus, he felt that this
might be something within Firefox rather than in the extension.

I'm quite incapable of knowing if that MozillaZine report is accurate, hence my
original report on Bugzilla, to alert FF programmers to what might be a browser
problem. If it is not a FF problem, so be it; I've done what was suggested, and
I'm content to let the matter rest should it be so determined.

Comment 3

[Mike Connor [:mconnor]]

If we crash because of the extension code, that's bad.  If the plugin crashes
and takes us down, we can't do as much.

Still, lets get a talkback ID somehow and see where we're dying. (If you don't
have talkback, reinstall with the installer and do a custom install.  We only
install talkback on about 20% of builds to cut down on talkback load.)

Comment 4

[Phil Ringnalda (:philor)]

And since it's not a plugin-plugin, just a Mycroft search plugin, it's just
plain bad.

Talkbalk may not be as non-working as you think, if what it does is tries to
send, then mutters to itself, and winds up loudly annoucing that you should
check your proxy settings: quite often, those are actually sent, and it's just
the confirmation that doesn't get back to you. You can add something in the
comment field you can search for (like the bug number), and then check at
http://talkback-public.mozilla.org/ for the TB ID.

Comment 5

[John Liebson]

In reply to comments #3 & #4:

1. Thanks for being willing to reopen this.

2. I've had to remove the trunk release: There was a bug reported that this
release would not print, yet I was able to print using the release. Sadly, two
days later, even with a brand-new profile, I was unable to print, so I
reinstalled the release version.

3. As to Talkback not working: I've been trying to use it for a year, I know
what it does, and I also know that I--along with many others--am unable to get
it to actually connect to the server and deliver the information. Not once have
I seen a single message about proxy settings; all I get, with the exception of
the one time it worked, is several attempts to connect, each one of which gives
the error message that it is unable to connect. I finally just remove the crash
report from Talkback. (There are many similar reports on MozillaZine.)

So, again, I appreciate the willingness to reconsider the issue. Unfortunately,
at this time, I'm unable to contribute anything further. Once the non-printing
bug is fixed in Firefox's trunk releases, I'll reinstall it, along with
Talkback, and see what I can do.

(Oh, I just remembered that once, when I was having problems with another
extension that was causing Thunderbird [?] to crash, I was able to copy the data
that Talkback accumulated and email that to whomever it was that requested it.
Perhaps doing that with this extension would be helpful?)

Comment 6

[John Liebson]

As there's been nothing about this for some time, and as I no longer use the
extension, I'm going to consider this a now-null issue. I'll use "works for me,"
as a guess as to what the closed status should be. (If someone wants to change
that, it would be okay by me.)

Comment 7

[timeless]

if you're still interested in tracking this down, we can find a route that involves a non talkback build for which symbols are available.