Windows chromium-browser fresh build stacktrace and anonymous fatal errors on runtime

I hope this is a right place to ask this question, and if not, please tell me where I should ask it. I tried on chromium-discuss with no luck yet (I will give updates to both places if I get in the right path from any advice here or on chromium-discuss forums).

Recently, I've started to put time and efforts into understanding the chromium project. My goal is to eventually be able to contribute as a developper, so I ended up looking how to get it and build it locally. I am facing some issues when running it and cannot find any explanation just yet.

Hopefully it will help other people that are in the same situation. After looking quite a bit on forums, I didn't find something similar and would like to know if this is something I've missed.

I am trying to run chromium-browser on Windows 10 Home Edition. My current configuration is i5-2500k / 8gb DDR3 and my workspace is on a hard drive until I get a bigger SSD (The recommended specs are suggesting 16-32, can it be part of the problem?).

My current chromium build is: Version 54.0.2808.0 (64-bit)

To fetch and build the project, I've followed the instruction on how to get the code.

What I did is:

• Extracted the windows version of the depot-tools into my workspace
• Fetched the repositories with fetch chromium and gclient runhooks
• Built with cd src, gn gen out/Default and ninja -C out/Debug

The build process does its job and no errors are showing up in console. However, when I launch the browser, I get multiple errors that seems to be related to the stacktrace. Those errors are not modal and as long as I don't close any of them, chrome keeps responding and pages are shown as expected so this is no big deal for now:

But, if I do some heavy loading (e.g.: loading the facebook news feed), it seems to hang and doesn't respond very well from this point (e.g.: endless loading, mouse events not working inside tab). It can also be reproduced on my end by going to https://www.google.ca and right-clicking anywhere on the page.

To try speeding things up a little bit, I've run a script to rename every pdb files so they are not attaching to the process. This greatly improves speed, but there are still errors. StackTrace errors become this:

As for the hanging issue, it will now show an empty modal box suggesting an error (the description isn't too kind on what it is). This one is modal and once closed, chrome stops working as intended. What happens is the mouse over events don't show up, and the page will never finish loading when reloading it.

I am aware that the latest version can be instable sometimes. Is there something I did wrong here or steps I may have missed?

Thanks a lot, any help is greatly appreciated!

Frederik

Recent Questions...