Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Debug on Windows #1

Open
fastict opened this issue Sep 14, 2009 · 1 comment
Open

Debug on Windows #1

fastict opened this issue Sep 14, 2009 · 1 comment

Comments

@fastict
Copy link

fastict commented Sep 14, 2009

Hi,

I am trying to get Awesomium up and running on Windows. Here's my config:
XPSP2, Visual Studio 2008 SP1, Windows SDK 7.0.

The Release version compiles and runs ok (with minor adjustments).

The Debug version crashes soon after startup. It's in a different spot depending on which revision you're trying, but I think it's centered around isMainThread(). For example in one test, it failed the Assert() in ActiveDOMObject.cpp on this bit:

#if ENABLE(WORKERS)
ASSERT((m_scriptExecutionContext->isDocument() && isMainThread())
    || (m_scriptExecutionContext->isWorkerContext() && currentThread() == static_cast<WorkerContext*>(m_scriptExecutionContext)->thread()->threadID()));
#endif

Has anyone succesfully run the Debug version on Windows?

@pathorn
Copy link
Owner

pathorn commented Sep 14, 2009

Yeah, Chromium added an assert checking for the main thread, which actually checks the thread ID itself, rather than if you are in the same thread that started chromium

I don't think there's a way around this without a complete rewrite because awesomium is built from just the webkit layer and bypasses most of chromium's IPC code.

http://code.google.com/p/sirikata/source/browse/trunk/source/chromium-mainthread.patch

-Patrick

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants