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

Access Violation on startup #660

Closed
Seriousnes opened this issue Oct 3, 2017 · 4 comments
Closed

Access Violation on startup #660

Seriousnes opened this issue Oct 3, 2017 · 4 comments

Comments

@Seriousnes
Copy link

With the update to version 1.4.64, if PoB is closed while window is on the non-primary monitor, PoB crashes with an access violation (see attached image)
crit error

@Openarl
Copy link
Owner

Openarl commented Oct 3, 2017

Were you experiencing #336 before 1.4.64? If so, then we'll continue in there, as this is almost certainly related.

@Seriousnes
Copy link
Author

Nope, I have not experienced any of the issues outlined in #336.

I can provide more details of my pc setup tomorrow when I'm back at work, however iirc I have my main monitor using an ATI graphics card and second monitor using on-board intel graphics. PC is on Windows 10.

I have no issues moving or resizing PoB between monitors, the startup error only occurs if the application was closed on the second monitor.

Additionally removing the contents of Launch.cfg didn't help, but deleting Settings.xml did seem to fix the issue (e.g. close PoB > delete Settings.xml > open PoB > same AV > open PoB again > opens without any problems)

@Openarl
Copy link
Owner

Openarl commented Oct 4, 2017

That is quite unusual. As far as I can tell, the crash is occurring within your graphics driver during OpenGL initialisation; I have no idea why, though, and the only thing I can really suggest at the moment is updating your drivers.

@Jinnai
Copy link

Jinnai commented Oct 6, 2017

I'm having exactly the same issue. I tried upgrade my drivers but it didn't solve it.

@Seriousnes Seriousnes closed this as not planned Won't fix, can't repro, duplicate, stale Dec 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants