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

InitSafe() aborts with SIGILL #121

Open
noio opened this Issue Sep 16, 2016 · 9 comments

Comments

Projects
None yet
4 participants
@noio

noio commented Sep 16, 2016

A lot of our users are having the game crash with the following error:

ExecutionEngineException: SIGILL
at (wrapper managed-to-native) Steamworks.NativeMethods:SteamAPI_InitSafe ()
at Steamworks.SteamAPI.Init () [0x00000] in <filename unknown>:0 
at SteamManager.Awake () [0x00000] in <filename unknown>:0 
UnityEngine.GameObject:Internal_AddComponentWithType(Type)
UnityEngine.GameObject:AddComponent(Type)
UnityEngine.GameObject:AddComponent()
SteamManager:get_Instance()
SteamManager:get_Initialized()
<WaitForSteam>c__IteratorA3:MoveNext()
UnityEngine.SetupCoroutine:InvokeMoveNext(IEnumerator, IntPtr)
UnityEngine.MonoBehaviour:StartCoroutine_Auto(IEnumerator)
UnityEngine.MonoBehaviour:StartCoroutine(IEnumerator)
SteamWrapper:Init()
Managers:Init(Manager)
Managers:InitAll()
Managers:Awake()

I have found similar reports:

Do you think there is a generic cause to these? And do you have any idea as for how to fix them?

If this is definitely not an issue with Steamworks.NET, please close this GitHub issue, in that case apologies for going through this channel with a question ;).

EDIT: Apologies! Just found the topic on the SteamworksDevelopment discussion board around this topic. Guess it doesn't show up on Google because it's walled off without login. For those with access:

@rlabrecque

This comment has been minimized.

Owner

rlabrecque commented Sep 16, 2016

Hey noio, do you have any specific helpful users that could help us track this down? I never could reproduce it on many different computers.

Basically the first step is to try Valves steam_api.cs from the Steamworks SDK. It will likely require some 20-40 minutes worth of time disabling Steamworks.NET and integrating Valves steam_api.cs. If there's any chance that you could do that and then put up a beta branch for those users to try out it would be awesome!

@noio

This comment has been minimized.

noio commented Sep 16, 2016

Ok! It's worth a shot.

Where do I find steam_api.cs ? I couldn't find it in the latest SDK download (1.37), maybe I'm looking wrong?

@rlabrecque

This comment has been minimized.

Owner

rlabrecque commented Sep 16, 2016

Oh sorry, I wrote that really late, it's actually steam_api_interop.cs in the SDK.

Make sure you're using the latest steam_api.dll from that SDK version as well.

@noio

This comment has been minimized.

noio commented Sep 18, 2016

Just as an update. I have a few users who consistently run into the issue, how could they help?

One is running a Pentium D, another one a Pentium 4.

@WazWaz

This comment has been minimized.

WazWaz commented Nov 28, 2016

The user I have with this problem is running Windows XP, if that helps.

@rlabrecque

This comment has been minimized.

Owner

rlabrecque commented Dec 17, 2016

Were you ever able to look into this more yet @noio ?

@noio

This comment has been minimized.

noio commented Dec 21, 2016

Not yet! I opted for a workaround, I uploaded a build without Steam integration to a beta branch for the 3-4 users with this problem.

I guess it's a group that will get even smaller over time, as it seems to be hardware bound.

@IQpierce

This comment has been minimized.

IQpierce commented Mar 20, 2017

Is this issue considered resolved? Or is it still outstanding?

@rlabrecque

This comment has been minimized.

Owner

rlabrecque commented Mar 20, 2017

It comes up less and less, I'm pretty sure it's actually on Valve's side, but I've never been able to reproduce it. It seems to be a hardware spec issue, It only ever really happens to people running with really old <=Pentium 4 era hardware.

I'm keeping it open for now though until we can get some kind of confirmation that it's fixed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment