Thorium

[NotHereToPlayGames]

9 minutes ago, Dixel said:

topic that was locked for a good reason

I didn't see that it was locked.  Thanks.

I was googling for vulkan issues on XP x64 and that thread was in the top three results.

[NotHereToPlayGames]

18 minutes ago, Dixel said:

Not a word about Vulkan, of course.

Agreed!  I'm honestly not finding much of anything.

But I can report with 123,456,789.0% accuracy that the ONLY ONLY ONLY time that I get these FIRST LAUNCH CRASHES is when I take the advice of removing "vulkan" .dll's.

That advice always comes from "users" and NEVER "developers".

No offense.  Again, I can only report WHAT I WITNESS.

And sure, Thorium and Supermium and 360Chrome and Ungoogled are "usable" without these "vulkan" files.

But I hibernate several times per day!  And having to go into the OS's Task Manager to "kill" a process just to relaunch it after a CRASH is something I really have no interest in doing "for the sake of removing two .dll's that people keep insisting I do not need".

Edited August 14, 2024 by NotHereToPlayGames

[NotHereToPlayGames]

Technically, I shouldn't say that PEOPLE (it implies multiple) keep INSISTING that I do not need.

There is only TWO PEOPLE and they are RELENTLESS in this pursuit.  Downright RELENTLESS.

Edited August 14, 2024 by NotHereToPlayGames

[Dixel]

11 hours ago, NotHereToPlayGames said:

the ONLY ONLY ONLY time that I get these FIRST LAUNCH CRASHES is when I take the advice of removing "vulkan" .dll's.

Shoot a short video like @66cats does, add here so we can see.

[NotHereToPlayGames]

Maybe.  Kind of not really worth my time.  But maybe.  Depends on how bored I get in the next day or two, lol.

Granted, the video may be 360Chrome and not Thorium - will that still serve as your PROOF that your "advice" does NOT pertain to MY computer ???

[NotHereToPlayGames]

I will post a 360Chrome video of this first launch crash.  I do not keep Thorium and Supermium around, only test in VM to see if they are "ungoogled" or not.  BUT THAT HAS TO PUT THIS D#MN RELENTLESSNESS TO BED!  "Enough is enough."

Edited August 14, 2024 by NotHereToPlayGames

[Dixel]

11 hours ago, NotHereToPlayGames said:

BUT THAT HAS TO PUT THIS D#MN RELENTLESSNESS TO BED!

First do the following to make sure.

From extensive research on this topic, I understand that all those .dlls are a delay load dependency, not an immediate startup dependency.

Chrome will only load them if it gets a proper Vulkan config from your setup.

Get the latest XP capable GPUz, see if you have a Vilkan capable system.

Example:

 

 

[NotHereToPlayGames]

I know that UCyborg also had this issue.  Also both in Thorium and in 360Chrome.  https://msfn.org/board/topic/186133-thorium/?do=findComment&comment=1265727

[Dixel]

11 hours ago, NotHereToPlayGames said:

I do not keep Thorium and Supermium around, only test in VM to see if they are "ungoogled" or not. 

Pfffffff! That doesn't count even for one second, only real hardware does.

[Dixel]

11 hours ago, NotHereToPlayGames said:

I know that UCyborg also had this issue.  Also both in Thorium and in 360Chrome.  https://msfn.org/board/topic/186133-thorium/?do=findComment&comment=1265727

How is this related to Vulkan DLLs?

[NotHereToPlayGames]

3 minutes ago, Dixel said:

Chrome will only load them if it gets a proper Vulkan config from your setup.

Not to cloud the issue, but I have never confirmed that the .dll's are actually LOADED as a DEPENDENCY.

Only that their PRESENCE is required in ALL Chrome/Chromium-based browsers EVER used on my home Dell XPS 8700 (7800?, have to look when I get home).

I don't mind uploading a video because the folks that keep telling other people to delete "vulkan" files needs to realize that their "advice" may be BAD ADVICE.

It certainly is for MY computer.  But only for XP x64.

[NotHereToPlayGames]

4 minutes ago, Dixel said:

Pfffffff! That doesn't count even for one second, only real hardware does.

Even Thorium has crashed on REAL HARDWARE ALSO.  Only in XP x64 and only first launch after reboot or hibernate.

UNFORTUNATE for YOUR PROOF, that real harware has since been upgraded to Win10.

[NotHereToPlayGames]

4 minutes ago, Dixel said:

How is this related to Vulkan DLLs?

Good point.  He posts later down that he KEEPS the vulkan files, that he only deletes D3DCompiler_47.dll.

[Saxon]

11 hours ago, NotHereToPlayGames said:

I don't mind uploading a video because the folks that keep telling other people to delete "vulkan" files needs to realize that their "advice" may be BAD ADVICE.

It certainly is for MY computer.  But only for XP x64.

Why "bad advice"? So far, no one reported any problems. The link to UCyborg's post, I just read it, he talks about another matter.

Saxon is again just being objective, no sides.

[Saxon]

11 hours ago, NotHereToPlayGames said:

Good point.  He posts later down that he KEEPS the vulkan files, that he only deletes D3DCompiler_47.dll.

Of course he does, his GPU, and the OS he's on, are Vulkan capable, unlike yours,