search

3Dickulus / FragM

Derived from https://github.com/Syntopia/Fragmentarium/
GNU General Public License v3.0
344 stars 30 forks source link

Windows build of Fragmentarium 2.5.6 crashes at startup #179

Closed jee7 closed 2 years ago

jee7 commented 2 years ago

Describe the bug Downloaded the latest release of Fragmentarium (v.2.5.6) from here: https://github.com/3Dickulus/FragM/releases. When I unzip and run the Fragmentarium-2.5.6.exe file, I get a "not responding" status and the program fails to start. I initially got a memory access violation error too, but cannot reproduce it.

To Reproduce Steps to reproduce the behavior:

  1. Go to https://github.com/3Dickulus/FragM/releases
  2. Click on Fragmentarium-2.5.6-211212-winex.7z
  3. Download the file
  4. Unzip the package
  5. Run the Fragmentarium-2.5.6.exe file.
  6. Splash screen opens.
  7. See error (program not responding or maybe memory violation)

Expected behavior Fragmentarium should start without problems.

Screenshots

image

image

Desktop (please complete the following information):

Additional context I also tried on Windows 8.1 with non-integrated graphics, same issue. Does not matter if I enable or disable the autorun on the "Autorun on Load" popup, which appears after the program has crashed once before. The exe file does not show the Fragmentarium logo as the file icon either.

3Dickulus commented 2 years ago

ahh the gradient editor requires Qt 5.12 but compiled against 5.9 with no complaints... attempting to update Qt version under wine on linux...

jee7 commented 2 years ago

Don't know if I'm doing something wrong, but now it doesn't start either. No error this time, just doesn't do anything.

https://user-images.githubusercontent.com/3455815/146663367-dcf2dad9-1d37-4435-b99e-3dc6ff63ce18.mp4

3Dickulus commented 2 years ago

Ok not fixed ???

is there a dialog open waiting for input behind the splash screen? with text...

"It looks like the Fragmentarium program crashed during the last startup."
"To prevent repeated crashes, you may choose to disable 'Autorun on Load'."
"This option may be re-enabled through Preferences"

I ask because it happened after a crash on linux wine version, not sure why the splash obscured the dialog but it will sit there forever until "OK"d ... on linux Alt key + LMB click & drag allows moving the splash out of the way.

Will look at setting the timeout on the splash screen earlier and/or rearrange the logic for the "crashed on last run" dialog.

3Dickulus commented 2 years ago

572b925 sets dialog stay on top hint so it can't hide behind splash screen

jee7 commented 2 years ago

Yes, that was it! It works now. Thank you. :)

3Dickulus commented 2 years ago

cheers!