mpawlowski

Hi Since around August 18th we've been seeing crash reports with mbae.dll on stack. This looks similar to what's been reported here: All reports are from Windows 8.1 or 10. Here's an example stack we see: >61b6d3df 1c3df mbae.dll >61b79011 28011 mbae.dll 61b78f7c 27f7c mbae.dll 61b81370 30370 mbae.dll >61b78f98 27f98 mbae.dll >77890ace 8face ntdll.dll 61b78f7c 27f7c mbae.dll >7783fc08 3ec08 ntdll.dll 61b78f7c 27f7c mbae.dll >778215d2 205d2 ntdll.dll 61b78f7c 27f7c mbae.dll >778214a6 204a6 ntdll.dll >7520dbf3 2cbf3 KERNEL32.DLL >01062f13 41f13 40 opera.exe exit_or_terminate_process(unsigned int) >01062ea9 41ea9 ef opera.exe common_exit(int,_crt_exit_cleanup_mode,_crt_exit_return_mode) 0105c840 3b840 0 opera.exe __except_handler4 >0106304e 4204e 11 opera.exe _exit >01059663 38663 107 opera.exe __scrt_common_main_seh(void) 010596c4 386c4 0 opera.exe _wWinMainCRTStartup 010596c4 386c4 0 opera.exe _wWinMainCRTStartup 0105c840 3b840 0 opera.exe __except_handler4 >751f8cc4 17cc4 KERNEL32.DLL Memcrash logs needed >77879674 78674 ntdll.dll Memcrash logs needed >77879643 78643 ntdll.dll Memcrash logs needed 010596c4 386c4 0 opera.exe _wWinMainCRTStartup Since Opera is based on Chromium, the root cause may be similar to but that's just guessing on my part.

We can't influence our users in regards to what software they have installed (apart from Opera itself, which autoupdates), we just get crash reports and try to figure out what causes them. The expiry on 31st makes sense, thanks for letting me know!

Hi all, I've contacted Support but were redirected here, so here goes: We've been seeing some crash reports from our browser with a stack that suggests a problem in mbae.dll. The stack looks like this: ntdll.dll!76f9bcfc() Unknown[Frames below may be incorrect and/or missing, no symbols loaded for ntdll.dll]MBAE.dll!708a3b0a() UnknownMBAE.dll!708a3c06() UnknownMBAE.dll!708a3de4() UnknownMBAE.dll!708a3e42() UnknownMBAE.dll!708a8bc8() UnknownMBAE.dll!70894969() UnknownMBAE.dll!708aa885() UnknownMBAE.dll!708aa8c5() UnknownMBAE.dll!70889fdd() UnknownMBAE.dll!7088d8cb() UnknownMBAE.dll!7088d6e9() UnknownMBAE.dll!708918fe() UnknownMBAE.dll!7088fc61() Unknownntdll.dll!76fa2e7e() Unknownntdll.dll!76fa2ed4() Unknownntdll.dll!76fca394() Unknownntdll.dll!76fca247() UnknownKERNEL32.DLL!74df8287() Unknown> opera.exe!__crtExitProcess(int status) Line 708 Copera.exe!doexit(int code, int quick, int retcaller) Line 609 Copera.exe!exit(int code) Line 393 Copera.exe!__tmainCRTStartup() Line 284 CKERNEL32.DLL!74de495d() Unknownntdll.dll!76fa98ee() Unknownntdll.dll!76fa98c4() UnknownThe crash reason is: "Unhandled exception at 0x76F9BCFC (ntdll.dll) in stack-250980583.dmp: 0xC0000008: An invalid handle was specified. If there is a handler for this exception, the program may be safely continued." We don't know what version of mbae.dll was being used. These crashes have been happening across many versions of Opera. First reports are from around November 1st, last is from December 31st, which coincides with the release date of 0.09.5.0250 PREVIEW. As you can probably tell by the stack, this happens on exit, after we've returned from main so we think the crash is not our fault. Please let me know if you're aware of this issue or had similar problems before. If you need the crash dump, I'll have to ask around if it's okay. Also, does MBAE have an autoupdate feature? I'm trying to figure out whether the fact that the crash reports stopped after 31st is the result of you releasing an update on 30th. Would you expect such quick intake of the new version from your users?