Minecraft
  1. Minecraft
  2. MC-103399

/debug command create empty files

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Resolution: Fixed
    • Affects Version/s: Minecraft 1.10, Minecraft 1.10.2, Minecraft 16w33a, Minecraft 16w35a, Minecraft 16w36a, Minecraft 16w38a, Minecraft 16w39a, Minecraft 16w39b, Minecraft 16w39c, Minecraft 16w40a, Minecraft 16w41a, Minecraft 16w42a, Minecraft 16w43a, Minecraft 16w44a
    • Security Level: Minecraft - Public (Viewable by everyone)
    • Labels:
      None
    • Confirmation Status:
      Community Consensus

      Description

      running the /debug command with

      /debug start
      /debug stop

      creates a new file but with no content.


      Code analysis by [Helper] Marcono1234 can be found in this comment.

        Activity

        Hide
        [Mod] Skylinerw added a comment -

        Confirmed.

        Show
        [Mod] Skylinerw added a comment - Confirmed.
        Hide
        [Mod] Anon Ymus added a comment -

        There were no issues to log, so there is nothing in the log file. The file is created to indicate that the session was indeed logged.

        Show
        [Mod] Anon Ymus added a comment - There were no issues to log, so there is nothing in the log file. The file is created to indicate that the session was indeed logged.
        Hide
        [Mod] Skylinerw added a comment -

        What issues would there need to be in order for something to exist within the file? Even when getting warnings in the game output tab ("Something's taking too long! 'root' took aprox 120.008753 ms"), which only occur when debugging is turned on, the file created is empty. Having a non-perfect tickrate also doesn't prompt any content.

        Show
        [Mod] Skylinerw added a comment - What issues would there need to be in order for something to exist within the file? Even when getting warnings in the game output tab ("Something's taking too long! 'root' took aprox 120.008753 ms"), which only occur when debugging is turned on, the file created is empty. Having a non-perfect tickrate also doesn't prompt any content.
        Hide
        [Mod] Anon Ymus added a comment -

        Hmm, I suppose you're right. It seems there should be a witty comment in the file, at the very least.

        Show
        [Mod] Anon Ymus added a comment - Hmm, I suppose you're right. It seems there should be a witty comment in the file, at the very least.
        Hide
        Arcensoth added a comment -

        Confirmed for 1.10 and 1.10.2. These files should always have content, even if the profiling lasts a mere second with no problems to report.

        Show
        Arcensoth added a comment - Confirmed for 1.10 and 1.10.2. These files should always have content, even if the profiling lasts a mere second with no problems to report.
        Hide
        [Helper] Marcono1234 added a comment -

        Please link to this comment in the description

        The following is based on a decompiled version of Minecraft 1.10 using MCP 9.30.

        The reason is very likely that the method net.minecraft.command.CommandDebug.saveProfilerResults(long, int, MinecraftServer) is not closing the FileWriter.

        Show
        [Helper] Marcono1234 added a comment - Please link to this comment in the description The following is based on a decompiled version of Minecraft 1.10 using MCP 9.30. The reason is very likely that the method net.minecraft.command.CommandDebug.saveProfilerResults(long, int, MinecraftServer) is not closing the FileWriter .

          People

          • Assignee:
            [Mojang] Grum (Erik Broes)
            Reporter:
            George Stichel
          • Votes:
            8 Vote for this issue
            Watchers:
            9 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:
              CHK: