Issue 474 in fds-smv: Access Violations on 64 bit Windows

[codesite...@google.com]

Comment #79 on issue 474 by christop...@firelinkllc.com: Access Violations
on 64 bit Windows
http://code.google.com/p/fds-smv/issues/detail?id=474

Unfortunately, I do not have an appropriate platform upon which I might
perform such
a test.

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings

[codesite...@google.com]

Comment #80 on issue 474 by mcgratta: Access Violations on 64 bit Windows
http://code.google.com/p/fds-smv/issues/detail?id=474

Does the job fail at the same time in the simulation if you were to run it
again?

[codesite...@google.com]

Comment #81 on issue 474 by christop...@firelinkllc.com: Access Violations

on 64 bit Windows
http://code.google.com/p/fds-smv/issues/detail?id=474

To the extent that I recall the previous runs, the run failed at the same
time.
There are no changes occurring at that time. In other words, other than a
growing t-
squared fire, nothing in the domain opens, nothing closes, nothing turns on
or off,
and there are no forced changes in flow. It is possible that this would be
the
first time flow went into the new mesh to which I referred, but to be
honest I have
not examined that scenario. It is just a guess based upon the
relationships of the
meshes.

To be honest, I just had a gut feeling that there was a relationship
between the
failure in my problem and the sound of the discussion above. This sense,
in turn,
was based upon the extremely limited changes that I had made to the input
file from
the previously running file, my sense of how I selected certain mesh
parameters
based upon smokeview output (because smokeview rounds the mesh location
numbers) and
my sense of the likelihood that the failure time was near the time at which
flow
would have moved from the previously existing mesh to the new (added)
mesh. My
previous software experience in trying to sniff out intermittent or
difficult to
exactly reproduce problems also suggested that this information may be
assistive in
your search. So, I am not trying to waste your time with something that
does not
assist you in resolving another problem.

Eventually, I will probably retry my attempt to add the additional mesh
through a
more exacting grid generation process (on my side that is -- I'm not
talking about
FDS's process) and then see if I can get it to run that way. That might
also help
you if I am able to isolate the problem that way. Unfortunately, however,
all of my
current computational resources are tasked and I will probably not be able
to get a
free platform for a week or so to do a substantial rerun.

[codesite...@google.com]

Comment #82 on issue 474 by mcgratta: Access Violations on 64 bit Windows
http://code.google.com/p/fds-smv/issues/detail?id=474

Retry the case with the source code for 5.2.5 (SVN 2828), or even with the
latest
version in the repository. If it fails again, we'll try it here.