Quark Oddities

Quark Oddities

22M Downloads

Quark{beta-39} crashes dedicated Forge 1.10.2 build 2007 when placing boat

kreezxil opened this issue · 17 comments

commented

When place a boat for the first time on a brand new world the server kicks the client with this error in the console:

[18:29:47] [Server thread/INFO]: [Kreezxil: Given [Oak Boat] * 1 to Kreezxil]
[18:29:54] [Netty Server IO #1/ERROR] [FML]: NetworkDispatcher exception
java.io.IOException: An existing connection was forcibly closed by the remote host
        at sun.nio.ch.SocketDispatcher.read0(Native Method) ~[?:1.8.0_92]
        at sun.nio.ch.SocketDispatcher.read(Unknown Source) ~[?:1.8.0_92]
        at sun.nio.ch.IOUtil.readIntoNativeBuffer(Unknown Source) ~[?:1.8.0_92]
        at sun.nio.ch.IOUtil.read(Unknown Source) ~[?:1.8.0_92]
        at sun.nio.ch.SocketChannelImpl.read(Unknown Source) ~[?:1.8.0_92]
        at io.netty.buffer.UnpooledUnsafeDirectByteBuf.setBytes(UnpooledUnsafeDirectByteBuf.java:446) ~[UnpooledUnsafeDirectByteBuf.class:?]
        at io.netty.buffer.AbstractByteBuf.writeBytes(AbstractByteBuf.java:881) ~[AbstractByteBuf.class:?]
        at io.netty.channel.socket.nio.NioSocketChannel.doReadBytes(NioSocketChannel.java:225) ~[NioSocketChannel.class:?]
        at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:119) [AbstractNioByteChannel$NioByteUnsafe.class:?]
        at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:511) [NioEventLoop.class:?]
        at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:468) [NioEventLoop.class:?]
        at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:382) [NioEventLoop.class:?]
        at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:354) [NioEventLoop.class:?]
        at io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:116) [SingleThreadEventExecutor$2.class:?]
        at java.lang.Thread.run(Unknown Source) [?:1.8.0_92]
  1. if you stop the server,
  2. then delete quark,
  3. start the server,
  4. then stop the server,
  5. install quark again,
  6. start the server again,
  7. then placing a boat no longer kicks you.

fml server latest log: https://gist.github.com/35216aed8737c4dbd10cd81d7494b23b

The client crash report: http://pastebin.com/CXnhfcAP

fml-client-latest.log
https://gist.github.com/234127500dd73110e7e9609f6f6eac6c

commented

I see quark 40 is out, I'll try it and hope that the pirate ship fix was part of the problem.

commented

Are the configs in the server and client the same?

commented

Yes

-----Original Message-----
From: "Vasco Lavos" [email protected]
Sent: ‎7/‎8/‎2016 12:02 PM
To: "Vazkii/Quark" [email protected]
Cc: "kreezxil" [email protected]; "Author" [email protected]
Subject: Re: [Vazkii/Quark] Quark{beta-39} crashes dedicated Forge 1.10.2build 2007 when placing boat (#110)

Are the configs in the server and client the same?

You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

commented

Can't reproduce. Can you make it happen with just quark?

commented

it's happening with quark 41 too, I just set the BoatSails to false to see what happens. Disabling boat sails solved the issue.

commented

You still haven't answered my question :V

commented

No, it's not doing it when only your mod is installed regardless of the setting. But when your mod is installed with all the other mods in pack, the only way to stop the crash is to disable boat sails.

commented

Are you saying that it occurs with only Quark, and NO OTHER mods? If so, your meaning is unclear.

commented

That's not what I said.

-----Original Message-----
From: "Wire Segal" [email protected]
Sent: ‎7/‎14/‎2016 9:33 PM
To: "Vazkii/Quark" [email protected]
Cc: "kreezxil" [email protected]; "Author" [email protected]
Subject: Re: [Vazkii/Quark] Quark{beta-39} crashes dedicated Forge 1.10.2build 2007 when placing boat (#110)

Are you saying that it occurs with only Quark, and NO OTHER mods? If so, your meaning is unclear.

You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

commented

Well, does it occur when quark is the only mod installed?

commented

No

-----Original Message-----
From: "Wire Segal" [email protected]
Sent: ‎7/‎14/‎2016 10:43 PM
To: "Vazkii/Quark" [email protected]
Cc: "kreezxil" [email protected]; "Author" [email protected]
Subject: Re: [Vazkii/Quark] Quark{beta-39} crashes dedicated Forge 1.10.2build 2007 when placing boat (#110)

Well, does it occur when quark is the only mod installed?

You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

commented

The same thing is happening to everyone on my server. Here's the client crash log: http://pastebin.com/wBDQiFph

The client will crash if the person logs into an area that a boat exists or places one down. It started when I updated the modpack from quark version 47 to 49 and forge version 12.18.1.2026 to 12.18.1.2043, but reverting the update is getting the same crash now. It only happens in multiplayer. When I loaded the world in singleplayer it worked fine and I was able to get rid of all the boats. The server is running now but any time anyone places a boat they'll crash everyone in their area. I'm unable to recreate it in another world. Disabling sails did not fix it for me.

commented

Can you try narrowing it down to which mods cause it? Since @kreezxil confirmed it doesn't happen with only quark, it must be a bug between it and another mod.

commented

I know this isn't helpful but it fixed itself a couple days later. When I was having the crashes I fiddled around with my modlist and forge versions for a good 3 hours and found nothing consistent. It isn't crashing anymore and I can't get it to do it again.

commented

Gah. Well that doesn't help much. I'll keep it open in case someone else comes across it.

commented

Closing because I'm cleaning up the issues page. This issue is really old and probably irrelevant. If you feel i should be re-opened please tell me why.

commented