Can I ask about FATAL and WARNING log?

[mung]

Hi ~

Window7, CEF 3.3440.1805.gbe00f9, used multi_thread_message_loop and subProcess in OSRMode.

Can I ask about FATAL and WARNING log?

I got a log message and call stack.

---- When I try to shutdown -----------------------------------------------------
[0831/145129.430:WARNING:discardable_shared_memory_manager.cc(431)] Some MojoDiscardableSharedMemoryManagerImpls are still alive. The will be leaked.
and
[0831/145129.587:FATAL:keyed_service_base_factory.cc(56)] Check failed: (sequence_checker_).CalledOnalideSequence().

fatal.jpg (77.6 KiB) Viewed 5426 times

---- ~When I try to shutdown -----------------------------------------------------

What is Mojo? When I got the log, what do I check things?

Actually, I have some problem, When I Minimize and Restore device in My D3D application.

so, while I looking for a solve way, I got the log.

I think some memory is leaked in CEF.

But, I don't know what I wrong?

Step is
open a OSRMode web browser in d3d application fullscreen mode ->
Try Minimizing window (Alt + Tab) ->
Clicked Minimized icon (try to restore d3d application) ->

When I while the step, often happened crash.

I can't try the step in cefSample. the sample is not a D3D application.

Could you advise me What should I check?

Thank you.

[Czarek]

You have to free CEF references before calling CefShutdown.
What is the stack trace for your crash?

[mung]

You have to free CEF references before calling CefShutdown.
What is the stack trace for your crash?

You can see the First problem in CefClient (build project).
I didn't create any web browser.
Just I executed CefInitialize() and CefShutdown.

You can see the call stack that is in upside image.
and You can see in CefClient --off-screen-rendering-enabled --multi-threaded-message-loop x64 debug.
Just start and click the 'X' button in the title.

The second problem(My crash d3d application)'s call stack is not exactly.
It is some different call stack maybe memory leak that is because.

I will share the CallStack after I collect information.

[Czarek]

In general, if the issue doesn't occur in Release mode then there is a small chance that it is going to be fixed.

[mung]

In general, if the issue doesn't occur in Release mode then there is a small chance that it is going to be fixed.

I'm sorry, I can't understand.

Do you mean it is not a problem?
Or it is going to be fixed?

I'm sorry I'm not good at English.

The second problem occurs in Release mode too.

Thank you

[Czarek]

I guess the checks that fail in Debug mode are in Chromium code. Looks like the first issue is already reported in CEF tracker:
https://bitbucket.org/chromiumembedded/ ... 5275-fatal

[mung]

I guess the checks that fail in Debug mode are in Chromium code. Looks like the first issue is already reported in CEF tracker:
https://bitbucket.org/chromiumembedded/ ... 5275-fatal

Ah, I got it.
Thank you I will share the second problem after collect information.

Thank you

[mung]

I guess the checks that fail in Debug mode are in Chromium code. Looks like the first issue is already reported in CEF tracker:
https://bitbucket.org/chromiumembedded/ ... 5275-fatal

this call stack is when I got a crash. [case 1]

when I got a crash call stack

crash_alttab.jpeg (120.22 KiB) Viewed 5404 times

It happened crash when my D3D9 application restore.

and it is CefMainThread when I got a case 1.

when I got a crash call stack cef main thread.

multithread_loop_cefmainthread.jpeg (118.19 KiB) Viewed 5404 times

When I use SingleThreadMessageLoop

single thread messge loop - call stack

SingleThreadMessageLoop.jpeg (100.31 KiB) Viewed 5387 times