Et un crash inconue qui vien d'arriver
-
comme décris dans le titre j’ais trouver un bug (je crois que j’ais un pc a bug)
–- Minecraft Crash Report ---- // Don't do that. Time: 14/07/16 00:01 Description: Ticking screen java.lang.NullPointerException: Ticking screen at io.netty.bootstrap.Bootstrap.checkAddress(Bootstrap.java:273) at io.netty.bootstrap.Bootstrap.doConnect(Bootstrap.java:150) at io.netty.bootstrap.Bootstrap.connect(Bootstrap.java:132) at io.netty.bootstrap.Bootstrap.connect(Bootstrap.java:113) at bls.b(SourceFile:165) at bls.a(SourceFile:45) at bls$1.a(SourceFile:144) at eo.l(SourceFile:380) at bls.a(SourceFile:254) at bhj.e(SourceFile:116) at bcx.t(SourceFile:1601) at bcx.av(SourceFile:968) at bcx.a(SourceFile:396) at net.minecraft.client.main.Main.main(SourceFile:124) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:483) at net.minecraft.launchwrapper.Launch.launch(Launch.java:131) at net.minecraft.launchwrapper.Launch.main(Launch.java:27) A detailed walkthrough of the error, its code path and all known details is as follows: --------------------------------------------------------------------------------------- -- Head -- Thread: Client thread Stacktrace: at io.netty.bootstrap.Bootstrap.checkAddress(Bootstrap.java:273) at io.netty.bootstrap.Bootstrap.doConnect(Bootstrap.java:150) at io.netty.bootstrap.Bootstrap.connect(Bootstrap.java:132) at io.netty.bootstrap.Bootstrap.connect(Bootstrap.java:113) at bls.b(SourceFile:165) at bls.a(SourceFile:45) at bls$1.a(SourceFile:144) at eo.l(SourceFile:380) at bls.a(SourceFile:254) at bhj.e(SourceFile:116) -- Affected screen -- Details: Screen name: bhj Stacktrace: at bcx.t(SourceFile:1601) at bcx.av(SourceFile:968) at bcx.a(SourceFile:396) at net.minecraft.client.main.Main.main(SourceFile:124) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:483) at net.minecraft.launchwrapper.Launch.launch(Launch.java:131) at net.minecraft.launchwrapper.Launch.main(Launch.java:27) -- System Details -- Details: Minecraft Version: 1.10 Operating System: Windows 7 (amd64) version 6.1 Java Version: 1.8.0_25, Oracle Corporation Java VM Version: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Oracle Corporation Memory: 238479072 bytes (227 MB) / 393277440 bytes (375 MB) up to 1060372480 bytes (1011 MB) JVM Flags: 6 total; -XX:HeapDumpPath=MojangTricksIntelDriversForPerformance_javaw.exe_minecraft.exe.heapdump -Xmx1G -XX:+UseConcMarkSweepGC -XX:+CMSIncrementalMode -XX:-UseAdaptiveSizePolicy -Xmn128M IntCache: cache: 0, tcache: 78, allocated: 13, tallocated: 95 Launched Version: 1.10-OptiFine_HD_U_C1 LWJGL: 2.9.4 OpenGL: Intel(R) HD Graphics GL version 2.1.0 - Build 8.15.10.2827, Intel GL Caps: Using GL 1.3 multitexturing. Using GL 1.3 texture combiners. Using framebuffer objects because ARB_framebuffer_object is supported and separate blending is supported. Shaders are available because OpenGL 2.1 is supported. VBOs are available because OpenGL 1.5 is supported. Using VBOs: No Is Modded: Very likely; Jar signature invalidated Type: Client (map_client.txt) Resource Packs: Current Language: English (US) Profiler Position: N/A (disabled) CPU: 4x Intel(R) Core(TM) i3 CPU M 370 @ 2.40GHz OptiFine Version: OptiFine_1.10_HD_U_C1 Render Distance Chunks: 8 Mipmaps: 0 Anisotropic Filtering: 1 Antialiasing: 0 Multitexture: false Shaders: null OpenGlVersion: 2.1.0 - Build 8.15.10.2827 OpenGlRenderer: Intel(R) HD Graphics OpenGlVendor: Intel CpuCount: 4et sa surgit allors que je suis sur le menu multi
j’ais un pc a bug j’en suis sur. -
Il y a un problème avec l’adresse d’un serveur.
Netty bug, il y a un npe. -
l’adresse que tu rentre semble ne rien retourner (DNS foireux peut-être?)
-
non car j’etait juste sur la page de ping
-
Oui et ?
Sur cette page il envoie un ping au serveur pour voir le nombre de joueur, s’il est on, etc …
Donc si l’adresse est foireuse ça le fait aussi crasher. -
as allors c’est que un serveur c’est fermer quand il avait fini le ping
-
Pas forcement; je sais pas comment gère minecraft pour leur système de ping serveur, mais si le serveur bloque le port de connexion mais pas le protocole ICMP ca peut poser problème
