Archived

This topic is now archived and is closed to further replies.

Bill Henslee

winpc issue Maxthon 5 has unacceptable rate of error close down

7 posts in this topic

I am getting a lot of error messages that Maxthon 5 has to be shut down. It give me the option to send back a response which I always do. But this begs the question of why this browser fails so often. Is there any download pack that fixes this problem?

1 person likes this

Share this post


Link to post
Share on other sites

Try a clean install of Maxthon.

Share this post


Link to post
Share on other sites

As above, and test with portable version.

Something clearly wrong, as it shouldn't be doing that.

Share this post


Link to post
Share on other sites

maybe if you try do do the same thing leading to a crash the result is a crash

i experienced two crahes. i have send a report. I'm waiting.

Mx5 is not my regular browser; i just try it like a not achieved soft; everybody should consider.

 

Share this post


Link to post
Share on other sites

This is the error detail of my problem. 

{"deviceid":"54E2F02B4119B9EE013DA7CE82598BA827740000","usertime":381,"cv":"5.0.1.3000","l":"en-us","pn":"max5","maxthoninfo":"Maxthon.exe%20=%205.0.1.3000%0D%0AMxBrowser.dll%20=%202.0.0.118%0D%0Amx_core.dll%20=%203.1.15.382%0D%0AMaxzlib.dll%20=%202.2.3.10%0D%0AMxAccountSvc.dll%20=%202.1.3.32%0D%0AMxAddonsMgr.dll%20=%205.3.0.10%0D%0AMxCrashCatch.dll%20=%204.0.1.18%0D%0AMxCrashReport.exe%20=%204.0.1.18%0D%0AMxDb.dll%20=%205.37.19.8%0D%0AMxDownloader.dll%20=%205.1.0.110%0D%0AMxEncode.dll%20=%202.0.0.10%0D%0AMxFilePackage.dll%20=%202.0.3.6%0D%0AMxHttpRq.dll%20=%204.0.0.58%0D%0AMxIPC.dll%20=%204.3.0.10%0D%0AMxMsg.dll%20=%202.0.0.24%0D%0AMxResMgr.dll%20=%205.2.7.146%0D%0AMxRsc.dll%20=%205.0.0.24%0D%0AMxTool.dll%20=%202.2.0.74%0D%0AMxUI.dll%20=%203.3.3.136%0D%0AMxXDR.dll%20=%202.1.0.8%0D%0AMxCmpUrl.dll%20=%205.0.0.12%0D%0AMxFav.dll%20=%204.0.0.18%0D%0AMxFavDb.dll%20=%2013.0.0.12%0D%0AMxHistory.dll%20=%202.5.0.6%0D%0AMxQRGen.dll%20=%202.1.0.6%0D%0AMxSiteIcon.dll%20=%202.0.18.38%0D%0AMxSmartUrl.dll%20=%203.0.0.44%0D%0AMxStorage.dll%20=%202.0.6.18%0D%0AMxMolebox.dll%20=%201.2.0.136%0D%0AMxSync.dll%20=%203.0.2.28%0D%0AMxUrlSec.dll%20=%203.0.0.40%0D%0AMxAvatarExt.dll%20=%205.1.0.8%0D%0AMxExtTools.dll%20=%204.0.0.22%0D%0AMxAddonMisc.dll%20=%205.2.0.44%0D%0AMxMsgCenter.dll%20=%201.0.0.5%0D%0AMxMsgPush.dll%20=%203.0.0.52%0D%0AMxQrcLogin.dll%20=%201.0.0.4%0D%0AMxSvInfo.dll%20=%203.2.0.20%0D%0AMxUeip.dll%20=%203.0.0.34%0D%0A","addonslist":"","urllist":"","systeminfo":"Physical%20memory%20total:%209654358016%0D%0APhysical%20memory%20free:%205319884800%0D%0APage%20file%20total:%2019318034432%0D%0APage%20file%20free:%2013990653952%0D%0AVirtual%20memory%20total:%204294836224%0D%0AVirtual%20memory%20free:%203756179456%0D%0AProcess%20Memory%20Usage:%0D%0APeakWorkingSetSize:%20836775936%0D%0AWorkingSetSize:%20216883200%0D%0APagefileUsage:%20185913344%0D%0A","commandinfo":"%22C:%5CProgram%20Files%20(x86)%5CMaxthon5%5CBin%5CMaxthon.exe%22","sv":"10.0.14393.","crashtime":1481035991,"m":"Maxthon","n":"mx_core.dll","stack":"1=0001:006947EF%20C:%5CProgram%20Files%20(x86)%5CMaxthon5%5CCore%5Cmx_core.dll_3.1.15.382%0D%0A2=0001:004C80C3%20C:%5CProgram%20Files%20(x86)%5CMaxthon5%5CCore%5Cmx_core.dll_3.1.15.382%0D%0A"}

Share this post


Link to post
Share on other sites
53 minutes ago, Bill Henslee said:

This is the error detail of my problem. 

{"deviceid":"54E2F02B4119B9EE013DA7CE82598BA827740000","usertime":381,"cv":"5.0.1.3000","l":"en-

Please read the following thread first:

@BugSir006  The reason for the error is file mx_core.dll but his diagnosis is the role of the MX developer team

PagefileUsage: 185913344
","commandinfo":""C:\Program Files (x86)\Maxthon5\Bin\Maxthon.exe"","sv":"10.0.14393.","crashtime":1481035991,"m":"Maxthon","n":"mx_core.dll","stack":"1=0001:006947EF C:\Program Files (x86)\Maxthon5\Core\mx_core.dll_3.1.15.382
2=0001:004C80C3 C:\Program Files (x86)\Maxthon5\Core\mx_core.dll_3.1.15.382

Share this post


Link to post
Share on other sites

 

Thank you Mr. G for helping decipher! I'll wait for the dump file. 

Share this post


Link to post
Share on other sites