Minefield Nightly build crashes

[yowanvista]

Use the hourly builds: Index of /pub/mozilla.org/firefox/tinderbox-builds/mozilla-central-win32

Is there an advantage in doing so? I mean, over the nightly builds?

Here is the link to the x64 hourlies. (they're not quite hourlies)

These builds are compiled every hour and contain the latest fixes/features but they might be buggy

 

[mikedl]

Thanks, Yowanvista, but I'll stick with the nightlies. I like being on the cutting edge, even the bleeding edge, but I think I'll stay out of the tinderbox for now.

 

[windstrings]

Doesn't seem I'm able to do much with it. I get a few menu options, but don't seem to be able to change the value to false. I feel like a huge n00b. When I double-click it (I searched and found how boolean values are changed) minefield will crash.

By the way, for those who don't already know, I found this nifty little link: http://www.computerworld.com/s/article/9020880/Hacking_Firefox_The_secrets_of_about_config

Does anyone know if the "prefs.js" file from 32 bit FF can simply be copied to the 64 bit version to maintain all of your tweaks and settings?

 

[bobtran]

Doesn't seem I'm able to do much with it. I get a few menu options, but don't seem to be able to change the value to false. I feel like a huge n00b. When I double-click it (I searched and found how boolean values are changed) minefield will crash.

By the way, for those who don't already know, I found this nifty little link: http://www.computerworld.com/s/article/9020880/Hacking_Firefox_The_secrets_of_about_config

First you highlight (single click) the option to be changed then right click on the true/false and choose "Toggle"

 

[HOT97ECLIPSEGSX]

Toggling the option also crashes Minefield. I'll do what mikedl suggested and see if I can get it to work.

 

[zigzag3143]

I just cant live without my addons so I ended up going back to Firefox

RE: ADDONS

There is a about:config edit the stops the verify so you can run all your addons. I have been using it forever. Just google it.


Ken


edit: see bobtran post for the link. Sorry didnt see the post.

 

[HOT97ECLIPSEGSX]

I don't know what impacts the settings might have on the performance of Firefox but I'm heading over to Bugzilla and MozillaZine to see what I can find out.

Did you ever find anything out about this over on Bugzilla or MozillaZine? Interested.

 

[windstrings]

So at this point in time which version are you guys recommending as the most stable for running 64 bit flash?

Still the third one down on this link?
Index of /pub/mozilla.org/firefox/nightly/2010-10-01-02-mozilla-central

 

[bobtran]

So at this point in time which version are you guys recommending as the most stable for running 64 bit flash?

Still the third one down on this link?
Index of /pub/mozilla.org/firefox/nightly/2010-10-01-02-mozilla-central

Yes third one down, you may want to change the update options to "ask me what I want to do" in the options menu otherwise it will just update back to the current problem. You can always change it back later or manually update under help -> about minefield.

Or change javascript.options.tracejit.content in the about:config to false which is also working with the current release.

 

[windstrings]

Great!... that was the concise answer I was looking for.... the config mod sounds easy enough too.... too cool!... thanks!

Did you manually go through and redo all your config settings for X64 or did you just paste your old 32bit prefs.js file to the X64bit version?

 

[windstrings]

seems installing the adobe update makes my old 32 bit FF think it needs to update adobe...

 

[windstrings]

I just cant live without my addons so I ended up going back to Firefox

RE: ADDONS

There is a about:config edit the stops the verify so you can run all your addons. I have been using it forever. Just google it.


Ken


edit: see bobtran post for the link. Sorry didnt see the post.

Does this look familiar?

Advanced users can disable extension compatibility checking in Firefox by adding the boolean preference "extensions.checkCompatibility" and setting it to false

I did that but I still show all my add-ons as incompatible.

Normally I would expect to go to help ---> check for updates to prompt the add-on update.. but it appears the beta does not have that feature.

Even attempting to install the nightly tester tools doesn't work because that is not compatible either.

Ken, are you running the latest beta and can you run your add-ons?

I'm hoping to find a fix for this since my fingerprint software also adds an extension so that it can work within FF and presently, it obviously won't work.

 

[windstrings]

Humm.... if I can't load my extensions.. I might as well be using Chrome.... according to peacekeeper, its about twice as fast as FF.
I did a test between 3.65.10 32 bit and the latest FF beta 64bit .... I"m on my laptop with wireless 5.3G connection, cable internet running an intel multicore I7 720 processor.
Here are my results..
3366 points for minefield with peacekeeper.
2550 points for 3.6.10 2470 second time.

Looks like Chrome 7.0.5 runs twice as fast according to their benchmarks.....

 

[bobtran]

It depends on the add-on, most will not work yet but Adblock works fine. Not sure about the others because this is the most important to me. If I really need an add-on then I just use Firefox 3.6.10 (x86).

I am playing with Chrome but only on my laptop which is x86. I want to run x64 browser as default unless there is an insurmountably issue, thus Minefield as default.

While Chrome may be technically faster, the difference really isn't that apparent so, I tend to stick with Firefox/Minefield. After 22 months of Wildblue internet (My old ISP) any browser on TransWorld Network (My new ISP) is fast, fast, fast.

 

[windstrings]

I do love a lot of the addons FF offers.... If we can figure a way to get the addons to load onto FF 64bit, we have a winner... otherwise, I'm tempted to just use Chrome and then use FF whenever I need the add-ons for some thing special.

Of course, Chrome does have its own extensions its working on... something to consider if FF beta doesn't provide a way to install add-ons.

I'm just not convinced FF64bit is much slower than 32bit Chrome.....

I'm still trying to figure a way to get addons to load to FF prebuild.

 

[dgwin7]

I just updated to 4.0b8pre today !!! but still same fock problem crashes !!!!.

dg

 

[mikedl]

Yeah, same here. It's still necessary to leave the "javascript.options.methodjit.content" entry set to "false."

 

[Blongs]

Yeah, same here. It's still necessary to leave the "javascript.options.methodjit.content" entry set to "false."

Interesting thing I found today, I uninstalled both Firefox and Minefield including my profile info and reinstalled both Minefield X64 and Firefox 4.0 beta 6 from scratch. I went into about:config and found these entries loaded by default

"javascript.options.methodjit.content" (true)
"javascript.options.methodjit.chrome" (false)

Both seem to be working fine at the moment

After updating minefield to latest version, problem returned. Had to set "methodjit.content" back to false

 

[mikedl]

Thanks, Blongs, that is interesting. I'm might give it a shot and see what happens.

You no longer have a crashing issue with leaving the default "methodjit.content" set to "true?"

Currently, the "methodjit.content" entry on my set-up is showing "true" to be the default, just as you have indicated (I have to change it to "false to prevent crashing), whereas the "methodjit.chrome" is showing "false" to be the default, just as you have indicated.

I quit running the 32 bit version of FF a while ago. I don't even have it installed any longer.

EDIT: An uninstall and a re-install from scratch didn't work for me. I still have to go into safe mode and set the "methodjit.content" entry to "false."

 

[Blongs]

Thanks, Blongs, that is interesting. I'm might give it a shot and see what happens.

You no longer have a crashing issue with leaving the default "methodjit.content" set to "true?"

Currently, the "methodjit.content" entry on my set-up is showing "true" to be the default, just as you have indicated (I have to change it to "false to prevent crashing), whereas the "methodjit.chrome" is showing "false" to be the default, just as you have indicated.

I quit running the 32 bit version of FF a while ago. I don't even have it installed any longer.

EDIT: An uninstall and a re-install from scratch didn't work for me. I still have to go into safe mode and set the "methodjit.content" entry to "false."

Sorry, after updating minefield it went back to same problem. Had to change "methodjit.content" back to false to prevent crashes.