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

Instant close/crash on Windows 10 Pro on fresh install #23

Open
silbinarywolf opened this issue Oct 25, 2016 · 14 comments
Open

Instant close/crash on Windows 10 Pro on fresh install #23

silbinarywolf opened this issue Oct 25, 2016 · 14 comments
Labels

Comments

@silbinarywolf
Copy link

silbinarywolf commented Oct 25, 2016

  • Windows 10 Pro, Version 1607 (OS Build: 14393.321)
  • i7-2620M 2.7GHZ
  • 8GB of RAM
  • Intel HD Graphics 3000

Never run Milton before, went to give it a quick go and the window opens then immediately closes (still unpainted/white).

Not at all going to be surprised if its Intel HD Graphics 3000 being awful.

@serge-rgb
Copy link
Owner

Milton shouldn't fail silently even if your Intel graphics can't run it. Would you mind pasting the contents of this file? %APPDATA%\MiltonPaint\data\milton.log. Maybe it has more information about the crash.
Thanks for the bug report!

@smasher164
Copy link

I'm having a similar issue. Unfortunately, the crash log at $APPDATA%\MiltonPaint\data\milton.log is a completely empty file.

@silbinarywolf
Copy link
Author

silbinarywolf commented Nov 2, 2016

This is all mine says:

Could not open file for writing prefs
*** [FATAL] ***: 
    Could not create OpenGL context

@theGeekPirate
Copy link

Same thing occurs on my Surface 3, running on Windows 10 Pro with Intel HD Graphics, it instantly crashes.

milton.log is empty.

@ApoorvaJ
Copy link

What folder do you have Milton installed in? Could this be a file access permissions issue?

@serge-rgb
Copy link
Owner

Crashing with "Could not create OpenGL context" probably means that the card doesn't support GL 3.2. The next release will require a lower GL version. However, it still might fail on cards without the extensions required by Milton.

Crashing with an empty milton.log is more interesting... Not sure what it could be. Could be a very long path name triggering an assertion

@theGeekPirate
Copy link

theGeekPirate commented Dec 10, 2016

Unfortunately it has nothing to do with the path, as it also crashes when located inside a folder on my desktop.

Intel HD Graphics supports every feature from OpenGL 3.0 -> 4.4 according to OpenGL Extensions Viewer.

I'm unfamiliar if this tool is correct or not since the vast majority of my computing is done on Linux, but I'd be more than happy to provide any additional information, and in a more timely fashion (GitHub notifications were disabled).

EDIT: GPU Caps Viewer seems to confirm the above regarding OpenGL support.

@serge-rgb
Copy link
Owner

This issue could apply to all sorts of problems because Milton's logging sucks (though it sucks less now!)

Is it still crashing for you? Is there any new information (possibly a non-empty milton.log) with the latest version?

@serge-rgb serge-rgb added the bug label Mar 21, 2017
@theGeekPirate
Copy link

theGeekPirate commented Mar 21, 2017

I can confirm that 1.2.8 works on my Surface without crashing.

Great work!

@silbinarywolf
Copy link
Author

This is still a bug on my GPU.

Could not open file for writing prefs
*** [FATAL] ***: 
	Could not create OpenGL context

It's a driver issue with this graphics card wherein it only supports OpenGL 2.1 on Windows.

See similar issue I had over here:
faiface/pixel#26

@serge-rgb
Copy link
Owner

Milton should at the very least detect when the card does not meet its requirements, instead of just exploding :)
Also, Milton doesn't use that many features on top of GL 2.1. I'm hoping I can lower the requirements a bit to make it work with chips like the HD3000

@silbinarywolf
Copy link
Author

Just ping @ me with various versions if you want to nail down the extensions it does/doesn't have.
Not sure the easiest way to get you such a list.

@Achaean
Copy link

Achaean commented May 28, 2018

Same problem here (with v.1.51 on Win V.10.0.16299.461. Both x64).

Here's my log:

CommandLine is 
Running Milton
Initializing SDL... Done.
Loading preferences... Could not open file for writing prefs
Done.
Creating Milton Window
Created OpenGL context with version 4.5.13521 Compatibility Profile Context 24.20.11016.4
    and GLSL 4.50
Easy Tab Failed to load. Code -3Maximum viewport dimensions, 16384.000000x16384.000000
Vendor string: "ATI Technologies Inc."
Milton: loading file
Increased guid to 1

@CipherBruceH
Copy link

Same problem with v.1.5.1 x64 on latest Windows 10 Pro x64 with Intel HD 3000 graphics (and latest driver available).

CommandLine is 
Running Milton
Initializing SDL... Done.
Loading preferences... Could not open file for writing prefs
Done.
Creating Milton Window
Created OpenGL context with version 3.1.0 - Build 9.17.10.4459
    and GLSL 1.40 - Intel Build 9.17.10.4459
Maximum viewport dimensions, 8192.000000x8192.000000
Vendor string: "Intel"
Milton: loading file
Could not open file!Increased guid to 1

Basic OpenGL info:

OpenGL version - 3.1.0 - Build 9.17.10.4459
Operating system - Windows 10
Renderer - Intel(R) HD Graphics 3000
Shading language version - 1.40 - Intel Build 9.17.10.4459
Vendor - Intel

I've also attached the full glCapsViewer XML report file (glCapsViewer_Report.xml) for my tablet as a .ZIP file.

glCapsViewer_Report.zip

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

7 participants