search

Blaukovitch / GOOGLE_CHROME_Windows_7

Google Chrome for Windows 7 (cracklab)
The Unlicense
15 stars 1 forks source link

Wery long start the program #2

Open mogileuchik opened 1 month ago

mogileuchik commented 1 month ago

Hi, I used browser on 114 version. Before upgrade to wersion 124 or 125, i see long start the appllication chrome.exe. If I enable logging, the log returned the following: [6716:5088:0518/174414.325:WARNING:chrome_main_delegate.cc(742)] This is Chrome version 125.0.6422.61 (not a warning) [6716:5088:0518/174414.335:VERBOSE1:chrome_browser_cloud_management_controller.cc(97)] DM token = empty [6716:5088:0518/174414.335:VERBOSE1:chrome_browser_cloud_management_controller.cc(103)] Enrollment token = [6716:5088:0518/174414.335:VERBOSE1:chrome_browser_cloud_management_controller.cc(104)] Client ID = 88b3f44f-9ddf-4e34-93b1-83ddf66ea75b [6716:5088:0518/174414.335:VERBOSE2:policy_service_impl.cc(527)] Policy refresh complete [6716:5088:0518/174414.355:VERBOSE1:variations_field_trial_creator_base.cc(77)] VariationsSeedUsage:0 [6716:5088:0518/174414.355:VERBOSE1:variations_field_trial_creator_base.cc(725)] CreateTrialsFromSeed complete with seed.version='20240517-130106.256000' [6716:5088:0518/174414.355:VERBOSE1:variations_field_trial_creator_base.cc(350)] VariationsSetupComplete [6716:6484:0518/174414.355:FATAL:check.cc(375)] Check failed: false. NOTREACHED log messages are omitted in official builds. Sorry! Os: Windows 7 Proffesional x64

i486 commented 1 month ago

How much RAM do you have?

❌ Huge memory VirtualAlloc bug in Windows 7. Affected x64 versions! Need 8Gb of RAM or more for stable workflow.

mogileuchik commented 1 month ago

I have 16 gb ram, but bug it manifests itself both on х86 and х64 versions of browser

Blaukovitch commented 1 month ago

Check failed: false. NOTREACHED log messages are omitted in official builds. Sorry!

This is standard Chrome message for Windows 7 - no worry about.

i see long start the appllication chrome.exe

How much longer does it take to load? May need to delete %LOCALAPPDATA%\Google\Chrome\User Data the folder (if not critical, of course! Backup your tabs and plugins list) - the browser will re-create the folder with settings. Usually, this behavior is related to loading themes and first settings. I haven't seen any technical problems when launching inside the browser itself (waiting for threads and so on). You can also try arguments --single-process, --in-process-gpu.

mogileuchik commented 1 month ago

The first time chrome may not start at all, I didn't check the flags, but I don't think I need it on a multi-core processor, but the second time the program starts, it hangs for 1-2 seconds and the main page loads as usual.

Blaukovitch commented 1 month ago

it hangs for 1-2 seconds and the main page loads as usual.

How CPU load at this time?

The first time chrome may not start at all

Any errors screen? Ex, program stop working.

mogileuchik commented 1 month ago

Sorry for the long absence just now I have a computer with Windows 7 under my hand and this bug floats unfortunately, errors do not give out, but the program loads for the first time for quite a long time, the CPU load does not reach 22%. and after about 10 seconds, Chrome starts up. The second and subsequent chrome launches occur in 2-3 seconds as usual. The same version 122 runs normally. image

Blaukovitch commented 1 month ago

the first time

When Windows 7 is started? And next time - during current session?!

Probably, you can delete user data folder and run again: %LOCALAPPDATA%\Google\Chrome\User Data May be help.

Also, current ver. 125 is affected by this bug?

mogileuchik commented 1 month ago

Thanks, after deleting this folder, chrome worked, but I completely deleted this folder on version 122 after the update. And on the 125th version, chrome began to work like this.However, the first launch is still 125 versions longer than usual.

adeii commented 3 weeks ago

Could you add GetSystemTimePreciseAsFileTime to some future kernel64.exe?

Blaukovitch commented 3 weeks ago

Could you add GetSystemTimePreciseAsFileTime to some future kernel64.exe?

No problems. I marked this issue.

Blaukovitch commented 3 weeks ago

GetSystemTimePreciseAsFileTime

@adeii, also, you can use manually GetSystemTimeAsFileTime instead Precise. No different between.

adeii commented 3 weeks ago

instead Precise. No diffs.

I already use it. But it could be hidden in some DLL/EXE and no visible in CFF Explorer 's imports. So need to rename function and add seven 00 after, in hex editor.