Jesse Kint

@Alexander Torstling,

Based on your statement that the error is caused by a DNS issue, it suggests the issue was with YOUR realms servers. When MULTIPLE people on MULTIPLE OS in MULTIPLE countries using MULTIPLE internet providers are having issues connecting to ONE service.

What my mind as a professional technical support agent tells me the common item is the issue. That is trouble shooting at it's most basic level. 

I agree that this crash shouldn't be happening, thats why we report these bugs.

i'm sorry if my comment may seem a bit gruff but your statement that "DNS issues can be anywhere on the network" just feels like you are trying to pass blame on what is the common point of the failure.

Everyone in our realm was not able to connect at almost the exact same time then ,now that is it working again, we can connect. This suggests there was an issue with your servers (based on the the program log crashed with, servers provided through amazon).

Here is one thing I found interesting, if you try the same IP it says it can't connect to in realms and it crashes, I put that ip in the add server window and try to connect I got the error it can't connected but then go to try to connect to realms it give the same error but doesn't crash. I tested this a few times. it looks like the error handling code was only loaded when trying to connect to a multiplayer non-realms server. 

thats just my two cents.

@kumasasa I run macOS no updates done on either of my computer

having this issue on both of my macs running 10.13.6

updated java

here is 15 logs in a zip