Adobe previews 64-bit Flash Player 'Square'

[Blongs]

I haven't followed this thread much but what is the problem with Minefield exactly? I installed the latest build and it run perfectly fine.

I think people said something about it crashing on startup. I'm not sure as reading this made me stop myself from updating Minefield. Maybe I should just test it out...

Well, I cannot tell you whether you should or shouldn't but I can tell you that I am uneffected for it.

To those having the startup problems, try reportig the bugs to Mozilla if you haven't already. There may be a chance they have no clue about the bug!

To anyone still having problems with FF crashing on startup, try this, it seems to work

start minefield in safe mode
go into about:config
make sure these 2 line are set to false
javascript.options.methodjit.content
javascript.options.methodjit.chrome
restart minefield

Some have said that 1 line was set true and 1 false, just make sure both are set to false.

This has worked for me

 

[johnwillyums]

Excellent. Well done Blongs

I thought I'd try a reinstall so I uninstalled Minefield and installed the nightly build for today but that still didn't solve the problem. It seemed that Minefield was trying to restart my last session and crashing.
So I followed your instructions and went into about:config

my "javascript.options.methodjit.content" was set to true so I toggled it to false and everything seems to be ok again.
I'm none the wiser as to why this should have happened in the first place though.
Also signed up for the nightly builds test programme and newsletter. That gives an opportunity to report bugs.

Thanks again for your excellent fix, John

 

[kpo6969]

Not even trying Minefield x64 today. Last 3 days, installed, un-installed, clean install, etc..., etc...
Bug is still there so sticking with x86.

https://bugzilla.mozilla.org/show_bug.cgi?id=601355

 

[mikedl]

As has been mentioned many times in this thread, and on a few others, just stick with the October 1st nightly x64 build.

Try the updates. If they cause you to crash again, just reinstall the October 1st build again. It takes all of 2 minutes.

Until I get a new build (I try each nightly as it comes out) that lets me leave all of these settings on "true",

I'm going to keep reverting back to the October 1st build.

 

[Blongs]

Not even trying Minefield x64 today. Last 3 days, installed, un-installed, clean install, etc..., etc...
Bug is still there so sticking with x86.

https://bugzilla.mozilla.org/show_bug.cgi?id=601355

As per my previous post try this and you will be ok

start minefield in safe mode
go into about:config
make sure these 2 line are set to false
javascript.options.methodjit.content
javascript.options.methodjit.chrome
restart minefield

Some have said that 1 line was set true and 1 false, just make sure both are set to false.

 

[Klaw117]

Well, I cannot tell you whether you should or shouldn't but I can tell you that I am uneffected for it.

To those having the startup problems, try reportig the bugs to Mozilla if you haven't already. There may be a chance they have no clue about the bug!

Lol, I decided to try it and guess what? I click on the icon in the taskbar only for a window to pop up and say "Minefield has stopped working."

To anyone still having problems with FF crashing on startup, try this, it seems to work

start minefield in safe mode
go into about:config
make sure these 2 line are set to false
javascript.options.methodjit.content
javascript.options.methodjit.chrome
restart minefield

Some have said that 1 line was set true and 1 false, just make sure both are set to false.

This has worked for me

Thanks, this fixed the issue. Once a stable update comes out, I'm gonna revert it back.

 

[johnwillyums]

As has been mentioned many times in this thread, and on a few others, just stick with the October 1st nightly x64 build.

Try the updates. If they cause you to crash again, just reinstall the October 1st build again. It takes all of 2 minutes.

Until I get a new build (I try each nightly as it comes out) that lets me leave all of these settings on "true",
View attachment 102367
I'm going to keep reverting back to the October 1st build.

Pardon my ignorance but why doe it matter that they are on true?

Blongs' fix worked fine for me.

 

[Dark Nova Gamer]

Well, I cannot tell you whether you should or shouldn't but I can tell you that I am uneffected for it.

To those having the startup problems, try reportig the bugs to Mozilla if you haven't already. There may be a chance they have no clue about the bug!

Lol, I decided to try it and guess what? I click on the icon in the taskbar only for a window to pop up and say "Minefield has stopped working."

To anyone still having problems with FF crashing on startup, try this, it seems to work

start minefield in safe mode
go into about:config
make sure these 2 line are set to false
javascript.options.methodjit.content
javascript.options.methodjit.chrome
restart minefield

Some have said that 1 line was set true and 1 false, just make sure both are set to false.

This has worked for me

Thanks, this fixed the issue. Once a stable update comes out, I'm gonna revert it back.

That is why I won't tell someone if they should use a beta software that is not working for a good percentage of people.

I guess I am just lucky, it could also make a difference that I haven't had an installation of Firefox (minefield) on these two computers prior to 3 days ago (when I first installed both the 32-bit and 64-bit minefield).

 

[mikedl]

As has been mentioned many times in this thread, and on a few others, just stick with the October 1st nightly x64 build.

Try the updates. If they cause you to crash again, just reinstall the October 1st build again. It takes all of 2 minutes.

Until I get a new build (I try each nightly as it comes out) that lets me leave all of these settings on "true",
View attachment 102367
I'm going to keep reverting back to the October 1st build.

Pardon my ignorance but why doe it matter that they are on true?

Blongs' fix worked fine for me.

Blongs' fix worked for me as well but I just didn't like setting YaegerMonkey code to "false". I actually have the new builds working with YaegerMonkey "chrome" set to false and YaegerMonkey "content" set to true (not both set to "false") but I had to set TraceMonkey "content" to false (see below - this works in the new nightlies):


I guess I wasn't comfortable with that so I reverted to the October 1st build wherein I can leave them all set to "true" (see my post earlier).

Don't ask my why, as I have no pertinent reasoning, just a preference. Once the nightlies quit crashing with all of them set to "true," I'll quit reverting back to the October 1st build.

BTW, John, I have never thought of you as ignorant. I admire the knowledge you bring to these forums. In this case, perhaps it is I that is being ignorant in regard to my desire to have the settings all be true.

 

[mikedl]

Just tried the October 5th nightly. It's crashing still. Back on the October 1st build.

 

[johnwillyums]

Hey Mike. I wasn't being sarcastic. I genuinely don't know anything at all about YaegerMonkey code or the significance of the true or false commands.

 

[24c]

Just tried the October 5th nightly. It's crashing still. Back on the October 1st build.

Oct 1st build working OK for me too.

 

[neeraj]

Just tried the October 5th nightly. It's crashing still. Back on the October 1st build.

Oct 1st build working OK for me too.

but mine Oct 1st build is crashing again & again..!

 

[johnwillyums]

Blongs fix worked and Minefield has been stable. There was another update and it's still mostly fine.
I just noticed a reluctance to close or minimize and had to close from the task bar. Oh dear......

 

[mikedl]

Hey Mike. I wasn't being sarcastic. I genuinely don't know anything at all about YaegerMonkey code or the significance of the true or false commands.

That's OK. I decided to go with the new builds and set both mothodjit (YaegerMonkey) entries to "false" per Blongs' recommendation.


At least it keeps TraceMomkey code set to "true."

I just couldn't handle not being updated regardless of the settings.

I'm keeping an eye on the bug though:

https://bugzilla.mozilla.org/show_bug.cgi?id=601355

 

[PMorgan]

Any sign that ANY of the MineField releases since 10/1/10 do not need BLongs' "config" settings put to "false" to avoid crashing?

Regards,
- - Phil

 

[bobtran]

Any sign that ANY of the MineField releases since 10/1/10 do not need BLongs' "config" settings put to "false" to avoid crashing?

Regards,
- - Phil

Nope, the latest 4.0b8pre still needs "false", I tested at 7am this morning.

 

[johnwillyums]

Can someone explain to me what is the perceived danger in leaving the config settings set as false permanently?

 

[mikedl]

There is no "danger" but once JaegerMonkey is implemented bug-free, performance enhancements will finally be realized even more for the Javascript engine.

The "false" setting disables JaegerMonkey.

The TraceMonkey build works with JaegerMonkey enabled. Just don't update through the program - go to the TraceMonkey build link I referenced to check for the latest version.

Additionally, a poster on the Mozillazine site has compiled a new x64 installer with the fix for the JIT bug incorporated. It is a newer build than the JS Preview build as it incorporates the new spinning progress wheel on the tab.

 

[johnwillyums]

Thanks Mike. That's a lot clearer to me now. Presumably a build is coming that will not have this problem. J