Replay Mod Forums

This Thread is locked - no new replies are allowed.

Locked Crash when just watching replays
    • User
    • 21 forum posts
    User79737
    #1

    Aug 20 17, 09:11 AM

    Hey Replaymod team,

    I love your mod! :-)

    Currently, I've got the problem that my Minecraft game will crash after a few seconds into watching my replays. Sadly, I cannot find a crash report. In my "crash-reports" folder, there are a few reports, but all from 2016 and older. So I'll just try and give you as much information without the crash report - and maybe you will be able to tell me how to get the crash report.

    Data

    Minecraft version: 1.12
    Forge version: 1.12
    Replaymod version: 1.12
    Launcher version: 1.6.73-j (old Minecraft launcher)

    Other mods: Worldedit (v1.12), Optifine (v1.12), LunatriusCore & Schematica (both v1.12), LiteLoader (v1.12 - for the Macromod, which sadly doesn't exist in v1.12, so I don't have it installed).

    Java version: Version 8 Update 144 (Build 1.8.0_144-b01)
    OS: Windows 10 Home
    Architecture: x64

    Story

    The problem originally occurred about a week ago, on Minecraft version 1.11.2 (all the mods were 1.11.2 as well). Before that (and I have not actively changed anything), it worked just fine. I created a few well working replays.

    I tried updating everything: Minecraft, Forge, Replaymod, all other Mods, Java, and even my graphics driver. The problem is still the same.
    I also tried reading about the problem virtually EVERYWHERE. I can't find anything on it.

    I have no clue why it happens. I open a replay. It starts normally. After some time (usually after 10 to 30 seconds), the game freezes. I have even tried just waiting a long time: nothing changes. When I quit the game, the launcher opens with no crash report.

    I wanna continue using the Replaymod... I don't like screen recording videos.
    Please help! :-(


    • Developer
    • 1883 forum posts
    User10
    #2

    Aug 20 17, 09:19 AM

    Please post the contents of the fml-client-latest.log file inside the log folder inside your .minecraft folder to some pastebin site and link to the post here.

    Note that this log will only contain information on the last time you started Minecraft, not any previous runs.


    • User
    • 21 forum posts
    User79737
    #3

    Aug 20 17, 09:37 AM

    Thank you for your prompt reply!

    I have started Minecraft, started watching my replay until it crashed, and the closed the Minecraft launcher. I hope this generated a "fresh" log.

    Here you will find it: https://paste.replaymod.com/toqezotina.md

    And something that I forgot to mention above:
    The replay does not always crash at the same time, and it happens in different replays.

    Thanks for helping me!


    • Developer
    • 1883 forum posts
    User10
    #4

    Aug 20 17, 09:45 AM

    That log only lists ReplayMod and WorldEdit, are you sure it's recent? To make sure it's recent, you can delete the file before starting Minecraft.


    • User
    • 21 forum posts
    User79737
    #5

    Aug 20 17, 09:55 AM

    I deleted the file, started Minecraft, entered a single player game, walked around a little, exited the game (after about 10 seconds), started watching my replay, waited until it crashed, and closed Minecraft.

    No new log file has been created.
    So, yes, you seem to be right, the file was not recent.

    The log file I linked to above does state that I am using Minecraft 1.12, right?
    I don't know if that's of any use, but I have only ever started Minecraft 1.12 after I had the crashes in the Replaymod. So I guess the log file is not from today, but should already "include" my problem, right?



    • Developer
    • 1883 forum posts
    User10
    #6

    Aug 20 17, 10:01 AM

    Well, that log ends right after the loading is finished, it doesn't show you going into any replay and therefore also doesn't contain the moment in which the game freezes for you.
    Could you pastebin the log shown in the launcher? It'll contain less information than the fml-client-latest.log file but at least will be a good start.


    • User
    • 21 forum posts
    User79737
    #7

    Aug 20 17, 10:18 AM

    Launcher Log: https://paste.replaymod.com/tuwovuqayo.tex
    Game Output: https://paste.replaymod.com/wapohakequ.tex

    I checked: Sadly, there is still no new fml-client-latest.log file. I'll check again frequently.


    • Developer
    • 1883 forum posts
    User10
    #8

    Aug 20 17, 11:53 AM

    Nothing out of the ordinary in that log.

    Install this mod (drop it into your mods folder). Then, whenever you start Minecraft, another small window will open which has a button labled Create Thread Dump. Once your Minecraft freezes, press that button. It'll generate a thread dump in the text area above the button. Copy that thread dump and pastebin it.


    • User
    • 21 forum posts
    User79737
    #9

    Aug 20 17, 12:15 PM

    Thanks!

    Here's the thread dump: https://paste.replaymod.com/fanajedama.rb


    • Developer
    • 1883 forum posts
    User10
    #10

    Aug 20 17, 12:43 PM

    Could you do the same thing again with this updated version of the same mod?



    • User
    • 21 forum posts
    User79737
    #11

    Aug 20 17, 12:57 PM

    Thread dump with updated version: https://paste.replaymod.com/lotacatuwo.rb

    There's two other things that I could do:
    - Update to the new Minecraft launcher
    - Get 64 bit Java (I haven't done it yet, because java.com recommends the 32 bit version)

    Let me know if you think this could make a difference.


    • Developer
    • 1883 forum posts
    User10
    #12

    Aug 21 17, 12:14 PM

    Could you test whether this version of the ReplayMod solves the problem?


    • User
    • 21 forum posts
    User79737
    #13

    Aug 21 17, 08:08 PM

    Sadly, it doesn't. The replay won't even start.

    Here's the Tread dump: https://paste.replaymod.com/ahawuzidod.sql

    Sorry for my brief answer - I'm in a hurry. Will take more time later!


    • Developer
    • 1883 forum posts
    User10
    #14

    Aug 21 17, 09:16 PM

    Thanks, the thread dump is sufficient.

    That looks like another bug. I'm somewhat surprised that I haven't ever seen it before because it looks rather obvious and likely to happen.
    It should be timing related, does it happen everytime?
    If it does, I'll build another version with that bug fixed as well.
    If it doesn't, is the original bug fixed by above version?


    • User
    • 21 forum posts
    User79737
    #15

    Aug 22 17, 12:13 AM

    Thanks for your help again.

    After ten tries, I am pretty confident to say that it depends on the replay that I want to open: I have three Minecraft 1.12 replays. I have tried to open them four / three / three times. Two of the replays (the one I tried four times and one of the ones that I tried three times) always crashed - I could not even get past the replay selection screen. The other one worked all three times (I have not experimented around with key frames or camera paths, but watching the replay worked).

    The two that did not work were from my single player game, the one that worked is from my multiplayer server - I am not sure if that was't coincidence, though. I'll test that more thoroughly tomorrow evening (then I'll have more time).

    So in summary: I think so far that this might have fixed the original bug (haven't tested it in detail, but it sure seems so at first glance). But it got me a new bug! ;-)

    Thanks again. Good night & see you tomorrow.



    • Developer
    • 1883 forum posts
    User10
    #16

    Aug 22 17, 11:32 AM

    The difference between SP and MP seems about right. The bug depends on the timing of the first few packets which will certainly be different for SP and MP. Just to be on the safe side, this version of the ReplayMod should fix both bugs.


    • User
    • 21 forum posts
    User79737
    #17

    Aug 22 17, 08:41 PM

    Sadly, it doesn't. I have tried a few times now to start the replays: Same outcome as yesterday. It works for the multiplayer replay, but not on the two singleplayer ones.

    Here's the thread dump: https://paste.replaymod.com/comakoqaqe.sql

    Anything I can do to help? Tonight, I actually have some free time... ;-).


    • Developer
    • 1883 forum posts
    User10
    #18

    Aug 23 17, 11:19 AM

    Oh, my bad. I rushed that fix and didn't implement it properly. Here is a version that hopefully has a proper implementation of the fix.

    No, thanks. Unless you can program and fix the problem by yourself, there's nothing more you can do to help than to test the fix.


    • User
    • 21 forum posts
    User79737
    #19

    Aug 23 17, 08:03 PM

    Thank you very much.
    I hope you don't start hating me right now... ;-).

    The game does not crash any more with this version. It does, however, not load the replays (the multiplayer replay works fine, the two single player replays won't start).

    After doubleclicking one of the two SP replays (or selecting one and clicking "Load"), the "Load" button grays out - but apart from that, nothing happens. I can still do everything in the menu. If I select another replay, the "Load" button is not grayed out any more.

    For the MP replay, everything just works out fine again.

    I also found out that if I doubleclick the replays multiple times, the game gets very slow. So it seems that something does happen in the background. Just nothing that I can see.

    Thread dump (after sucessfully running the MP replay, then trying an SP one): https://paste.replaymod.com/zabudojino.sql
    Thread dump #2 (trying the SP replay directly after starting up the game): https://paste.replaymod.com/xuduwoyehe.sql


    • Developer
    • 1883 forum posts
    User10
    #20

    Aug 23 17, 08:22 PM

    I can no longer see anything wrong with those thread dumps.
    Are there any exceptions in the game log / has the fml-client-latest.log appeared by now?
    Could you upload one of those SP replays so I can try myself? Since it seems like there is more than the timing issues I saw initially, I might be able to reproduce it.



    • User
    • 21 forum posts
    User79737
    #21

    Aug 23 17, 08:49 PM

    Okay, too bad. I have sent you a link to download one of the two SP replay files as a private message here in the forum.

    I have just created another replay. It seems to work fine for the new one.
    I'll try around a little more and share my experience here.

    The fml-client-latest.log has not reappeared - I have actually checked every time before posting here.


    • User
    • 21 forum posts
    User79737
    #22

    Aug 23 17, 08:54 PM

    I don't know if it is in any way related:
    My game just crashed when I tried to start the single player mode. The next time I started single player mode, it all worked fine.

    Here's the crash report: https://paste.replaymod.com/wigakosize.sql

    I have since installed Java 64 bit, though. I found out that I can have the two Java versions on my computer at the same time! :-)
    So maybe this has actually got nothing to do with the replay mod. I just thought I'd include everything that might be relevant.


    • Developer
    • 1883 forum posts
    User10
    #23

    Aug 23 17, 09:29 PM

    That crash seems unrelated, I've created a ticket for it and will look at it another time if it doesn't happen more often.

    Now, back to that apparent third bug:
    I can reproduce what you're describing and it looks like it's pretty much this bug but during replay.
    The workaround obviously won't work, so I've build yet another version which also includes the fix for that bug. Using that version, your replay loads fine, at least on my machine.


    • User
    • 21 forum posts
    User79737
    #24

    Aug 23 17, 10:01 PM

    Incredible! It works!! :D

    Thank you SO MUCH!! :D
    I am impressed by your support - this must be the single best tech support that I ever experienced - anywhere!

    Please forgive my one last question:
    I don't know how much effort it is for you to create these new versions of the replay mod. If it's just a matter of copy&paste of two lines of code (or so)... would you mind creating a bug-fixed version 1.11.2 for me as well?

    This would just be for "saving" a 1:50 hours replay that I created in 1.11.2, which also has the bug that you just fixed. If this is a bigger effort for you, please forget about it. I am totally able to recreate that replay.


    • Developer
    • 1883 forum posts
    User10
    #25

    Aug 23 17, 10:48 PM

    Thank you very much for reporting and helping to fix those two bugs. You've been very pleasant to work with.

    Here are the same changes applied to 1.11.2-2.0.0: https://i.johni0702.de/replaymod-1.11.2-2.0.0-3-gedaf74d.jar
    For all other versions. they'll also be in the *-2.0.1 release with lots of other bug fixes which should be coming out within the next few days.



    • User
    • 21 forum posts
    User79737
    #26

    Aug 24 17, 08:23 AM

    Just for having mentioned it: The fix for 1.11.2 also works perfectly.

    Thanks again.
    I am also happy that I could help.

    Since this bug is fixed, from my point of view, this thread can be closed.