X
點擊此處開啟此網站的行動版。

技術支援討論區

I live in Mountain View. How do I contact a live person?

已張貼

I can bring my Macbook Pro running Firefox 22.0 on Snow Leopard to your offices on Castro Street. That would be the fastest way to demonstrate the "crash" that consistently occurs. I've been a Systems Programmer at Stanford for over 41 years, and I've written code for which I've received Copyright protection. NOTE: I'm sending this from another computer running Firefox 3.6.28, which is NOT the version that's crashing. Contact me via the mailto-link on my Google Home Page at <https://sites.google.com/site/dickguertin/home> .

I can bring my Macbook Pro running Firefox 22.0 on Snow Leopard to your offices on Castro Street. That would be the fastest way to demonstrate the "crash" that consistently occurs. I've been a Systems Programmer at Stanford for over 41 years, and I've written code for which I've received Copyright protection. NOTE: I'm sending this from another computer running Firefox 3.6.28, which is NOT the version that's crashing. Contact me via the mailto-link on my Google Home Page at <https://sites.google.com/site/dickguertin/home> .

被選擇的解決方法

john99, I didn't think I gave my email address in the posts. I did give my public Google Home Page web-address which would require someone take that route to email me. And I can always "filter" email into oblivion. I don't mind if people look at what I've been doing for the past 50 years.

As for 3.6.8, I'm stuck there on an Intel-based Mac-Mini Core Duo running OSX 10.4.11. I have too much invested in that system to abandon it. However, I'm also running OSX 10.6.8 on a Macbook Pro with Core 2 Duo, and there I try to run (almost) the latest that system will support. I'm unwilling to go to 10.7.x or higher because I'd loose a lot of Rosetta interpreted PPC code. I'm not a rich person, and don't have deep pockets.

Thanks for your advice. If you think my Web-address should be removed, I can edit the post to delete it.

從原來的回覆中察看解決方案 1

額外的系統細節

已安裝的外掛程式

  • Gecko default plugin
  • Runs Java applets using the latest installed versions of Java. For more information: Java Embedding Plugin. Run version test: Java Information.
  • WebEx General Plugin Container Version 172
  • iPhoto6
  • Google Talk Browser Plugin
  • The Flip4Mac WMV Plugin allows you to view Windows Media content using QuickTime.
  • The Google Earth Plugin allows you to view 3D imagery and terrain in your web browser.
  • Shockwave Flash 10.3 r183
  • The QuickTime Plugin allows you to view a wide variety of multimedia content in web pages. For more information, visit the QuickTime Web site.

應用程式

  • User Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.4; en-US; rv:1.9.2.28) Gecko/20120306 Firefox/3.6.28

更多資訊

philipp
  • Top 25 Contributor
  • Moderator
5343 個解決方法 23599 個答案

hello dickguertin, most of us in the support forum are volunteers and scattered all around the world. if you could provide your latest few submitted crash reports, we might be able to help you this way - therefore please enter about:crashes into the location bar, copy the latest few report ids from there & paste them here into a forum reply...

i don't know how to get in contact with someone in mountain view in particular, but since most mozillians are rather nice & helpful you could test your luck and just stumble into mozilla's office. or try to reach out to the crash-kill team on irc beforehand: https://wiki.mozilla.org/CrashKill#Logistics

hello dickguertin, most of us in the support forum are volunteers and scattered all around the world. if you could provide your latest few submitted crash reports, we might be able to help you this way - therefore please enter '''about:crashes''' into the location bar, copy the latest few report ids from there & paste them here into a forum reply... i don't know how to get in contact with someone in mountain view in particular, but since most mozillians are rather nice & helpful you could test your luck and just stumble into mozilla's office. or try to reach out to the crash-kill team on irc beforehand: https://wiki.mozilla.org/CrashKill#Logistics

提出問題者

First, my thanks to philipp for responding. There were multiple crash reports, but I only sent one because they were all basically identical. the URL is:

https://crash-stats.mozilla.com/report/index/d5eda859-51e7-4b58-9a9b-e83442131130

What I was doing in Applescript looked like this:
set myapp to "Firefox"
tell application "System Events"
 	set the visible of every process to true
	delay 1
	set process_list to the name of every process whose visible is true
	delay 1
	set myexists to (process_list contains myapp)
end tell
if not myexists then
	tell application "Finder"
		launch my application myapp
	end tell
end if
set process_name to ""
tell application "System Events"
	try
		set process_name to name of my application myapp
	end try
end tell

etc... Not only does this last "set" command fail, Firefox crashes.

I believe I may have a workaround, and it's probably required because Applescript won't wait to communicate with Firefox without extensive "waiting" logic, doing things like "repeat until the application exists", and then "repeat until the front window is visible". Each of these repeat loops requires a "delay 1" and possibly a loop-counter to prevent infinite loops.

But, regardless, I wouldn't expect Firefox to crash if asked to do something before it's ready. (Sometimes I hate Applescript; sometimes I like it.)

Formatted - one method add an extra leading space on each line. Sorry no specific code format option available ~J99

First, my thanks to philipp for responding. There were multiple crash reports, but I only sent one because they were all basically identical. the URL is: https://crash-stats.mozilla.com/report/index/d5eda859-51e7-4b58-9a9b-e83442131130 What I was doing in Applescript looked like this: set myapp to "Firefox" tell application "System Events" set the visible of every process to true delay 1 set process_list to the name of every process whose visible is true delay 1 set myexists to (process_list contains myapp) end tell if not myexists then tell application "Finder" launch my application myapp end tell end if set process_name to "" tell application "System Events" try set process_name to name of my application myapp end try end tell etc... Not only does this last "set" command fail, Firefox crashes. I believe I may have a workaround, and it's probably required because Applescript won't wait to communicate with Firefox without extensive "waiting" logic, doing things like "repeat until the application exists", and then "repeat until the front window is visible". Each of these repeat loops requires a "delay 1" and possibly a loop-counter to prevent infinite loops. But, regardless, I wouldn't expect Firefox to crash if asked to do something before it's ready. (Sometimes I hate Applescript; sometimes I like it.) Formatted - one method add an extra leading space on each line. Sorry no specific code format option available ~J99

由 John99 於 修改

提出問題者

YIKES! I didn't expect my carefully formatted text to turn into paragraphs.

YIKES! I didn't expect my carefully formatted text to turn into paragraphs.

提出問題者

NOTE: The "Question Details" and "Tabs" DO NOT contain proper information. This problem is for Firefox 22.0 on Mac OSX 10.6.8. Unfortunately, I can't edit the data to make it right.

NOTE: The "Question Details" and "Tabs" DO NOT contain proper information. This problem is for Firefox 22.0 on Mac OSX 10.6.8. Unfortunately, I can't edit the data to make it right.
James
  • Top 25 Contributor
  • Moderator
1603 個解決方法 11348 個答案

Have you tried the current Firefox 25.0.1 from mozilla.org ?

Have you tried the current Firefox 25.0.1 from mozilla.org ?

提出問題者

James, NO, I have not, simply because I'm seeing postings of problems introduced in that version. I prefer to wait a few months for a "stable" version to be documented on the Web. THIS PROBLEM that I've posted has a work-around, but I reported it because products shouldn't crash as simply as this case. Hopefully, a future version will benefit from my report.

James, NO, I have not, simply because I'm seeing postings of problems introduced in that version. I prefer to wait a few months for a "stable" version to be documented on the Web. THIS PROBLEM that I've posted has a work-around, but I reported it because products shouldn't crash as simply as this case. Hopefully, a future version will benefit from my report.
philipp
  • Top 25 Contributor
  • Moderator
5343 個解決方法 23599 個答案

hey dick, there are reports of problems with each and every version of firefox - this is the nature of a support forum. each firefox version goes through months of testing and stabilizing until it hits the release track.

regarding the crash report you've provided, i fear i don't know enough to help out there, but i would re-suggest reaching out to the developers at the #crashkill irc channel and adding your information to the bug report for this crash signature: https://bugzilla.mozilla.org/show_bug.cgi?id=878440

hey dick, there are reports of problems with each and every version of firefox - this is the nature of a support forum. each firefox version goes through months of testing and stabilizing until it hits the release track. regarding the crash report you've provided, i fear i don't know enough to help out there, but i would re-suggest reaching out to the developers at the #crashkill [https://wiki.mozilla.org/IRC irc channel] and adding your information to the bug report for this crash signature: https://bugzilla.mozilla.org/show_bug.cgi?id=878440
James
  • Top 25 Contributor
  • Moderator
1603 個解決方法 11348 個答案

The old insecure Firefox 22.0 was released on June 25.0. If you went there they would have asked if you have same issue with the current stable release which is 25.0.1. There is is often a minority that says insert version has problems including with the Firefox 22.0 you have.

The Firefox 25.0.1 is a stable version. Things are not going to be fixed in 22.0 as it was made EOL when 23.0 came out then.

If you are looking for a version that has long term security and allowed stability fixes support then perhaps you could try the Firefox 24 ESR which is made for Enterprise users in mind as it will be supported until two releases after Firefox 31.0 which is what the ESR will be based on.

http://www.mozilla.org/en-US/firefox/organizations/all.html

The current 24.1.1esr is based on Firefox 24.0 Release and came out when Firefox 25.0.1 was released. The next 24esr will be 24.2.0 when Firefox 26.0 is released on December 10.

The old insecure Firefox 22.0 was released on June 25.0. If you went there they would have asked if you have same issue with the current stable release which is 25.0.1. There is is often a minority that says insert version has problems including with the Firefox 22.0 you have. The Firefox 25.0.1 is a stable version. Things are not going to be fixed in 22.0 as it was made EOL when 23.0 came out then. If you are looking for a version that has long term security and allowed stability fixes support then perhaps you could try the Firefox 24 ESR which is made for Enterprise users in mind as it will be supported until two releases after Firefox 31.0 which is what the ESR will be based on. http://www.mozilla.org/en-US/firefox/organizations/all.html The current 24.1.1esr is based on Firefox 24.0 Release and came out when Firefox 25.0.1 was released. The next 24esr will be 24.2.0 when Firefox 26.0 is released on December 10.
John99 971 個解決方法 13138 個答案

I made an attempt at formatting your post.

You mentioned earlier the Release not being tested. In fact they currently spend six weeks in each of Nightly, Aurora & Beta before moving to the Release. As James mentioned ESR is out longer and is supported with security updates, but officially Mozilla supports it only for corporate users. So anyone may currently install and test Fx 26, 27 & 28.

You could try dropping down to Fx17 esr Bug 878440 - crash in mozilla::dom::XULDocument::AddPrototypeSheets does not mention Fx17 as being affected and it could be outside the regression range.

Background info

Email address
Do you wish to leave that in your post or edit it out ?
Presumably as it relates to your website you are happy for it to be seen. IYou have not opted to publicly display that or your website in your profile in this forum. The forum is public and indexed by search engines.
Emails addresses need not be displayed because whilst logged in you may send or read Private Messages without your email address being disclosed.

I made an attempt at formatting your post. You mentioned earlier the Release not being tested. In fact they currently spend six weeks in each of Nightly, Aurora & Beta before moving to the Release. As James mentioned ESR is out longer and is supported with security updates, but officially Mozilla supports it only for corporate users. So anyone may currently install and test Fx 26, 27 & 28. You could try dropping down to Fx17 esr ''Bug 878440 - crash in mozilla::dom::XULDocument::AddPrototypeSheets'' does not mention Fx17 as being affected and it could be outside the regression range. Background info *https://wiki.mozilla.org/RapidRelease/Calendar * What does the Mozilla Firefox ESR life cycle look like? <br/>http://www.mozilla.org/en-US/firefox/organizations/faq/ *No need to mention Fx3.6 is outdated, but you may be interested in the security fixes / vulnerabilities https://www.mozilla.org/security/known-vulnerabilities/firefox.html Email address<br /> Do you wish to leave that in your post or edit it out ? <br />Presumably as it relates to your website you are happy for it to be seen. IYou have not opted to publicly display that or your website in your [/users/edit profile] in this forum. The forum is public and indexed by search engines.<br/> Emails addresses need not be displayed because whilst logged in you may send or read Private Messages without your email address being disclosed.

選擇的解決方法

john99, I didn't think I gave my email address in the posts. I did give my public Google Home Page web-address which would require someone take that route to email me. And I can always "filter" email into oblivion. I don't mind if people look at what I've been doing for the past 50 years.

As for 3.6.8, I'm stuck there on an Intel-based Mac-Mini Core Duo running OSX 10.4.11. I have too much invested in that system to abandon it. However, I'm also running OSX 10.6.8 on a Macbook Pro with Core 2 Duo, and there I try to run (almost) the latest that system will support. I'm unwilling to go to 10.7.x or higher because I'd loose a lot of Rosetta interpreted PPC code. I'm not a rich person, and don't have deep pockets.

Thanks for your advice. If you think my Web-address should be removed, I can edit the post to delete it.

john99, I didn't think I gave my email address in the posts. I did give my public Google Home Page web-address which would require someone take that route to email me. And I can always "filter" email into oblivion. I don't mind if people look at what I've been doing for the past 50 years. As for 3.6.8, I'm stuck there on an Intel-based Mac-Mini Core Duo running OSX 10.4.11. I have too much invested in that system to abandon it. However, I'm also running OSX 10.6.8 on a Macbook Pro with Core 2 Duo, and there I try to run (almost) the latest that system will support. I'm unwilling to go to 10.7.x or higher because I'd loose a lot of Rosetta interpreted PPC code. I'm not a rich person, and don't have deep pockets. Thanks for your advice. If you think my Web-address should be removed, I can edit the post to delete it.
John99 971 個解決方法 13138 個答案

OK it was more a question of whether you wished to and realised there's a facility to add the Website address and email to your profile.

I mentioned Fx17esr because it is still current as it overlaps with Fx24esr. It may have avoided the bug.

The OSX 10.4 runs into Firefox support EOL after Fx16, but I see you have another limit before Fx10.7

The Bug 878440 is very low in the frequency ratings.
You could vote on it and add your Crash ID.
(If indeed this is a Bug that affects you)
You could also even consider installing and running a current Fx version as an additional browser solely for Bug investigation. By adding a crash ID anyone triaging or assigned to the Bug may then take an opportunity to contact you if they are looking for Steps To Reproduce.

Or you could be proactive and find the regression range for the Bug. No need to manually install additional Fx. Instead install and use the test utility mozregression.

OK it was more a question of whether you wished to and realised there's a facility to add the Website address and email to your profile. I mentioned Fx17esr because it is still current as it overlaps with Fx24esr. It may have avoided the bug. The OSX 10.4 runs into Firefox support EOL after Fx16, but I see you have another limit before Fx10.7 * EOL article [[Firefox no longer works with Mac OS X 10.5]] The Bug 878440 is very low in the frequency ratings. <br /> You could vote on it and add your Crash ID. <br /> (If indeed this is a Bug that affects you)<br /> You could also even consider installing and running a current Fx version as an additional browser solely for Bug investigation. By adding a crash ID anyone triaging or assigned to the Bug may then take an opportunity to contact you if they are looking for Steps To Reproduce. Or you could be proactive and find the regression range for the Bug. No need to manually install additional Fx. Instead install and use the test utility mozregression. * http://mozilla.github.io/mozregression/

提出問題者

John99, so you're saying I could run Fx16 on my Mac-Mini if I upgraded the OS to an Intel-version of 10.5 (Leopard). I have a bootable backup disk from a former 10.5 system on my Macbook Pro. I'm going to try and boot from it on my Mac-Mini. If that works, I could clone that backup onto my Mac-Mini and install Fx16. I'll let you know what happens. [Of course, I'd have to make sure I capture important data from my Mac-Mini onto the backup before I clone.]

John99, so you're saying I could run Fx16 on my Mac-Mini if I upgraded the OS to an Intel-version of 10.5 (Leopard). I have a bootable backup disk from a former 10.5 system on my Macbook Pro. I'm going to try and boot from it on my Mac-Mini. If that works, I could clone that backup onto my Mac-Mini and install Fx16. I'll let you know what happens. [Of course, I'd have to make sure I capture important data from my Mac-Mini onto the backup before I clone.]
John99 971 個解決方法 13138 個答案

Dick,
I tend to use Linux and sometimes Windows but haven't used a Mac for decades, but my understanding is that:

Old Intel based Mac-Mini editing WRONG info see James'post under

Thanks for the correct info James.

Intel 10.4 (Tiger)' and 10.5(Leopard) may both already run Fx16 that is the last Fx version for themit. So there is no need to upgrade the Mac Mini OSX 10.4 as long as you do not try to go above Fx16 Only the Power PC machines were restricted to Fx3.6
Firefox no longer works with Mac OS X 10.4 or PowerPC processors

Intel Mackbook Pro OS X 10.6 (SnowLeopard)
That should for now support whatever Fx version you wish.

You are probably aware it is easy to install & run multiple versions of Firefox. (Although Not officially supported by Mozilla or this forum; however I am able to provide suitable links) For testing purposes you can install versions permanently, (& turn off the auto upgrades if older versions) of Firefox. Or you can semi automate it to install and uninstall on the fly if looking for regressions.

Dick, <br /> I tend to use Linux and sometimes Windows but haven't used a Mac for decades, but my understanding is that: <u>Old Intel based Mac-Mini</u> '''editing''' ''WRONG info see James'post under'' '''Thanks for the correct info James.''' <s>''Intel 10.4 (Tiger)''' and</s> 10.5(Leopard) may <s>both</s> already run '''Fx16''' that is the last Fx version for <s>them</s>''it''.<s> So there is no need to upgrade the Mac Mini OSX 10.4 as long as you do not try to go above Fx16 </s> <s>Only the Power PC machines were restricted to Fx3.6</s> <br /> [[Firefox no longer works with Mac OS X 10.4 or PowerPC processors]] <u>Intel Mackbook Pro OS X 10.6 (SnowLeopard)</u><br /> That should for now support whatever Fx version you wish. You are probably aware it is easy to install & run multiple versions of Firefox. (Although Not officially supported by Mozilla or this forum; however I am able to provide suitable links) For testing purposes you can install versions permanently, (& turn off the auto upgrades if older versions) of Firefox. Or you can semi automate it to install and uninstall on the fly if looking for regressions.

由 John99 於 修改

提出問題者

To everyone reading this topic: AMAZING! I just booted from a year old backup of a Macbook Pro Leopard system on my Mac-Mini. IT WORKS! I can now upgrade to Fx16 from Fx3. Thanks John99, I would never have known this was possible without your help. Dick.Guertin

To everyone reading this topic: AMAZING! I just booted from a year old backup of a Macbook Pro Leopard system on my Mac-Mini. IT WORKS! I can now upgrade to Fx16 from Fx3. Thanks John99, I would never have known this was possible without your help. Dick.Guertin
John99 971 個解決方法 13138 個答案

Glad to have helped, thanks for posting back.

Your initial question about the bug would be best stand a chance of being solved of course if you are able to run a supported version of Firefox on one of your machines.

Glad to have helped, thanks for posting back. Your initial question about the bug would be best stand a chance of being solved of course if you are able to run a supported version of Firefox on one of your machines.

提出問題者

John, I am running Fx22 on 10.6.8 (Snow Leopard) which is a supporting machine, and that's where the crash happened. I've stated several times that I'm using my 10.4.11 machine to communicate with the Forum about a crash that happened on 10.6.8 with Fx22. All the details are in this report:

https://bugzilla.mozilla.org/show_bug.cgi?id=878440

John, I am running Fx22 on 10.6.8 (Snow Leopard) which is a supporting machine, and that's where the crash happened. I've stated several times that I'm using my 10.4.11 machine to communicate with the Forum about a crash that happened on 10.6.8 with Fx22. All the details are in this report: https://bugzilla.mozilla.org/show_bug.cgi?id=878440
James
  • Top 25 Contributor
  • Moderator
1603 個解決方法 11348 個答案

John99, the Firefox 3.6.28 was the last to support the old Mac OSX 10.4 regardless whether it was PPC or Intel. As of Firefox 4.0 to 16.0 the minimum requirements was Mac OSX 10.5 and Intel. So the Firefox 16.0 you suggest will not work on OSX 10.4.

http://www.mozilla.org/en-US/firefox/4.0/system-requirements/


dickguertin, The supported version is Firefox 25.0.1 as Firefox 22.0 is End Of Life. Any issue you have in 22.0 is not going to be fixed in 22.0 and the fix will not be in a future release unless it is reproducible in current and can be fixed.

John99, the Firefox '''3.6.28''' was the last to support the old Mac OSX '''10.4''' regardless whether it was PPC or Intel. As of Firefox '''4.0''' to 16.0 the minimum requirements was Mac OSX 10.'''5''' and Intel. So the Firefox 16.0 you suggest will not work on OSX 10.4. http://www.mozilla.org/en-US/firefox/4.0/system-requirements/ dickguertin, The supported version is Firefox 25.0.1 as Firefox 22.0 is End Of Life. Any issue you have in 22.0 is not going to be fixed in 22.0 and the fix will not be in a future release unless it is reproducible in current and can be fixed.

由 James 於 修改

提出問題者

John99, so you've reversed course from your original statement: "Old Intel based Mac-Mini Intel 10.4 (Tiger) and 10.5(Leopard) may both already run Fx16. That is the last Fx version for them. So there is no need to upgrade the Mac Mini OSX 10.4 as long as you do not try to go above Fx16 Only the Power PC machines were restricted to Fx3.6 " My Mac-Mini is Intel, but you're now saying I do have to upgrade to 10.5 to run Fx16. That's the path I'm following.

John99, so you've reversed course from your original statement: "Old Intel based Mac-Mini Intel 10.4 (Tiger) and 10.5(Leopard) may both already run Fx16. That is the last Fx version for them. So there is no need to upgrade the Mac Mini OSX 10.4 as long as you do not try to go above Fx16 Only the Power PC machines were restricted to Fx3.6 " My Mac-Mini is Intel, but you're now saying I do have to upgrade to 10.5 to run Fx16. That's the path I'm following.
John99 971 個解決方法 13138 個答案

Yes sorry. James corrected the comment about OS X 10.4 and so you correctly upgraded.

Otherwise I think I was consistent. James's short summary above is best but my reasoning is

  • ESR support
    Firefox 17 esr on the FAQ calender is shown as not yet EOL for Firefox support, although Fx22 esr is released.
  • The bug report does not mention Fx17 as being affected, there is a possibility it is outside the regression range and not affected by the bug so is worth testing. I also think it could be worth commenting in the bug if a supported Fx17 esr is affected and you are able to give Steps To Reproduce . Fixes however will only be in later Releases, probably Fx 27 esr or later, unless possibly it is a security issue important enough to fix in a point release of the current Fx22 esr and will be dependent on the low priority bug even being reproduced and fixed.
  • Fx 3.6 support on Macs
    It was possible you were on on Fx3.6 because you thought later versions were not supported on OS X, they are are and James commented on that.
  • If you go to OS X 10.7.x as you said you may on the Mackbook pro
    then current mainline Releases or ESR Releases are useable. If nothing else you will be able to test these versions on your Mackbook pro. One way of doing that is by having multiple installs of Firefox. If the bug is fixed the fix probably would not get on to a Release prior to Fx28. You could test on the current release or better still on a Fx28 nightly,
Yes sorry. James corrected the comment about OS X 10.4 and so you correctly upgraded. Otherwise I think I was consistent. James's short summary above is best but my reasoning is * ESR support <br> Firefox 17 esr on the FAQ calender is shown as not yet EOL for Firefox support, although Fx22 esr is released. * The bug report does not mention Fx17 as being affected, there is a possibility it is outside the regression range and not affected by the bug so is worth testing. I also think it could be worth commenting in the bug if a supported Fx17 esr is affected and you are able to give Steps To Reproduce . Fixes however will only be in later Releases, probably Fx 27 esr or later, unless possibly it is a security issue important enough to fix in a point release of the current Fx22 esr and will be dependent on the low priority bug even being reproduced and fixed. * Fx 3.6 support on Macs <br /> It was possible you were on on Fx3.6 because you thought later versions were not supported on OS X, they are are and James commented on that. * If you go to OS X 10.7.x as you said you may on the Mackbook pro<br />then current mainline Releases or ESR Releases are useable. If nothing else you will be able to test these versions on your Mackbook pro. One way of doing that is by having multiple installs of Firefox. If the bug is fixed the fix probably would not get on to a Release prior to Fx28. You could test on the current release or better still on a Fx28 nightly,

提出問題者

John, I have NO intention of going to OSX 10.7 or above. Snow Leopard is the last OSX that supports Rosetta, and I'd have to spend buckets of money to replace a lot of software, not to mention buy a new (expensive) computer.

John, I have NO intention of going to OSX 10.7 or above. Snow Leopard is the last OSX that supports Rosetta, and I'd have to spend buckets of money to replace a lot of software, not to mention buy a new (expensive) computer.