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

Chromium 126.x - Error STATUS_DLL_INIT_FAILED #68

Closed
Uber-1 opened this issue May 4, 2024 · 6 comments
Closed

Chromium 126.x - Error STATUS_DLL_INIT_FAILED #68

Uber-1 opened this issue May 4, 2024 · 6 comments
Labels
bug Something isn't working question Further information is requested

Comments

@Uber-1
Copy link

Uber-1 commented May 4, 2024

The Chromium dev builds ( https://download-chromium.appspot.com/dl/Win ; https://download-chromium.appspot.com/dl/Win_x64 ) don't work with "version.dll". Error STATUS_DLL_INIT_FAILED
Screenshot:
2

@Bush2021 Bush2021 added the invalid This doesn't seem right label May 5, 2024
@Bush2021
Copy link
Owner

Bush2021 commented May 5, 2024

2024-05-04_202910

The official build of Chrome 126 worked fine.

Also, I will consider your issue invalid if you raise it without reading the document.

https://github.com/Bush2021/chrome_plus?tab=readme-ov-file#compatibility

@Bush2021 Bush2021 closed this as not planned Won't fix, can't repro, duplicate, stale May 5, 2024
@Uber-1
Copy link
Author

Uber-1 commented May 5, 2024

Well...
You can just wait until Google merges all changes from Chromium to "master" of Chrome in some weeks. Then we will get the same error on any Chrome 126.
Or you may try to find the reason of the problem now, when we have some time before the "bad 126 comes". Your wish.

This error acts the same way as that was on 118 version (with older dll versions by Shuax). Do you remember? The first bugs were found with this zip releases (versions of early dev of Chromium). Another browsers got the error some weeks later, just when they got update to the same 118 version.

Please, try that zip to check.
Now these Chromium dev still can work with "--no-sandbox" parameter. The same symptom of "118 problem". But can't work without "--no-sandbox" parameter.

@Bush2021 Bush2021 added question Further information is requested help wanted Extra attention is needed and removed invalid This doesn't seem right labels May 5, 2024
@Bush2021
Copy link
Owner

Bush2021 commented May 5, 2024

Well, I guess that is because chromium/chromium@5ea1f70, which enabled WinSboxNoFakeGdiInit. Since Chrome official builds do not use fieldtrial_testing_config.json by default, I mistakenly assume everything works fine.

I am still not sure if this commit will reach the stable releases channel, therefore further observation is required. Anyway, thanks for letting me know.

@Bush2021 Bush2021 reopened this May 5, 2024
@Uber-1
Copy link
Author

Uber-1 commented May 5, 2024

I have no hope on Google. They like to spoil the browser. That is not the first time they make a problem for Chrome++ DLL.
Sorry, I am not a "big guru" of chromium sources, can't help.
I have also found that Vivaldi++ DLL also does not work there and wrote the same issue for ca-x (aka czyt) here. May be that would help for you both. Don't know... Need for another users to confirm the problem.

Bush2021 added a commit that referenced this issue May 5, 2024
Co-authored-by: YorkWaugh <67750590+YorkWaugh@users.noreply.github.com>
@Bush2021
Copy link
Owner

Bush2021 commented May 5, 2024

@Uber-1
Copy link
Author

Uber-1 commented May 5, 2024

try https://github.com/Bush2021/chrome_plus/releases/tag/1.8.7-alpha

Thanks. This works fine for me:
3

@Bush2021 Bush2021 added bug Something isn't working and removed help wanted Extra attention is needed labels May 10, 2024
Bush2021 added a commit that referenced this issue May 14, 2024
fix: disable win32k lockdown to properly load DLLs (#68)"
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants