Open Zero3K opened 10 months ago
It looks like the UI is not being displayed?
Correct. It keeps launching itself until ReactOS crashes and also states that "Chromium is unresponsive. Would you like to relaunch it?".
I wonder if it is a bug in your build of Chromium or a bug in ReactOS.
I am currently unable to confirm this, as I have not installed a ReactOS virtual machine to test this scenario.
Okay. I think it also affects Windows 2000 from what I have seen.
I don't think it will run on Win2000 because there are still a few APIs that I haven't implemented yet.
Would a debug log made while running it under ReactOS help?
I'm afraid it's not very useful. I need to find a virtual machine to debug it.
You can easily make one.
It looks to be a ReactOS bug according to the attached debug log.
Maybe someone could make a ticket regarding it on https://jira.reactos.org.
The new version doesn't give me the error dialog box, it just keeps loading itself with no UI showing.
Is there anything I can do to help?
Do you have a VMware image of ReactOS? This way I can run it directly for testing.
Not VirtualBox?
ok, i try it
Did you find anything?
Sorry, I've been quite busy these days and haven't had a chance to take a look yet.
I think making a ticket on https://jira.reactos.org would be a start just in case it is a ReactOS issue.
ZERO3K STOP HARASSING THIS GUY HOLY FUCK
Bro reacted 3 minutes ago, bro's sleep deprived
I won't comment in here any more until he responds with his findings.
The same thing happens on Windows XP if WineD3D installed. I think it's because dxgi.dll. This file isn't in original Windows XP, but it is in ReactOS. May be replace dxgi.dll on something like axgi.dll with Hex Editor in chrome.dll allow you to solve the problem.
dxgi.dll isn't included by default in ReactOS.
It keeps launching itself when ran under ReactOS. Here's a screenshot of the issue: