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

ChromiumFXRenderProcess.exe crash problem #125

Closed
HADB opened this issue Aug 25, 2019 · 3 comments
Closed

ChromiumFXRenderProcess.exe crash problem #125

HADB opened this issue Aug 25, 2019 · 3 comments

Comments

@HADB
Copy link

HADB commented Aug 25, 2019

Recently, we found our app will show blank screen after running in 4K screens for some time.

We are using large images for 4K screens which may cause more cpu and memory using.

Memory using of ChromiumFXRenderProcess.exe will growing up to about 400M and then the process will go missing which causes blank screen.

And sometimes, ChromiumFXRenderProcess.exe will not be killed after the main application exited.

It seems ChromiumFXRenderProcess.exe is uncontrollable.

I found ChromiumFX has some new release after 3.3440.x, will these updates be useful?

What do you suggest to locate the problem?

Thanks!

@David-Desmaisons
Copy link
Member

David-Desmaisons commented Aug 25, 2019

  1. You may use Chromium inspector memory tabs to try get more information of the problem
  2. Are you using 64 bits builds this may help with memory problem.
  3. Maybe you can try to play around with Chromium switch that may be helpfull for your use case.
  4. The updates may be useful as Chromium keeps improving its memory performance, I will provide in the short/mid-term.

It will be also nice if you could list your application here: #12

@HADB
Copy link
Author

HADB commented Aug 26, 2019

Thanks for replying.

We reduced the size of these large images yesterday and never see blank screens again.

I will go digging this problem after our project launched.

@HADB
Copy link
Author

HADB commented Sep 2, 2019

Update:
Using 64 bits builds solve this problem.

Problem I found while using 64 bits builds:
#127

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