Aurora receives an update everyday. See if tomorrows version is less prone to crash.

I'm curious why you are using Aurora to begin with. I trust that you are aware that Aurora is an alpha-2 level pre-release build which is intended for "testing" new features. Not intended to replace the stable Release build.

Yes I am aware of the purpose of Aurora channel ;) I used it for testing more before and it became my regular browser.

I'm curious why there is no way to control the Aurora updates, from a testing perspective it would be useful to rollback/forward version, to test anything and know from which version it stopped working etc.

Maybe there is or suppose to be add-on to control Aurora versions.

See also:

• http://forums.mozillazine.org/viewtopic.php?f=23&t=2848781

Before the software updator existed in the then Firefox 1.5 builds in development on the then Trunk builds (Nightly) you had to download and setup each new build manually (with its own Profile) for the years before so it was not uncommon for the Testers to have a dozen plus builds going at a time. This made it easier for going back to a useable build in meantime if there was a issue in current build(s). Nowdays testers are more lazy in relying on the partial updates each time there is checkins which then means updates.

See also:

• http://forums.mozillazine.org/viewtopic.php?f=23&t=2848781
• bug 1031697 - Aurora32.0a1, crash in nsTArray_base<nsTArrayFallibleAllocator, nsTArray_CopyWithConstructors<JS::Heap<JSObject*> > >::IncrementLength(unsigned int) | mozilla::net::HttpBaseChannel::ApplyContentConversions() </li>

Comment 6: workaround browser.cache.use_new_backend_temp = false

The workaround "browser.cache.use_new_backend_temp = false" worked, but for now it is only a patch not a solution. The solution now would be downloading installer with earlier version.

If it works with the workaround then there is no need to revert to an older version. Keep the new cache backend disabled for now and keep an eye on the developments, either via the mozillaZine Builds forum or the involved bug reports.