This sort of leads me to think the problem may be either with memory or resources not being released after each scan

Uninitialized variables that happen to be zero on the first run, but re-use memory with random contents on subsequent runs are always a good candidate for things like this :-).

As I mentioned before, when I tried to do multiple revolutions (720° for example), it didn't do it, it only did a single revolution (360°).  However, when I told it to do only 90° worked.  But I don't know how to tell it to do a range from a specific stating point (like from 45° to 90°).  How do you input that?

FWIW, I found that the missing bands seem to get worse on larger/more complicated scans with each successive scan.  So if I power down between scans, I usually get a pretty decent scan (some missing parts. but not too bad).  But if I do 3-4 successive scans, it gets pretty bad. 

This sort of leads me to think the problem may be either with memory or resources not being released after each scan, or maybe thermally related issues?

Just thinking out loud...

Hmm... I'll look into what could be causing that.

Any insights on this issue yet?

I was thinking that a second pass may fill in those missing parts.

To this end I thought that changing the number of degrees in the scan page, would do just that.  But it doesn't appear to do anything.  Regardless of how many degrees you tell it to do (I tried 720º & 1080º), it only makes one revolution (360º).

Is this a bug, or am I doing something wrong?