Could be.
But they ought to tell users what they fix with each new build.
That is the norm in the software industry as a whole and in their own product history.
Without that information, it's impossible for users -- especially those gracious enough to beta test -- to guess WHAT the supposed fixes are.
I don't understand their recent opacity and apparent lack of organization/coordination/communication.
MM
Latest version 1.09.1.1261[info2]
See first post
If you wait it will update automatically, in the background silently, or it you want it now, go to the provided link in the first post
[/info2]
Hi:
That's highly abnormal.
Most of the issues that were behind the fixes for the current build relate to Edge/IE, security apps, etc, not Firefox.
Are you sure it's MBAE that's causing the Fx crash?
Reason for asking is that most Fx performance issues originate in the user's profile.
The first, basic step in troubleshooting Fx issues is Mozilla Safe Mode (not to be confused with Windows Safe Mode):
Troubleshoot Firefox issues using Safe Mode | Firefox Help
It may help to isolate the issue to a wonky extension (a common cause of Fx problems).
But it could be a plug-in problem hardware acceleration, software conflict (especially security programs), giant cache, etc.
There's a set of steps to try, such as a new, clean profile with no add-ons or extensions:
https://support.mozilla.org/en-US/kb...refox-problems
That also helps to isolate the issue.
I don't wish to pull this thread off-topic.
It's just that there haven't been (m)any recent trouble reports of MBAE and Firefox at the MBAE forum...
If you do end up isolating your issue to MBAE, then the best place to report it would be at the MBAE forum.
The devs and QA team monitor that forum and are quite responsive.
Cheers,
MM
Hi MM and thanks for your reply.
Yep, I am pretty sure I've narrowed it down to this. I backed up my bookmarks and Revo'd FF out completely, after messing around for days (in-between other stuff). I am on the 64-bit version 50 now, and I can turn MBAE on, crash the browser immediately; turn MBAE off and it works fine. I don't have this problem with any other browser. I tried v48, 49 & 50, in both 32 and 64-bit. Only v48-32 bit clean install did not present the problems with the previous version MBAE running.
I did have an issue with ESET NOD32, which was resolved. You can see that here. Not sure why I seem to be the only one having this problem.
Hi:
I've never heard of this issue and don't see anything like it, but it must be real for you and your system.
I wonder what would happen under 32-bit Fx, instead of 64-bit?
(64-bit has always been a bit buggy for a lot of folks.)
I hope the forum Admins here will indulge me:
Probably the only way to get to the bottom of it without a lot of guessing will be to post at the MBAE support forum.
The MBAE logs they will undoubtedly need to see are not "end user-friendly", so I can't be of much help.
I suggest starting with this sticky for instructions:
[README FIRST] Posts here need to include MBAE logs
Then I would post the requested logs (the zipped MBAE logs and both logs from FRST) here:
Malwarebytes Anti-Exploit - Malwarebytes Forums
One of the staff members will likely reply promptly and assist you with sorting it out.
Please let us know how it goes,
MM
P.S. To avoid cluttering @Cliff S's thread, perhaps a mod/admin might split off this sub-thread to a new topic?
@simrick, this is a shot in the dark. Sometimes....the service gets messed up or not replaced on an MBAE update. Do these match on yours?Hi MM and thanks for your reply.
Yep, I am pretty sure I've narrowed it down to this. I backed up my bookmarks and Revo'd FF out completely, after messing around for days (in-between other stuff). I am on the 64-bit version 50 now, and I can turn MBAE on, crash the browser immediately; turn MBAE off and it works fine. I don't have this problem with any other browser. I tried v48, 49 & 50, in both 32 and 64-bit. Only v48-32 bit clean install did not present the problems with the previous version MBAE running.
I did have an issue with ESET NOD32, which was resolved. You can see that here. Not sure why I seem to be the only one having this problem.
Quote
You're welcome.
