[Xastir] Findu Trails in 1.4.2

[Curt, WE7U]

On Tue, 15 Feb 2005, Curt, WE7U wrote:

> On Mon, 14 Feb 2005, Tom Tessier wrote:
>
> > This is on the 1.4.2 with rtree on in Cygwin 1.5.7-1 (version from
> > setup.ini) running on a 2.8 GHz Pentium 4 in Windows XP Professional.
> >
> > After 5-7 requests for Findu trails for stations, Xastir enters some sort of
> > state where it uses all of the available CPU, 80-99%. After a number of
> > trials, I found that Xastir would do this from as little as 3 requests to as
> > many as 15 requests. I let Xastir run for about 20 minutes one time at "full
> > CPU" and it did not stop. It was in some sort of loop, evidently. I was
> > requesting the "example" trail of K4HG-8, with various start times and
> > lengths. This happened most often with long trail lengths, 30+ points, like
> > that.
> >
> > One way I did find to stop this behaviour was to delete .xastir/tmp/map.log
> > before each trail download. After I got to about 40, I got tired of
> > repeating this...no problems.
>
> Hmmm.  I don't know why deleting that file would have something to
> do with it.  Perhaps something errors out if the file it created
> suddently disappears, which kiss the process that is causing the
> excessive CPU.

Meant "kill" the process.


> What I think is happening:  You're requesting a URL from findu.  For
> some reason the wget or libcurl is not timing out, or else you're
> able to make a new request before it times out.  As I recall we
> spawn this request off to a new process, which waits for the return.

Nope.  No extra processes here.  Looks like the main thread waits
until the wget/libcurl completes.

Did you immediately make another request while the earlier sets of
points were still being processed by Xastir and displayed?

--
Curt, WE7U.   APRS Client Comparisons: http://www.eskimo.com/~archer
"Lotto:    A tax on people who are bad at math." -- unknown
"Windows:  Microsoft's tax on computer illiterates." -- WE7U
"The world DOES revolve around me:  I picked the coordinate system!"