Using the latest version of sync with the latest version of Forge results in a client crash upon entering a shell.

Edit: I am suddenly no longer able to reproduce this. Please disregard this.

I love the lack of a crash report that could be used to debug the crash
there.
On 24 Dec 2014 01:29, "PsionicArchon" [email protected] wrote:

Using the latest version of sync with the latest version of Forge results
in a client crash upon entering a shell.

—
Reply to this email directly or view it on GitHub
#165.

Like seriously, I can't help you if there's no crash report.
On 24 Dec 2014 14:29, "Kay Vin Tee" [email protected] wrote:

I love the lack of a crash report that could be used to debug the crash
there.
On 24 Dec 2014 01:29, "PsionicArchon" [email protected] wrote:

Using the latest version of sync with the latest version of Forge results
in a client crash upon entering a shell.

—
Reply to this email directly or view it on GitHub
#165.

No need to be rude. There is no crash report. The best I could give you is a stack trace but, like I said, I can no longer reproduce the crash. Thus, I cannot profile the jvm hence the "please disregard this".

I was able to reproduce it by jumping into a Sync shell. This would result in the client closing coupled with the above opengl error 9 from my drivers. This has since stopped happening for seemingly no reason. If I can get it to happen again I'll dump some information here.

That would be great, thanks. If you edited your message I wouldn't be able
to have seen your edits cause I'm reading it off the email at the moment.
Apologies for the rudeness, been having a long day.
On 24 Dec 2014 15:17, "PsionicArchon" [email protected] wrote:

No need to be rude. There is no crash report. The best I could give you is
a stack trace but, like I said, I can no longer reproduce the crash. Thus,
I cannot profile the jvm hence the "please disregard this".

I was able to reproduce it by jumping into a Sync shell. This would result
in the client closing coupled with the above opengl error 9 from my
drivers. This has since stopped happening for seemingly no reason. If I can
get it to happen again I'll dump some information here.

—
Reply to this email directly or view it on GitHub
#165 (comment).

It's cool, yea I did edit it last second. Next time I can reproduce it I'll drop a thread dump. Sorry I couldn't provide more info. The last message in the forge logs is the standard 'Couldn't look up profile properties for com.mojang.authlib' message I get every time I hop into a Sync shell. Not even a client closed in a bad state message.

Cheers and happy holidays.

That's unfortunately a standard issue I've been having the entire 1.7 due
to getting skins properly. I've scheduled fixes or changes to try and fix
it for 1.8, plus changes to the mod.

Yeah well, happy holidays to you too.
On 24 Dec 2014 15:27, "PsionicArchon" [email protected] wrote:

It's cool, yea I did edit it last second. Next time I can reproduce it
I'll drop a thread dump. Sorry I couldn't provide more info. The last
message in the forge logs is the standard 'Couldn't look up profile
properties for com.mojang.authlib' message I get every time I hop into a
Sync shell. Not even a client closed in a bad state message.

Cheers and happy holidays.

—
Reply to this email directly or view it on GitHub
#165 (comment).