hs_err_pidxxx.log files keep appearing in root folder macOS Mojave












0















I have been researching hs_err_pidxxx.log files online for weeks and the only information I can find is that they are error logs generated by Java in plain text.



First, these files have been popping up in my root directory (Macintosh HD) sporadically ever since I got this computer. They usually appear while the computer is sleeping, around 2 o'clock in the morning.



Second, I uninstalled the Java runtime from this Mac several months ago and have used "deep uninstall" apps to make sure all Java-related files have been deleted from the computer.



Finally, the files that appear on my computer are not readable. Whether their content is binary or plain text I cannot tell but the contents are pure gibberish and do not contain any readable words.



Could someone help me figure out what these files are and where they are coming from (they do not seem to fit the description, as stated above, of what everyone else's posts on the internet say they are).



Addendum (2019.02.13):



Below are the results of the launchctl command suggested by @MMB yesterday:




Label

com.bitdefender.AuthHelperTool

com.bitdefender.CoreIssues

com.bitdefender.Daemon

com.bitdefender.UpdDaemon

com.bitdefender.agent

com.bitdefender.credentials

com.bitdefender.upgrade

com.teamviewer.Helper

com.vix.cron

net.tunnelblick.tunnelblick.tunnelblickd

org.cups.cupsd

org.serviio.server




Note that BitDefender AntiVirus was not installed at the time this problem started occurring. The latest log file generated, though, is hs_err_pid208.log and PID 208 is com.apple.usbd, not any of the above.










share|improve this question





























    0















    I have been researching hs_err_pidxxx.log files online for weeks and the only information I can find is that they are error logs generated by Java in plain text.



    First, these files have been popping up in my root directory (Macintosh HD) sporadically ever since I got this computer. They usually appear while the computer is sleeping, around 2 o'clock in the morning.



    Second, I uninstalled the Java runtime from this Mac several months ago and have used "deep uninstall" apps to make sure all Java-related files have been deleted from the computer.



    Finally, the files that appear on my computer are not readable. Whether their content is binary or plain text I cannot tell but the contents are pure gibberish and do not contain any readable words.



    Could someone help me figure out what these files are and where they are coming from (they do not seem to fit the description, as stated above, of what everyone else's posts on the internet say they are).



    Addendum (2019.02.13):



    Below are the results of the launchctl command suggested by @MMB yesterday:




    Label

    com.bitdefender.AuthHelperTool

    com.bitdefender.CoreIssues

    com.bitdefender.Daemon

    com.bitdefender.UpdDaemon

    com.bitdefender.agent

    com.bitdefender.credentials

    com.bitdefender.upgrade

    com.teamviewer.Helper

    com.vix.cron

    net.tunnelblick.tunnelblick.tunnelblickd

    org.cups.cupsd

    org.serviio.server




    Note that BitDefender AntiVirus was not installed at the time this problem started occurring. The latest log file generated, though, is hs_err_pid208.log and PID 208 is com.apple.usbd, not any of the above.










    share|improve this question



























      0












      0








      0








      I have been researching hs_err_pidxxx.log files online for weeks and the only information I can find is that they are error logs generated by Java in plain text.



      First, these files have been popping up in my root directory (Macintosh HD) sporadically ever since I got this computer. They usually appear while the computer is sleeping, around 2 o'clock in the morning.



      Second, I uninstalled the Java runtime from this Mac several months ago and have used "deep uninstall" apps to make sure all Java-related files have been deleted from the computer.



      Finally, the files that appear on my computer are not readable. Whether their content is binary or plain text I cannot tell but the contents are pure gibberish and do not contain any readable words.



      Could someone help me figure out what these files are and where they are coming from (they do not seem to fit the description, as stated above, of what everyone else's posts on the internet say they are).



      Addendum (2019.02.13):



      Below are the results of the launchctl command suggested by @MMB yesterday:




      Label

      com.bitdefender.AuthHelperTool

      com.bitdefender.CoreIssues

      com.bitdefender.Daemon

      com.bitdefender.UpdDaemon

      com.bitdefender.agent

      com.bitdefender.credentials

      com.bitdefender.upgrade

      com.teamviewer.Helper

      com.vix.cron

      net.tunnelblick.tunnelblick.tunnelblickd

      org.cups.cupsd

      org.serviio.server




      Note that BitDefender AntiVirus was not installed at the time this problem started occurring. The latest log file generated, though, is hs_err_pid208.log and PID 208 is com.apple.usbd, not any of the above.










      share|improve this question
















      I have been researching hs_err_pidxxx.log files online for weeks and the only information I can find is that they are error logs generated by Java in plain text.



      First, these files have been popping up in my root directory (Macintosh HD) sporadically ever since I got this computer. They usually appear while the computer is sleeping, around 2 o'clock in the morning.



      Second, I uninstalled the Java runtime from this Mac several months ago and have used "deep uninstall" apps to make sure all Java-related files have been deleted from the computer.



      Finally, the files that appear on my computer are not readable. Whether their content is binary or plain text I cannot tell but the contents are pure gibberish and do not contain any readable words.



      Could someone help me figure out what these files are and where they are coming from (they do not seem to fit the description, as stated above, of what everyone else's posts on the internet say they are).



      Addendum (2019.02.13):



      Below are the results of the launchctl command suggested by @MMB yesterday:




      Label

      com.bitdefender.AuthHelperTool

      com.bitdefender.CoreIssues

      com.bitdefender.Daemon

      com.bitdefender.UpdDaemon

      com.bitdefender.agent

      com.bitdefender.credentials

      com.bitdefender.upgrade

      com.teamviewer.Helper

      com.vix.cron

      net.tunnelblick.tunnelblick.tunnelblickd

      org.cups.cupsd

      org.serviio.server




      Note that BitDefender AntiVirus was not installed at the time this problem started occurring. The latest log file generated, though, is hs_err_pid208.log and PID 208 is com.apple.usbd, not any of the above.







      mac java






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Feb 13 at 22:48







      PBear.SF

















      asked Jan 31 at 19:12









      PBear.SFPBear.SF

      12




      12






















          1 Answer
          1






          active

          oldest

          votes


















          0














          These occur when a JVM crashes and these are the equivalent of core files for debugging. You can't read them because they're likely from a service launched by root.



          Regardless, it appears you still have Java on your system, which isn't too surprising given some vendors with Java-based apps shipped their own JVM so they didn't have version issues or require the user to manually install Java in addition to their own app. If memory serves, Crashplan, a backup app used to do this, but Java has fallen out of favor, so it's probably an older app or service (which also probably explains why it is crashing).



          There's an easy resolution via the Terminal, though. Take the PID number (xxx) from the log filename and search the process table for it. For example, if the PID were 13924, then



          ~ ps -e | grep 13924
          13924 ?? 0:07.79 /Applications/Arduino.app/Contents/MacOS/Arduino


          I don't believe I have any of said apps on my system anymore, so I just used the Arduino app as an example, but with that information, you should be able to determine where the Java runtime is located. From there you can figure out the proper way to uninstall the guilty app.






          share|improve this answer


























          • Thanks for the answer, @MMB The only results for the code above, at the time, pointed to the built-in file for the ColorSync daemon, which confused me. A new log file appeared today and the results for the ps command this time returned: 208 ?? 0:00.06 /usr/libexec/usbd. Again, a built-in macOS file, not an application. How could macOS' own usb daemon cause a Java error?

            – PBear.SF
            Feb 11 at 17:57













          • Puzzling. According the man pages, usbd arrived in 10.9 as a way for iOS devices to charge and send notifications.

            – MMB
            Feb 12 at 21:18











          • Let's tackle this a different way. Given Apple's disdain for Java, let us assume the file isn't coming from Apple software. You also said the files are created around 2AM, which suggests something launched. Try the following command, which the results of which you might want to append to your original question: sudo launchctl list | cut -f3 | grep -v com.apple | sort

            – MMB
            Feb 12 at 22:08













          • The above command will generate a list of services launched by third-party software that you have installed. Note that since the sudo command is issued, you'll need to enter your password.

            – MMB
            Feb 12 at 22:32











          • Four Java crash logs later @MMB and one finally appeared today with a useful PID - revealing that there is indeed a JRE installed on my Mac, contained in the Serviio Media Server. I plan to uninstall Serviio, which should stop the Java error logs from appearing, but I am beginning to fear that these Java logs are just a symptom of my main problem and not the cause of what is making my computer crash at 2:10 AM every one to three days, during sleep mode. I have looked at many diverse crash logs now, in the Console, and every one that has a time stamp of 2:10 AM is in unreadable text or code.

            – PBear.SF
            Feb 17 at 18:16













          Your Answer








          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "3"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1400718%2fhs-err-pidxxx-log-files-keep-appearing-in-root-folder-macos-mojave%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          0














          These occur when a JVM crashes and these are the equivalent of core files for debugging. You can't read them because they're likely from a service launched by root.



          Regardless, it appears you still have Java on your system, which isn't too surprising given some vendors with Java-based apps shipped their own JVM so they didn't have version issues or require the user to manually install Java in addition to their own app. If memory serves, Crashplan, a backup app used to do this, but Java has fallen out of favor, so it's probably an older app or service (which also probably explains why it is crashing).



          There's an easy resolution via the Terminal, though. Take the PID number (xxx) from the log filename and search the process table for it. For example, if the PID were 13924, then



          ~ ps -e | grep 13924
          13924 ?? 0:07.79 /Applications/Arduino.app/Contents/MacOS/Arduino


          I don't believe I have any of said apps on my system anymore, so I just used the Arduino app as an example, but with that information, you should be able to determine where the Java runtime is located. From there you can figure out the proper way to uninstall the guilty app.






          share|improve this answer


























          • Thanks for the answer, @MMB The only results for the code above, at the time, pointed to the built-in file for the ColorSync daemon, which confused me. A new log file appeared today and the results for the ps command this time returned: 208 ?? 0:00.06 /usr/libexec/usbd. Again, a built-in macOS file, not an application. How could macOS' own usb daemon cause a Java error?

            – PBear.SF
            Feb 11 at 17:57













          • Puzzling. According the man pages, usbd arrived in 10.9 as a way for iOS devices to charge and send notifications.

            – MMB
            Feb 12 at 21:18











          • Let's tackle this a different way. Given Apple's disdain for Java, let us assume the file isn't coming from Apple software. You also said the files are created around 2AM, which suggests something launched. Try the following command, which the results of which you might want to append to your original question: sudo launchctl list | cut -f3 | grep -v com.apple | sort

            – MMB
            Feb 12 at 22:08













          • The above command will generate a list of services launched by third-party software that you have installed. Note that since the sudo command is issued, you'll need to enter your password.

            – MMB
            Feb 12 at 22:32











          • Four Java crash logs later @MMB and one finally appeared today with a useful PID - revealing that there is indeed a JRE installed on my Mac, contained in the Serviio Media Server. I plan to uninstall Serviio, which should stop the Java error logs from appearing, but I am beginning to fear that these Java logs are just a symptom of my main problem and not the cause of what is making my computer crash at 2:10 AM every one to three days, during sleep mode. I have looked at many diverse crash logs now, in the Console, and every one that has a time stamp of 2:10 AM is in unreadable text or code.

            – PBear.SF
            Feb 17 at 18:16


















          0














          These occur when a JVM crashes and these are the equivalent of core files for debugging. You can't read them because they're likely from a service launched by root.



          Regardless, it appears you still have Java on your system, which isn't too surprising given some vendors with Java-based apps shipped their own JVM so they didn't have version issues or require the user to manually install Java in addition to their own app. If memory serves, Crashplan, a backup app used to do this, but Java has fallen out of favor, so it's probably an older app or service (which also probably explains why it is crashing).



          There's an easy resolution via the Terminal, though. Take the PID number (xxx) from the log filename and search the process table for it. For example, if the PID were 13924, then



          ~ ps -e | grep 13924
          13924 ?? 0:07.79 /Applications/Arduino.app/Contents/MacOS/Arduino


          I don't believe I have any of said apps on my system anymore, so I just used the Arduino app as an example, but with that information, you should be able to determine where the Java runtime is located. From there you can figure out the proper way to uninstall the guilty app.






          share|improve this answer


























          • Thanks for the answer, @MMB The only results for the code above, at the time, pointed to the built-in file for the ColorSync daemon, which confused me. A new log file appeared today and the results for the ps command this time returned: 208 ?? 0:00.06 /usr/libexec/usbd. Again, a built-in macOS file, not an application. How could macOS' own usb daemon cause a Java error?

            – PBear.SF
            Feb 11 at 17:57













          • Puzzling. According the man pages, usbd arrived in 10.9 as a way for iOS devices to charge and send notifications.

            – MMB
            Feb 12 at 21:18











          • Let's tackle this a different way. Given Apple's disdain for Java, let us assume the file isn't coming from Apple software. You also said the files are created around 2AM, which suggests something launched. Try the following command, which the results of which you might want to append to your original question: sudo launchctl list | cut -f3 | grep -v com.apple | sort

            – MMB
            Feb 12 at 22:08













          • The above command will generate a list of services launched by third-party software that you have installed. Note that since the sudo command is issued, you'll need to enter your password.

            – MMB
            Feb 12 at 22:32











          • Four Java crash logs later @MMB and one finally appeared today with a useful PID - revealing that there is indeed a JRE installed on my Mac, contained in the Serviio Media Server. I plan to uninstall Serviio, which should stop the Java error logs from appearing, but I am beginning to fear that these Java logs are just a symptom of my main problem and not the cause of what is making my computer crash at 2:10 AM every one to three days, during sleep mode. I have looked at many diverse crash logs now, in the Console, and every one that has a time stamp of 2:10 AM is in unreadable text or code.

            – PBear.SF
            Feb 17 at 18:16
















          0












          0








          0







          These occur when a JVM crashes and these are the equivalent of core files for debugging. You can't read them because they're likely from a service launched by root.



          Regardless, it appears you still have Java on your system, which isn't too surprising given some vendors with Java-based apps shipped their own JVM so they didn't have version issues or require the user to manually install Java in addition to their own app. If memory serves, Crashplan, a backup app used to do this, but Java has fallen out of favor, so it's probably an older app or service (which also probably explains why it is crashing).



          There's an easy resolution via the Terminal, though. Take the PID number (xxx) from the log filename and search the process table for it. For example, if the PID were 13924, then



          ~ ps -e | grep 13924
          13924 ?? 0:07.79 /Applications/Arduino.app/Contents/MacOS/Arduino


          I don't believe I have any of said apps on my system anymore, so I just used the Arduino app as an example, but with that information, you should be able to determine where the Java runtime is located. From there you can figure out the proper way to uninstall the guilty app.






          share|improve this answer















          These occur when a JVM crashes and these are the equivalent of core files for debugging. You can't read them because they're likely from a service launched by root.



          Regardless, it appears you still have Java on your system, which isn't too surprising given some vendors with Java-based apps shipped their own JVM so they didn't have version issues or require the user to manually install Java in addition to their own app. If memory serves, Crashplan, a backup app used to do this, but Java has fallen out of favor, so it's probably an older app or service (which also probably explains why it is crashing).



          There's an easy resolution via the Terminal, though. Take the PID number (xxx) from the log filename and search the process table for it. For example, if the PID were 13924, then



          ~ ps -e | grep 13924
          13924 ?? 0:07.79 /Applications/Arduino.app/Contents/MacOS/Arduino


          I don't believe I have any of said apps on my system anymore, so I just used the Arduino app as an example, but with that information, you should be able to determine where the Java runtime is located. From there you can figure out the proper way to uninstall the guilty app.







          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited Feb 12 at 21:17

























          answered Feb 3 at 10:07









          MMBMMB

          45326




          45326













          • Thanks for the answer, @MMB The only results for the code above, at the time, pointed to the built-in file for the ColorSync daemon, which confused me. A new log file appeared today and the results for the ps command this time returned: 208 ?? 0:00.06 /usr/libexec/usbd. Again, a built-in macOS file, not an application. How could macOS' own usb daemon cause a Java error?

            – PBear.SF
            Feb 11 at 17:57













          • Puzzling. According the man pages, usbd arrived in 10.9 as a way for iOS devices to charge and send notifications.

            – MMB
            Feb 12 at 21:18











          • Let's tackle this a different way. Given Apple's disdain for Java, let us assume the file isn't coming from Apple software. You also said the files are created around 2AM, which suggests something launched. Try the following command, which the results of which you might want to append to your original question: sudo launchctl list | cut -f3 | grep -v com.apple | sort

            – MMB
            Feb 12 at 22:08













          • The above command will generate a list of services launched by third-party software that you have installed. Note that since the sudo command is issued, you'll need to enter your password.

            – MMB
            Feb 12 at 22:32











          • Four Java crash logs later @MMB and one finally appeared today with a useful PID - revealing that there is indeed a JRE installed on my Mac, contained in the Serviio Media Server. I plan to uninstall Serviio, which should stop the Java error logs from appearing, but I am beginning to fear that these Java logs are just a symptom of my main problem and not the cause of what is making my computer crash at 2:10 AM every one to three days, during sleep mode. I have looked at many diverse crash logs now, in the Console, and every one that has a time stamp of 2:10 AM is in unreadable text or code.

            – PBear.SF
            Feb 17 at 18:16





















          • Thanks for the answer, @MMB The only results for the code above, at the time, pointed to the built-in file for the ColorSync daemon, which confused me. A new log file appeared today and the results for the ps command this time returned: 208 ?? 0:00.06 /usr/libexec/usbd. Again, a built-in macOS file, not an application. How could macOS' own usb daemon cause a Java error?

            – PBear.SF
            Feb 11 at 17:57













          • Puzzling. According the man pages, usbd arrived in 10.9 as a way for iOS devices to charge and send notifications.

            – MMB
            Feb 12 at 21:18











          • Let's tackle this a different way. Given Apple's disdain for Java, let us assume the file isn't coming from Apple software. You also said the files are created around 2AM, which suggests something launched. Try the following command, which the results of which you might want to append to your original question: sudo launchctl list | cut -f3 | grep -v com.apple | sort

            – MMB
            Feb 12 at 22:08













          • The above command will generate a list of services launched by third-party software that you have installed. Note that since the sudo command is issued, you'll need to enter your password.

            – MMB
            Feb 12 at 22:32











          • Four Java crash logs later @MMB and one finally appeared today with a useful PID - revealing that there is indeed a JRE installed on my Mac, contained in the Serviio Media Server. I plan to uninstall Serviio, which should stop the Java error logs from appearing, but I am beginning to fear that these Java logs are just a symptom of my main problem and not the cause of what is making my computer crash at 2:10 AM every one to three days, during sleep mode. I have looked at many diverse crash logs now, in the Console, and every one that has a time stamp of 2:10 AM is in unreadable text or code.

            – PBear.SF
            Feb 17 at 18:16



















          Thanks for the answer, @MMB The only results for the code above, at the time, pointed to the built-in file for the ColorSync daemon, which confused me. A new log file appeared today and the results for the ps command this time returned: 208 ?? 0:00.06 /usr/libexec/usbd. Again, a built-in macOS file, not an application. How could macOS' own usb daemon cause a Java error?

          – PBear.SF
          Feb 11 at 17:57







          Thanks for the answer, @MMB The only results for the code above, at the time, pointed to the built-in file for the ColorSync daemon, which confused me. A new log file appeared today and the results for the ps command this time returned: 208 ?? 0:00.06 /usr/libexec/usbd. Again, a built-in macOS file, not an application. How could macOS' own usb daemon cause a Java error?

          – PBear.SF
          Feb 11 at 17:57















          Puzzling. According the man pages, usbd arrived in 10.9 as a way for iOS devices to charge and send notifications.

          – MMB
          Feb 12 at 21:18





          Puzzling. According the man pages, usbd arrived in 10.9 as a way for iOS devices to charge and send notifications.

          – MMB
          Feb 12 at 21:18













          Let's tackle this a different way. Given Apple's disdain for Java, let us assume the file isn't coming from Apple software. You also said the files are created around 2AM, which suggests something launched. Try the following command, which the results of which you might want to append to your original question: sudo launchctl list | cut -f3 | grep -v com.apple | sort

          – MMB
          Feb 12 at 22:08







          Let's tackle this a different way. Given Apple's disdain for Java, let us assume the file isn't coming from Apple software. You also said the files are created around 2AM, which suggests something launched. Try the following command, which the results of which you might want to append to your original question: sudo launchctl list | cut -f3 | grep -v com.apple | sort

          – MMB
          Feb 12 at 22:08















          The above command will generate a list of services launched by third-party software that you have installed. Note that since the sudo command is issued, you'll need to enter your password.

          – MMB
          Feb 12 at 22:32





          The above command will generate a list of services launched by third-party software that you have installed. Note that since the sudo command is issued, you'll need to enter your password.

          – MMB
          Feb 12 at 22:32













          Four Java crash logs later @MMB and one finally appeared today with a useful PID - revealing that there is indeed a JRE installed on my Mac, contained in the Serviio Media Server. I plan to uninstall Serviio, which should stop the Java error logs from appearing, but I am beginning to fear that these Java logs are just a symptom of my main problem and not the cause of what is making my computer crash at 2:10 AM every one to three days, during sleep mode. I have looked at many diverse crash logs now, in the Console, and every one that has a time stamp of 2:10 AM is in unreadable text or code.

          – PBear.SF
          Feb 17 at 18:16







          Four Java crash logs later @MMB and one finally appeared today with a useful PID - revealing that there is indeed a JRE installed on my Mac, contained in the Serviio Media Server. I plan to uninstall Serviio, which should stop the Java error logs from appearing, but I am beginning to fear that these Java logs are just a symptom of my main problem and not the cause of what is making my computer crash at 2:10 AM every one to three days, during sleep mode. I have looked at many diverse crash logs now, in the Console, and every one that has a time stamp of 2:10 AM is in unreadable text or code.

          – PBear.SF
          Feb 17 at 18:16




















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Super User!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1400718%2fhs-err-pidxxx-log-files-keep-appearing-in-root-folder-macos-mojave%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          flock() on closed filehandle LOCK_FILE at /usr/bin/apt-mirror

          Mangá

          Eduardo VII do Reino Unido