Jump to content


Photo

Recent repeated crashes


    4 replies to this topic

    #1 Cptbirdseye

    Cptbirdseye

      Advanced Member

    • Members
    • PipPipPip
    • 88 posts

      Posted 23 July 2014 - 04:50 PM

      Just happened right after the latest Windower update, repeated crashing seconds after loading into a 2nd client.  Doesn't crash if I disable most of the plugins/addons through plugin_manager and doesn't crash immediately after loading them manually so I've no idea which one is the culprit.

       

      Here's a list of the plugins/addons I use on both clients:

       

       

      <plugin>Chatmon</plugin>
      <plugin>Clock</plugin>
      <plugin>Guildwork</plugin>
      <plugin>LightLuggage</plugin>
      <plugin>Timestamp</plugin>
       
      <plugin>Attainment</plugin>
      <plugin>AutoExec</plugin>
      <plugin>BlinkMeNot</plugin>
      <plugin>BoxHelper</plugin>
      <plugin>Cancel</plugin>
      <plugin>Distance</plugin>
      <plugin>DrawDistance</plugin>
      <plugin>FFXIDB</plugin>
      <plugin>FishingCrashFix</plugin>
      <plugin>InfoBar</plugin>
      <plugin>Itemizer</plugin>
      <plugin>PetTP</plugin>
      <plugin>Silence</plugin>
      <plugin>Timers</plugin>
      <plugin>TParty</plugin>
       
      <addon>aecho</addon>
      <addon>AutoRA</addon>
      <addon>azureSets</addon>
      <addon>chatPorter</addon>
      <addon>enternity</addon>
      <addon>eval</addon>
      <addon>gametime</addon>
      <addon>GearSwap</addon>
      <addon>ohShi</addon>
      <addon>pet_fix</addon>
      <addon>porter</addon>
      <addon>shortcuts</addon>
      <addon>thtracker</addon>
      

       

      Chatmon, Clock, Guildwork, LightLuggage and Timestamp are set to load on all characters so the cause of the crashes doesn't seem to come from those plugins, and AutoRA, azuresets and thtracker are only loaded on one of the characters..



      #2 Cptbirdseye

      Cptbirdseye

        Advanced Member

      • Members
      • PipPipPip
      • 88 posts

        Posted 23 July 2014 - 05:03 PM

        Update on this, it's now affecting the first instance where all the above addons/plugins were loaded, so I'm gonna have to disable them all for now.



        #3 Arcon

        Arcon

          Advanced Member

        • Windower Staff
        • 1189 posts
        • LocationMunich, Germany

        Posted 23 July 2014 - 10:47 PM

        You have to disable some, then disable/enable some more, until you figure out what's causing it. My bets are on Guildwork, but I am absolutely not sure. Just giving you an idea where you could start.

         

        But in the end, without a crash dump there is hardly anything we can do about it unless we can reproduce it ourselves.



        #4 Cptbirdseye

        Cptbirdseye

          Advanced Member

        • Members
        • PipPipPip
        • 88 posts

          Posted 24 July 2014 - 09:45 AM

          My guess is it's infobar, as soon as I loaded it POL crashed, which is a pity since I know it's an addon no longer in development which makes it the most likely culprit.

           

          Isn't infobar.  Had a crash as soon as the 2nd client loaded, so I guess it's back to the start of enabling/disabling addons again.



          #5 Cptbirdseye

          Cptbirdseye

            Advanced Member

          • Members
          • PipPipPip
          • 88 posts

            Posted 25 July 2014 - 10:03 AM

            By the looks of it the plugin Timers doesn't like to be loaded via plugin_manager. If it's loaded from the character selection screen it doesn't seem to have any issues, you can unload and load it manually through the console and no trouble. But if you start a fresh new game using plugin_manager to load it after logging onto a specific character then it just locks up the game after a couple of seconds and brings up the "PlayOnline view has stopped responding" error box.

             

            Edit: It's most certainly Timers being loaded individually through plugin_manager doing the crashes.  I've put it into a global set to stop it crashing.






            1 user(s) are reading this topic

            0 members, 1 guests, 0 anonymous users