User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:188.8.131.52) Gecko/20090729 Firefox/3.5.2 AutoPager/0.5.2.2 (http://www.teesoft.info/) Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:184.108.40.206) Gecko/20090729 Firefox/3.5.2 AutoPager/0.5.2.2 (http://www.teesoft.info/) Hi. First of all, I want to say I'm sorry if my writing isn't that clear (I'm Brazilian). Let's go to the bug report. I use MAC/OS, and firefox for years, but he last 6 months that was a nightmare. Firefox 3 crashes everytime. Everyday I was looking for an update that could solve my issue. Every update, a new hope, but the problem persists. Last week, I had a simple idea, that was to delete my actual profile, and create a new one. OH MY GOD, THAT SOLVED THE PROBLEM! I COULD USE FIREFOX AGAIN, and that was the happiest day in web in my whole life. BUT, that was a problem. I had to search the web to learn how to manage profiles, and that was not easy. I had to open terminal, and go along the way to folders, and there I was. SO I SUGGEST TO YOU - TURN ON THE OPTION TO CREATE A NEW PROFILE AFTER AN UPDATE, OR MAKE SOMETHING THAT AUTOMATICALLY CREATE THIS NEW PROFILE AND TRANSFER THE USER SETTINGS. AFTER CHANGING THE PROFILE, FIREFOX NEVER CRASHED AGAIN. I KNOW THAT IS IT, BECAUSE BEFORE CREATING A NEW PROFILE, I'VE UNINSTALLED ALL MY EXTENSIONS, DELETED ALL BOOKMARKS, TRIED TO CHANGE ALL SETTINGS TO DEFAULT, AND SO ON. ONLY CREATING A NEW PROFILE (NOW WITH THE SAME EXTENSIONS I HAD), SOLVED THIS PROBLEM. TODAY, I'VE REGISTERED HERE, JUST TO SAY YOU THAT. THANK YOU FOR YOUR ATTENTION. Reproducible: Always Steps to Reproduce: 1. OPEN FIREFOX 3 ON MAC OS. 2. NAVIGATE FOR 1 - 2 MINUTES 3. CRASH. Actual Results: CREATED A NEW PROFILE, AND TRANSFER THE OLD SETTINGS TO THE NEW PROFILE. Expected Results: SOLVED ALL(LLLLL) THE PROBLEMS. I'M A HAPPY FIREFOX USER AGAIN. PLEASE, CONSIDER WHAT I'M SAYING, BECAUSE I LOVE FIREFOX, AND UNFORTUNATELY HATED IT FOR ALMOST 6 MONTHS OF CRASHES. IT WAS IMPOSSIBLE TO USE IT FOR MORE THAN 2 MINUTES. AFTER SOLVING THIS, IT'S EXTREMELY CONFIDENT. PLEASE, I WANT A REPLY FROM MOZILLA ABOUT MY REPORT. THANKS.
Starting Firefox in the Firefox safemode (http://support.mozilla.com/en-US/kb/Safe+Mode) or a new profile (http://support.mozilla.com/en-US/kb/Managing+Profiles) is only a step to find the real issue. That are the files in your profile http://kb.mozillazine.org/Profile_folder_-_Firefox#Folders and we need to find the file that is causing issues. Just creating a new profile doesn't solve the issue itself because it can always happen again.
Ok, I agree with that Matthias, every software can crash. But I can say that after this new profile, firefox return being the best internet browser I've ever seen. It's faster than ever, and extremely solid. Hope you're wrong.
Why don't we suggest users, to move the profile to a different directory. Then, if creating a new profile works. we ask to send the profile.
We (I) are already suggesting a new profile in some cases if the safemode doesn't help. Sending the whole profile is a no go because the profile contains many private data including passwords and Form history, history, bookmarks, personal security certificates To identify the issue you have to find the file and after that what in the file is causing the issue and finally what leads to this wrong "values" in the file.
Ok, thank you for the opinion. But the fact is, many users (I) didn't see anywhere your suggestion for new profile creation, and firefox became unusable for at least 4-6 months, even after updates. Some (not me) are not able to open and use the terminal for solving that. I'm suggesting to mozilla to automatically switch the old profile for a new one, backing up the settings, because manually doing that, solved ALL the problems I had. If that was a standard, I wouldn't notice any problem. Please, more opinions. Thanks again.
Well I don't have specific knowledge about the profiles, but I have seen lot of suggestions about new profiles and one could brainstorm about improvements. Offer a button to create new profile in session restore window. Further, FF should not never crash or get instable on files. Does Mozilla run fuzzers on profile files? Lucas
>Well I don't have specific knowledge about the profiles, but I have seen lot of >suggestions about new profiles What you see in bugzilla is just part of the things we do to isolate the issue and nothing more. >I'm suggesting to mozilla to automatically switch the old profile for a new one I'm sure that this will not happen because it's useless excedpt if you don't import all userfiles. Either you create a new profile and don't use the old files which would make nearly every user unhappy or you use the old profile. Importing the old files into a new profile means that you are using the same old profile again. >and firefox became unusable for at least 4-6 months, even after updates. We are interested if you know a file that causes an issue. We are also interested in crashes, in that case create a bug report and post a crash ID ( https://developer.mozilla.org/en/How_to_get_a_stacktrace_for_a_bug_report ). If you have water in your brand new car, would you be happy if the mechanic changes the wet carpet instead of repairing the spot where the water is coming into your car ?
Thank you very much for your comments. Matti, your comments are so intersting, that the last one could be left behind, we can go on without that. I'm very intersted about solving this, because I know what is it to find the best browser ever (FIREFOX, in this case), and work 4-6 months without it because of crashes, unexpectedly, everytime. If you want something to prove my interest about solving this issue, I can tell you that in Brazil I have more than 2,000 posts at a forum where I was the only one who spent time solving videocard problems. Again. I've created a lot of reports when firefox crashed, everytime I sent it to mozilla and almost everytime I've posted a comment there. I have the old profile (the one that crashes) here on my computer, and If I switch to it, firefox terminate with no reason. But the question is, WHY it was very nice and stable on versions before firefox 3 was released? If you have any sugestion to me about my profile (that crashes), I'll do that, and I'll try several times until exhaustion, to solve this. It was to bad being without firefox so much time. Nowadays, it don't crash for nothing, it's solid, faster than any other and extremely functional (thanks to my favourite extensions too).
Mattias, lot of arguments, but the facts are: - We have a loyal FF user. - The user has crashes for 4-6 months. - He found the solution (creating new profile), after 4-6 months. Those are pretty bad facts and I think there can be done more to deal with bad profiles. Lucas
Lucas: >- We have a loyal FF user That doesn't matter in bugzilla because the reporter usually doesn't matter for the priority of a bug. >- The user has crashes for 4-6 months He should have contacted the support earlier if he wants a solution. For example the knowledge database contains this article : http://support.mozilla.com/en-US/kb/Basic+troubleshooting and if you read this article you will find the "create new profile" part. >- He found the solution (creating new profile), after 4-6 months. He didn't found the solution from our point of view, he found a workaround. Finding workarounds is something for the support we try to fix the real issues here.That is the difference between the support and bugzilla. The support wants to help users with issues while bugzilla is a tool for the developers to fix bugs. ---------------------------------------------------------------------------- Rafael: >I've created a lot of reports when firefox crashed, everytime Those crashes are collected in the crash database and people are looking at the top crashes that affects many people. >I have the old profile (the one that crashes) here on my computer, and If I >switch to it, firefox terminate with no reason. Post a crash id for a start. https://developer.mozilla.org/en/How_to_get_a_stacktrace_for_a_bug_report
Good evening. I haven't contacted the support earlier because I thought it was an error that came out with the new update. I've moved on to Opera Browser (nice too, but not even close to FF) to wait for a new release, but everyday (more than 2 times a day) I've checked for a new Firefox update. When a new update was available, hope came to me with it. But the error persists. I've tried to "google" for the solution, but can't find anything useful. I've waited for new updates again and again, until last week, when I've tried to create the new profile. That worked like magic. I just couldn't believe that I could use firefox again, and I confirm that was the happiest day in my whole "web life" (I use computers since there were any type of network connection, and started working on bulletin board system (bbs) since the modem speed was 2400 bps...) I was pioneer in Remote Access in Brazil, at least in my city). Since I was an early internet user, from the beginning I've looked after solutions to substitute the "bad microsoft internet explorer". At that time, Mosaic and Netscape were my favorite. The reason for my post here, this week, was to share my experience with other users, not to create unfriendly discussions with you. If you look at my history, my problem was solved! I did not need to be here doing this, but all I want is to help Mozilla to make the best browser, better. About my old profile, today I've uninstalled all the add-on, themes, bookmarks, reset all to default. What I got? CRASH!. Changing the profile to the new one with all the extensions I like, resulted in safe, solid browsing experience. That's why I can say that creating a new profile is a nice start for us to solve at least some of unexpected firefox crashes. MATTHIAS, can you please be more specific about this CRASH ID (STACKTRACE) for a start, I went to the link you have posted, above, but I can't see nothing different from reporting the bug to Mozilla. Hope you can help me to work it out. Thanks a lot, again.
I understand that the new profile helped you to solve your issue with Firefox but that is something that doesn't matter here. In bugzilla you report a bug that contains all information like a crash ID and steps to reproduce that we can identify the issue. >I went to the link you have posted, above, but I can't see nothing different > from reporting the bug to Mozilla. Hope you can help me to work it out. Thanks a lot, again. We need a crash ID (if the crash reporter comes up) or a stack trace (if the crash reporter doesn't start). I hope you mean a real crash and not a hang/freeze. The link contains step by step instructions to either get a crash ID or a stacktrace. Start here https://developer.mozilla.org/en/How_to_get_a_stacktrace_for_a_bug_report#How_to_get_a_crash_ID_with_the_Mozilla_Crash_Reporter
Good morning. I'll record the screen, and send to you. Yes, that's a real crash. Firefox closes instantly, and the crash reporter starts immediately . I'll go back to work now, and in the afternoon I'll follow the steps you told me. Thanks again.
After the crash, restart and type in the address bar: about:crashes Then paste the ID in this bug. Lucas
Thanks Lucas. Here you are: 2d8cc2d9-a552-4d0a-9472-2ce652090814 8/14/09 9:39 AM. Back to work... Thank you very much.
If you put bp- for it, then Bugzilla makes it linkable: bp-2d8cc2d9-a552-4d0a-9472-2ce652090814 But you have to know that ;-)
0 Flash Player Flash Player@0x38bc5f 1 Flash Player Flash Player@0x2e9842 2 XUL nsNPAPIPluginInstance::SetWindow modules/plugin/base/src/nsNPAPIPluginInstance.cpp:1085 3 XUL nsPluginNativeWindow::CallSetWindow nsPluginNativeWindow.h:99 4 XUL nsObjectFrame::CallSetWindow layout/generic/nsObjectFrame.cpp:999 5 XUL nsObjectFrame::Instantiate layout/generic/nsObjectFrame.cpp:1832 6 XUL nsObjectLoadingContent::Instantiate content/base/src/nsObjectLoadingContent.cpp:1768 7 XUL nsAsyncInstantiateEvent::Run content/base/src/nsObjectLoadingContent.cpp:156 8 XUL nsThread::ProcessNextEvent xpcom/threads/nsThread.cpp:510 9 XUL NS_ProcessPendingEvents_P nsThreadUtils.cpp:180 10 XUL nsBaseAppShell::NativeEventCallback widget/src/xpwidgets/nsBaseAppShell.cpp:121 11 XUL nsAppShell::ProcessGeckoEvents widget/src/cocoa/nsAppShell.mm:405 12 CoreFoundation CFRunLoopRunSpecific 13 CoreFoundation CFRunLoopRunInMode The Flash Plugin is causing the crash...