Out of Memory crash on startup

[joeludwig]

We are getting a crash deep in CEF in one of the renderer processes. This is happening on customer machines where we don't have access to a lot of information, but I'm hoping somebody here will recognize this callstack and what might trigger it.

The process has only been running for a few seconds when it runs out of memory. From the call stack it looks to me like CEF is still starting up, and probably hasn't run any of the Javascript on the page yet, but if that is involved we're seeing this across multiple documents that run a variety of javascript. (All of them are running page that we serve from a local web server to function as UI in our system.)

Any ideas?

Code: Select all

    libcef.dll!base::internal::PartitionRootBase::OutOfMemory() Line 27   C++
    libcef.dll!base::internal::PartitionBucket::SlowPathAlloc(base::internal::PartitionRootBase * root, int flags, unsigned __int64 size, bool * is_already_zeroed) Line 539   C++
    libcef.dll!WTF::Partitions::FastMalloc(unsigned __int64 n, const char * type_name) Line 114   C++
    libcef.dll!WTF::WTFThreadData::Initialize() Line 46   C++
    libcef.dll!WTF::Initialize(void (void (void *) *, void *) * call_on_main_thread_function) Line 75   C++
    libcef.dll!blink::Platform::InitializeCommon(blink::Platform * platform) Line 194   C++
    libcef.dll!blink::Platform::Initialize(blink::Platform * platform, blink::scheduler::WebThreadScheduler * main_thread_scheduler) Line 177   C++
    libcef.dll!blink::Initialize(blink::Platform * platform, service_manager::BinderRegistryWithArgs<> * registry, blink::scheduler::WebThreadScheduler * main_thread_scheduler) Line 152   C++
    libcef.dll!content::RenderThreadImpl::InitializeWebKit(service_manager::BinderRegistryWithArgs<> * registry) Line 1211   C++
    libcef.dll!content::RenderThreadImpl::Init() Line 757   C++
    libcef.dll!content::RenderThreadImpl::RenderThreadImpl(base::RepeatingCallback<void ()> quit_closure, std::unique_ptr<blink::scheduler::WebThreadScheduler,std::default_delete<blink::scheduler::WebThreadScheduler> > scheduler) Line 715   C++
    libcef.dll!content::RendererMain(const content::MainFunctionParams & parameters) Line 191   C++
    libcef.dll!content::ContentMainRunnerImpl::Run(bool start_service_manager_only) Line 904   C++
    libcef.dll!service_manager::MainRun(service_manager::MainParams & params) Line 479   C++
    libcef.dll!service_manager::Main(service_manager::MainParams & params) Line 526   C++
    libcef.dll!content::ContentMain(const content::ContentMainParams & params) Line 19   C++
    libcef.dll!CefExecuteProcess(const CefMainArgs & args, scoped_refptr<CefApp> application, void * windows_sandbox_info) Line 213   C++
    libcef.dll!cef_execute_process(const _cef_main_args_t * args, _cef_app_t * application, void * windows_sandbox_info) Line 195   C++
    vrwebhelper.exe!CefExecuteProcess(const CefMainArgs & args, scoped_refptr<CefApp> application, void * windows_sandbox_info) Line 198   C++
    vrwebhelper.exe!vr::CefExecuteProcess(const CefMainArgs & args, scoped_refptr<CefApp> application, void * windows_sandbox_info) Line 121   C++
    vrwebhelper.exe!RealMain(int argc, char * * argv) Line 855   C++
    vrwebhelper.exe!VRCrashHandlerWrapMain<int,char * *,int &,char * * &,int>(int (int, char * *) * fnMain, int & <args_0>, char * * & <args_1>) Line 65   C++
    vrwebhelper.exe!WinMain(HINSTANCE__ * hInstance, HINSTANCE__ * hPrevInstance, char * lpCmdLine, int nShowCmd) Line 935   C++


[magreenblatt]

What OS and CEF version? 32-bit or 64-bit executable? What size is it failing to allocate? How much RAM does the machine have?

[joeludwig]

What OS and CEF version? 32-bit or 64-bit executable? What size is it failing to allocate? How much RAM does the machine have?

Sorry, should have included those.

OS: Windows 10 64 bit. 64 bit executable. AMD64 CPU
CEF version: 3578 (Yes, I know that's ancient. We can't upgrade until accelerated offscreen rendering is back up and running.)
The call to FastMalloc is being passed 16 and NULL (for type_name).

I don't know how much RAM the machine has, what else is running on that machine, or really anything else about the machine other than what ends up in a minidump. We've seen the crash from a dozen different machines, all of them in the wild. (Given our dump upload sampling rate it's probably 10x that number of actual crashes.)


Joe