Out of order trace()

[Animaleante]

Good morning everyone.

I've been using FMS for a couple of weeks, and there's this bug that is really annoying me. It is not a trace statement exclusive bug, but it can be better observed with it.

Here are a couple of images that will better explain my problem:

[SE_0208]

Does this happen intermittently or you always get this out of order trace each time you load this app?

[Animaleante]

Intermittenly. Sometimes it seems everything is going fine, and then it throws an error saying a var was not defined, but I see it being defined right before the statement that uses it, so it seems that it is running the statement before defining the var.

[SE_0208]

Hmm. I or someone else in my team will try to repro this issue and hopefully we can repro it our end. By the way which FMS version are you on and which OS are you on?

[Animaleante]

FMS 4.5. Windows 7 Ultimate 64x.

Thank you for the attention.

[SE_0208]

Hi Animaleante,

I am able to repro this only on Windows 7 but not able to repro it on supported platform of Windows 2008 - not yet tried on CentOS or RHEL. I would file bug for this but looks like this might Windows 7 issue and since we do not support Windows 7 for Production - this might have low priority. Will keep you updated once i get chance to discuss this more with engineering team.

[SE_0208]

I was able to repro this on CentOS too - FYI i have filed bug for the same and thanks a lot for reporting this to us.

[Animaleante]

Thank you a lot for the response.

Good thing I was not going crazy.

Will be waiting for the fix