Windower 4 - Discussion and Support

[Sechs]

Ok created a ~900mb crash dump, compressed to ~80mb and currently loading in the shared folder I linked above.
Check if you see something there

About to login again with the different luacore this time.

[Motenten]

Game should be frozen, and windbg active. In the command window, enter:

.dump /m c:\sechs_brdcrash2.dmp

and

.dump /ma c:\sechs_brdcrash2_full.dmp

Let us know the file sizes of them.

[Sechs]

Edited my previous post, but I've been too late sorry.
Bit less than 900mb uncompressed around 80mb compressed.
Uploading to the same repository I linked before but my connection is very slow upstream. Altough it feels slower than usual tonite >.> Should've tried dropbox.
Currently 34% the second I'm typing this.


Edit:
Upload complete now!
Please let me know if I can do anything else before the next dump.

[Motenten]

You're sure that FFXI is -not- crashing when Timers is not loaded?

[Sechs]

Never saw it crash with timers off. I've been forced to play events with timers unloaded (it's a mess, trust me ><)
Whenever I load it I crash, sooner or later. Sometimes several times in a row, sometimes it takes a while, but usually if I'm in an event (i.e. doing lots of buffs) I crash, for example, at least once per skirmish run.
Never ever ever ever crashed without timers loaded.
I couldn't swear on it being the only culprit of course, but I'm pretty sure Timers at least plays a role in my crashes.


Right now for instance as I'm writing this, I crashed as Pianissimo reached 0:00 and started flashing in the buffs tracker.
It's always the same behaviour. Screen stops for a second or two, then I get the POL crash window.


If I can provide any more detailed dumps I'll be glad to now that I can, but I'm afraid Arcon will need to fix his "new" luacore to work with addons if he wants us to take dumps with it.

[Motenten]

I've been reviewing the crash dump, and unfortunately I don't think it's useful. It only records a single thread, and that thread is -not- what caused the crash. It -should- have 60+ threads recorded (particularly with the /ma option).

You're running the x86 version, correct?

I really have no idea what to tell you to get a proper crash dump out of this. Though, any further dumps you can use the /m option instead of the /ma one, for the smaller files.

Random idea: if, when the game freezes, you can hit ctrl-break on windbg before the crash notice shows up over the game, and look at that. Would be difficult to manage, and I have no idea if that would actually give anything more useful.

Given that I have not encountered a crash since 3.4.0.5, and Subadai also apparently has gone long stretches of time without crashing, I'm wondering if something about your environment specifically is causing an issue. You're running live, but with the dev Timers copied over? Have you tried running on dev instead?

[Sechs]

Running the x86 version yes, but I have 2 more versions. "ia64" and "amd64".
If you have a guess at why the minidump is only 32kb, probably the same reason why there are missing threads, I'm willing to try. Some settings? Something obvious (for you guys) that I might have missed?
I can try the alt+tab then ctrl-break on windbg but I think it's gonna be hard, since I don't know when a crash is coming. If I were able to perfectly know that maybe... but without that I don't see it realisticaly with such a short window =/

I'm running on Live with 3.4.0.5 Timers, the dev hook Arcon posted before going on holidays.
I could try Dev, yes.
Never used dev, where do I get it on the github repository? In which subsection?

[Motenten]

On the Windower.net page, right below the main download button is a small link to the dev version installer. Just install it in a different directory than the main Windower version; otherwise it works the same.

[Sechs]

Ok logged on Dev and configured stuff, but it's a bit too late for me now, gonna test it tomorrow for LS event and see what happens.
Meanwhile I just noticed that both normal and dev versions of Windower have an "advanced" tab within options with 4 buttons to turn on additional logging.
Are those any useful to create dumps? I currently have them all to "off".

[Sechs]

I jinxed myself. Was about to come here to post "hey! No crash for over 40 mins on Dev with 3.4.0.6!" and then I just crashed lol.
Strange thing, I usually crashed on live when casting/overwriting songs or when songs were expiring.
This time I crashed while I was walking, after the event. Didn't see any song expiring (but I couldn't swear on this...)


Going back to the start: any clue on how I could "fix" my crash dumps so they list all threads so I can finally start providing dumps that are actually useful? >.>

[Sechs]

Another crash, similar to the old ones this time.
During Mugyinwa, long after I finished buffing, but when some other buffs were about to expire or had just expired.

[Subadai]

Well, it took me a long while, but I did crash last night in Dynamis on my THF. Just as I was about to ws. Crash dumps. I'm going to run all week without Timers to see if it really is a Timers issue or something else. As before, it takes me a long while to crash, many hours of play usually. Hopefully this dump helps. I'll report back as soon as I find out anything.

[Sechs]

Supposing the cause of my crashes is the same I've had before (not necessarily the case...) I barely ever crash on the other jobs I've been playing lately.
Never seen a crash on PUP.
Seen one or two max on DNC.
Never seen a crash on MNK.

I see crashes very easily on BRD though. That's because my beloved LSmates kinda put me on permabrd as if I don't have other jobs () and because compared to other jobs BRD probably has the highest rate of "buffs per minute" so, I guess, more chances of a crash during the same amount of time.
I might be wrong, but it seems to me it's a crash based on the "Buffs" part of Timers.
Wonder what would happen if I were to disable the Buffs side...



Either way, as I said before, I'd really love some clues or help to fix mine and Subadai's crashdumps.
If we cannot fix that, it's useless for us to even take dumps in the first place. As far as we know if we managed to take relevant dumps the issue could have been already solved by now =/ So yeah, I think this is really important.

[Suteru]

Does the buff duration portion of timers sort of migrate down the window for everyone else? Eventually it goes off screen and I can't see any of my roll durations.

[Johnblaze]

Yeah, it's a known issue that is fixed in dev builds of timers. I've just been unloading and loading timers to fix it. For some reason if I just do "//reload timers", it eventually crashes me.

[Karizo]

So I've been using the latest dev version of timers, and have a question regarding the feature which places the buff with the least amount of time at the top. It seems to have been removed in the latest dev version, is it something that will be brought back once other major bugs have been fixed?

[Motenten]

So I've been using the latest dev version of timers, and have a question regarding the feature which places the buff with the least amount of time at the top. It seems to have been removed in the latest dev version, is it something that will be brought back once other major bugs have been fixed?

Adjust the settings xml field of <sortType>. Default is Creation (ordered according to when the buff was originally cast; refreshed buffs keep their same position), and other options are Duration (soonest-to-expire at the top) and Alphabetical (A-Z).

[Karizo]

Adjust the settings xml field of <sortType>. Default is Creation (ordered according to when the buff was originally cast; refreshed buffs keep their same position), and other options are Duration (soonest-to-expire at the top) and Alphabetical (A-Z).

thanks!

[KuKuKaChoo]

So, having put in a lot of playtime on the latest dev Timers, I'd have to say it's very solid and reliable. There are only two things I've noticed wrong, although I think only one is actually a bug.

If I still have the Double-Up Chance timer ticking down from my last COR roll, my second COR roll will not get a duration timer at all. Second, the duration for Ballads is inaccurate. I don't think Timers is incorporating Eminent Flute, so maybe it's not hardcoded in yet? Out of curiosity, is Timers able to hardcode duration bonuses for gear with variable, but known, augments? I'm sure you guys are capable of making it work, but I wonder if the framework to do so is already in place. I don't even think such a thing has been relevant until Linos.

[Arcon]

[…] Out of curiosity, is Timers able to hardcode duration bonuses for gear with variable, but known, augments? I'm sure you guys are capable of making it work, but I wonder if the framework to do so is already in place. I don't even think such a thing has been relevant until Linos.

This is possible, we do have augments mapped. It would be easier in Lua, since we have a nice library for it there, but it can be added to Timers as well. You should put in a feature request for it on our issue tracker so we don't forget.