Jump to content


  • Posts

  • Joined

  • Last visited

Everything posted by SmileyBarry

  1. A couple thingsthat I've noticed just now: The title is badly worded: this started happening after the upgrade, but keeping it on before the upgrade isn't the cause of this issue. The stack trace, at least around the unloaded area, (above the last mbae64.dll call) is most probably wrong and showing data as function addresses. (There can't be code at 0x0000000000000084 or (user-mode code at) 0xffffffff82ac8004) The actually-mapped addresses might still help, though.
  2. I upgraded a couple weeks ago to Windows 10, and multiple Chrome processes started crashing on-launch. However, the main process, tab processes and extension processes don't seem to be affected, as the browser can keep running without any crash notification. I tried reinstalling, I tried doing a clean reinstall (deleting all remnants and rebooting between uninstall/install cycles), I tried the 1.08 beta and nothing works. I've kept MBAE off for the past two weeks thinking it'd get fixed in a new update, but I checked just now and the problem still occurs. On the latest crash, I looked into it and it's due to an invalid handle exception, raised by your DLL on the process' exit. (See attached screenshot) This was on beta This is on an up-to-date version of Windows 10 Pro x64, and it occurred on both version and the beta. My Chrome version is 45.0.2454.85 (Official Build) m (64-bit). I also use Avast Free Antivirus v10.3.2225. P.S.: I know I'm supposed to attach all user data as well, but I don't want to post it on a public forum. I can PM it to you if necessary.
  3. Okay, it's been over 2 hours and Chrome hasn't crashed, so I'm beginning to believe it's MBAE.
  4. Hi, I've used MBAE for a while now with Avast! Free on my Windows 7 Ultimate 64-bit machine, and I'm having some very weird Chrome crashes, without any malware. (I already went through the works and checked for malware with multiple products and came up empty) (Heads up: sorry for the lengthy post, thought you should know the whole story) After every long(ish) browsing session, I had Chrome beta (v40) crash when I exited the browser. I didn't mind much, because I was shutting down anyway, but one day I broke and opened Visual Studio for debugging. It was an Access Violation, and at first, it seemed like an extension bug, so I uninstalled it. Then another extension "caused" the crash. I noticed they were the only two extensions that needed full page access -- and I had a beta feature turned on that restricted full-page access -- so I thought it was related. (According to the stack trace, the crash occurred when the GUI tried to draw the extensions' icons and they were the only two extensions with icons in the address bar that weren't supposed to have one. (That's where full-page access is enabled) After disabling that feature, it seemed like it was OK again -- but then random (after about an hour) crashes started appearing, this time due to an Invalid Handle being closed. Chromium wiki says this points to corruption (without any actual handle bug), which sounds about right because my stack looks exactly like the second example. (Except "ntdll.dll" had called the exception, not any debug function) My point is: I've disabled MBAE about 20 minutes ago and I've had zero crashes so far. I noticed the known issues have nothing on Chrome x64 or Avast, but is there any chance of an incompatibility here? I'll wait until the hour passes and see, but so far it looks like MBAE is the culprit.
Back to top
  • Create New...

Important Information

This site uses cookies - We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.