Tweet
So, If anyone is wondering why DN is crashing... and why CST works... and why is there a Class: (null) with some really messed up dates for the event duration, here is why.
Basically, if you hover over the event duration, it says 2016/12 18:21 - 0/2016 12:19, Class: (null)... and you are thinking, WTF?
Well, here is what you need to know.
A correct time parser should be of the format YYYY/MM/DD HH:mm - YYYY/MM/DD HH:mm. What you should expect to see would be 2016/12/18 21:00 - 2016/12/19 00:00
HOWEVER, it looks like someone thought we can just ignore the year... or something... and they wrote the time parser as MM/DD HH:mm - MM/DD HH:mm
But guess what, windows still feeds to them a time format in YYYY/MM/DD HH:mm... and it looks like they just parse each value at a time anyways and did not ignore the YYYY.
What ends up happening is we have basically 10 values to parse, but the parse will only parse 8 values, and the first 8 values to be exact. This leave with us the HH:mm which represents the time the event ends that will not be parsed.
From the continued line that says "Class: (null)" it looks like the HH:mm is still parsed, BUT AS A MEMORY ADDRESS. This is why it ends up being crashing and why CST is the only time zone that does not crash DN.
The end time for this event for CST is midnight, which is 00:00. If we were to reference memory address that is a 0, it will return back as null. HOWEVER, for any other time zone, the end time for the event is not midnight, it would be like 1AM or 10PM for example, which makes it that the game is trying to reference the memory address somewhere that is not 0, but less than 23. There is a very good chance that those memory addresses is outside of the available memory space for DN. Windows sees it trying to ask for something outside, windows tells DN: HEY! This address space is not yours! You can't touch it!. DN then freaks out not knowing what to do and crashes.
So TL
R;
EyeDentity, FIX YOUR GAME AND TEST STUFF LIKE THIS! Also, sanitize your string parsing so it does not leak.
Basically, if you hover over the event duration, it says 2016/12 18:21 - 0/2016 12:19, Class: (null)... and you are thinking, WTF?
Well, here is what you need to know.
A correct time parser should be of the format YYYY/MM/DD HH:mm - YYYY/MM/DD HH:mm. What you should expect to see would be 2016/12/18 21:00 - 2016/12/19 00:00
HOWEVER, it looks like someone thought we can just ignore the year... or something... and they wrote the time parser as MM/DD HH:mm - MM/DD HH:mm
But guess what, windows still feeds to them a time format in YYYY/MM/DD HH:mm... and it looks like they just parse each value at a time anyways and did not ignore the YYYY.
What ends up happening is we have basically 10 values to parse, but the parse will only parse 8 values, and the first 8 values to be exact. This leave with us the HH:mm which represents the time the event ends that will not be parsed.
From the continued line that says "Class: (null)" it looks like the HH:mm is still parsed, BUT AS A MEMORY ADDRESS. This is why it ends up being crashing and why CST is the only time zone that does not crash DN.
The end time for this event for CST is midnight, which is 00:00. If we were to reference memory address that is a 0, it will return back as null. HOWEVER, for any other time zone, the end time for the event is not midnight, it would be like 1AM or 10PM for example, which makes it that the game is trying to reference the memory address somewhere that is not 0, but less than 23. There is a very good chance that those memory addresses is outside of the available memory space for DN. Windows sees it trying to ask for something outside, windows tells DN: HEY! This address space is not yours! You can't touch it!. DN then freaks out not knowing what to do and crashes.
So TL
R;EyeDentity, FIX YOUR GAME AND TEST STUFF LIKE THIS! Also, sanitize your string parsing so it does not leak.
Comment