We're sorry to hear that Firefox is crashing. In order to assist you better, please follow the steps below to provide us crash ID's to help us learn more about your crash.

1. Enter about:crashes in the address bar (that's where you enter your website URL) and press Enter. You should now see a list of submitted crash reports.
2. Copy the 5 most recent crash ID's that you see in the crash report window and paste them into your response here.

Thank you for your cooperation!

More information and further troubleshooting steps can be found in the Troubleshoot Firefox crashes (closing or quitting unexpectedly) article.

Actually Firefox 22.0 is not a Beta but a Nightly channel build. The Beta test builds are or were Firefox 20.0 as Firefox 20.0 looks like it may be released on April 2nd sometime.

Not sure why you thought a version three numbers a head of the current Release is a Beta build.

Until the move/merge of version on the channels happen they were for the last six weeks.

Firefox 19.0.* = Release
Firefox 20.0b* = Beta 
Firefox 21.0a2 = Aurora
Firefox 22.0a1 = Nightly

After the move/merges complete (soon) (23.0a1 will be on April 2nd Nightly update). Aurora channel builds will have updates disabled for a bit as usual due to being potentially unstable due to last minute dumping of checkins that can happen.

Firefox 20.0 = Release
Firefox 21.0b* = Beta
Firefox 22.0a2 = Aurora
Firefox 23.0a1 will start development on Nightly.

If you want a stable Firefox then use the Release or the Beta channel builds and if you want to be a Tester then use the Aurora and Nightly channel if you are adventurous. I do suggest to keep a separate Release or Beta build on hand with its own Profile in case a recent update on Aurora/Nightly build had issues that day. Nightly get checkins pretty much everyday so therefore gets updates pretty much day and Aurora gets update almost everyday also.

A place to hang out if you want to continue Testing the Nightly channel is http://forums.mozillazine.org/viewforum.php?f=23

Ver 22 is absolutely fine and stable with the only exception being Facebook. That is the only problem I am having with it. It didn't have this problem right at the start of Ver 22 with FB, just suddenly happened out of the blue after weeks of using it (and of course its predecessor Ver 21). It wasn't even like I had put the latest build in that day when it first happened. I can only presume it was because FB suddenly changed something that FF didn't agree with.

I have to revert to using FF19 purely because of the FB issue. This is the first time in all the time I have been using nightly builds (which started from way back in the Ver 3.6 days) that any issue has developed that has had no quick resolution. In the past these issues would only last a few days, not go for about 30 crash reports.

bp-a7f65372-53bf-48c0-927a-d91402130401 2/04/2013 12:18 p.m. bp-cbd0cc4a-a9db-41b1-bb71-d247d2130401 2/04/2013 12:17 p.m. bp-90792d9c-0623-4c7d-829b-d1ba32130401 2/04/2013 12:16 p.m. bp-2cab59e9-8960-46e4-ad03-c41d32130331 1/04/2013 9:41 a.m. bp-a37fdef9-4044-42ce-b5ff-8add72130331 1/04/2013 9:11 a.m.