+- CentBrowser Forum (https://www.centbrowser.net/en)
+-- Forum: Product Related (https://www.centbrowser.net/en/forumdisplay.php?fid=1)
+--- Forum: Bugs & Suggestions (https://www.centbrowser.net/en/forumdisplay.php?fid=4)
+--- Thread: [Bug Report] Runtime Error on 2.0.10.57_x64 (/showthread.php?tid=1170)
Pages:
1
2
[Bug Report] Runtime Error on 2.0.10.57_x64 - Explorare - 10-10-2016
System: Windows 8.1 Enterprise x64
Environment:
- All necessary VC++ library installed
- Mactype 20131231 installed
- Chrome 51.0.2704.103 (64-bit) installed
Many error messages came out when starting Cent Browser. Screen shoot as below.
Anybody have idea on why this happened and how to fix it?
Thx
RE: [Bug Report] Runtime Error on 2.0.10.57_x64 - tetsu - 10-10-2016
there's a newer version of mactype here: https://github.com/snowie2000/mactype/releases
may be you should update to see if it solves the problem.
RE: [Bug Report] Runtime Error on 2.0.10.57_x64 - Explorare - 10-10-2016
(10-10-2016, 12:06 AM)tetsu Wrote: there's a newer version of mactype here: https://github.com/snowie2000/mactype/releases
may be you should update to see if it solves the problem.
Thanks for your reply. I've updated the Mactype v1.2016.904.0 released on Sep. 04. But the problem still remains. And if I exclude the chrome.exe process in Mactype, the error not happened again. So there must be some compatibility problem with Mactype and Cent Browser? I start Mactype with registry mode.
RE: [Bug Report] Runtime Error on 2.0.10.57_x64 - tetsu - 10-10-2016
the setup i'm currently using is exactly like yours: windows 10 x64, Cent 64-bit with mactype in registry mode, and all's fine.
maybe something's wrong with your Cent installation.
did you try Mactray mode?
RE: [Bug Report] Runtime Error on 2.0.10.57_x64 - Explorare - 10-10-2016
(10-10-2016, 12:57 AM)tetsu Wrote: the setup i'm currently using is exactly like yours: windows 10 x64, Cent 64-bit with mactype in registry mode, and all's fine.
maybe something's wrong with your Cent installation.
did you try Mactray mode?
I've tried the tray mode. Got the same error message. I also added DirectWrite=1 and used the 1.16 patch for DirectWrite.
RE: [Bug Report] Runtime Error on 2.0.10.57_x64 - tetsu - 10-10-2016
i'm using vanilla Cent with no patch.
you may try portable version of Cent (with no patches), if there are no problems then those patches are the ones causing troubles.
RE: [Bug Report] Runtime Error on 2.0.10.57_x64 - Explorare - 10-10-2016
(10-10-2016, 01:29 PM)tetsu Wrote: i'm using vanilla Cent with no patch.Unfortunately the portable version didn't work too. I don't know why this could happened. They use the same chrome.exe process name. If I disable MacType for Cent Browser, it will also stop rendering Chrome as well.
you may try portable version of Cent (with no patches), if there are no problems then those patches are the ones causing troubles.
RE: [Bug Report] Runtime Error on 2.0.10.57_x64 - Admini - 10-10-2016
Maybe something conflicts with Chromium sandbox.
Have you tried running the browser(chrome.exe) with command line --no-sandbox?
Or upgrade MacType to 20160904 version(https://github.com/snowie2000/mactype/releases/download/v1.2016.904.0/MacTypeInstaller_2016_0904_0.exe)?
RE: [Bug Report] Runtime Error on 2.0.10.57_x64 - Explorare - 10-10-2016
(10-10-2016, 06:32 PM)CentBrowser Wrote: Maybe something conflicts with Chromium sandbox.
Have you tried running the browser(chrome.exe) with command line --no-sandbox?
Or upgrade MacType to 20160904 version(https://github.com/snowie2000/mactype/releases/download/v1.2016.904.0/MacTypeInstaller_2016_0904_0.exe)?
I am using the latest release for MacType and DirectWrite Patch. And `--no-sandbox` flag does work. The Cent Browser works again. But it's not secure without sandbox. So how to fix this? Thanks.
RE: [Bug Report] Runtime Error on 2.0.10.57_x64 - Admini - 10-11-2016
(10-10-2016, 11:47 PM)Explorare Wrote: I am using the latest release for MacType and DirectWrite Patch. And `--no-sandbox` flag does work. The Cent Browser works again. But it's not secure without sandbox. So how to fix this? Thanks.
Seems it is a conflict between DirectWrite Patch and chromium sandbox.
Have you changed this flag?
chrome://flags/#disable-direct-write
And you may follow this link to rebuild your Windows 8.1 font cache, and check the result.
http://www.tenforums.com/tutorials/54452-font-cache-rebuild-windows-10-a.html