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> .
Chosen solution
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.
Read this answer in context 👍 1All Replies (8)
Sorry I read it as willing to go to10.7.x you said unwilling.
OS X 10.6 will allow you to test Fx25 or better still Fx28 and so enable you to add Steps To Reproduce and a crash ID to Bug 878440 . It will also allow you to find and report the regression point in the bug report. That is assuming you are able to reproduce the crash on your Mackbook pro.
The bug report does show as affected Fx22, 23 ,24 and probably has not been tested and updated yet on Fx 25 . It does include in the initial comment
It first showed up in 23.0a1/20130503 and 22.0a2/20130423 but is discontinuous across builds.
There is no certainty that this is actually the same bug affecting your computer but no one has yet documented any attempt to find the regression range. Presumably because it is a known to be a low frequency crash; that has not been reliably reproduced. There is not much chance of any progress whatsoever without STR and regression ranges.
It may turn out that it is affected by third party software, and if so there is a possibility that that software may be fixed if the problem is identified. You will note that crash ID used as an example relates to a crash where the machine had several Firefox extensions installed. That could also explain both the low frequency of the crash reports and the discontinuity across builds.
Actually the 17.0.11esr released along side 24.1.1esr and 25.0.1 may be the last based on a older meeting notes I saw. If Mozilla does have another 17esr it will be 17.0.12esr when Firefox 26.0 and 24.2.0esr is released.
The current ESR is based on Firefox 24.0 and the next ESR will be based on seven versions later which will be 31.0.
Now I'm confused... I just received a message in my email from James that said: "Actually the 17.0.11esr released along side 24.1.1esr and 25.0.1 may be the last based on a older meeting notes I saw. If Mozilla does have another 17esr it will be 17.0.12esr when Firefox 26.0 and 24.2.0esr is released."
What's the latest version of Fx that will run on the following:
Mac Mini (Macmini1,1), Intel Core Duo, OSX 10.6.8 (Leopard)
P.S. I don't see James' comment on this BBoard.
Now I see the post, AFTER I posted the reply above. I did a refresh of this page before composing that reply, then it appears when I click "Post Reply". Is there something wrong with the BBoard system?
It is probably best to wait for James to confirm
but I have just been using been using Fx28a and although that has no release notes and system requirements, as it is not yet Released I presume it runs on OS X 10.6 AFAIK The system requirements and Release Notes get published as far as the Beta Version so it can be confirmed Firefox 26 is compatible.
There often seems to be lags on this forum before posts show up. And recently sometimes pretty slow loading times, but that is being looked into we are told.
FYI - I came back to view the latest response from John99 (@6:43PM), and it wasn't displayed. HOWEVER, at the top there was this: LAST REPLY BY JOHN99 - 55 MINUTES AGO. Those first four words were a link, and when I clicked it, John's reply showed up. So I'm not sure replies are being delayed, or you have to "click" that last-reply-by-whoever link to make it show up.
Lastly, I'll say this again, because I'm still being told about Fx-versions beyond Fx16, which is the LAST version that runs on OSX 10.5.x (Leopard), which is what I'm running now on my Mac-Mini. "QUESTION DETAILS" still shows my older 10.4.11 system, which was NOT the system that got the crash. It was simply the system I was using when I reported the crash.
I have no intention of going past Fx16 on my Mac-Mini. When I get a new computer, I'll find out what Fx version will work with it. Meanwhile, the crash is a crash, minor as it is, and can be circumvented by waiting for Fx to open it's 1st window. That's what I'm doing now in my Applescript. If anyone is interested in seeing the script, I can make it a down-loadable document from my Google Home Page. Just let me know, and I'll put it up, along with instructions for making it crash Fx22.
Modified by DICKGUERTIN
I will leave it to James, regarding any other suggestions and the forum problem.
Just thought you may be interested in using the mackbook to try to reproduce and troubleshoot the crash.
There is as I mentioned previously the posibility the crash could actually relate to third party software, and if that is the case the third party may fix the problem for you and that could enable you to fix the problem on the MacMini.
Mozilla bug fixes however revolve around tests on current Releases or preferably the development releases, with nearly all fixes involving Firefox code change gong through the train of pre release versions.
(Post tagged escalate as Mike obviously is able to demonstrte the forum problem, the new helpdesk may be interested in that)
Mike, and anyone else, might be able to use the information on this web page to demonstrate the crash. Read the body of the page, and pay special attention to the "my waitforit()" portion. There's a download-able applescript at the bottom of the page (click the down-arrow on right side). Good Luck.
Modified by DICKGUERTIN