Hi, yes but I have only fits files from my Canon DSLR from ekos. Could you point me at a fits file which works? I can then Isolate the problem to the DSLR.
TIA

Ah, so it likely is related to either color or de-bayer, I've only tried grey...
I don't have bayer FITS data, but I tried it with a (processed) RGB fits, and that worked, too.
(And I had just recompiled the latest version 'as of now')

Here's an example that causes the crash, also with the git from a few moments ago:
drive.google.com/open?id=1efn4UFufz1HWPYUTp-KlCKZwa-1-RPFx

It opens fine with the stable version however.
TIA

If you need a working file, you can try this: N7000_300.fits (raw from ASI1600, 32MB)

Hmm, your file is nicely displayed, stretched and zoomed here

Hi. Your file crashes too. Must be my install. Anything I could try?
TIA

Not really
(and I have to leave now for some ~2h - maybe someone else has suggestions)

Ok. One observation: the icon at the lower right of the fitsviewer window which restores default slider positions is missing in the git version but present in the stable PPA version.
Ubuntu 18.04

Steve, I'll also take a look. You say it crashes from the most recent git with that file. What computer, OS, other details are you using?

Also, that magic wand icon in the lower right is disabled when the image is already using the automatically computed stretch parameters. It only appears after the stretch has been modified. Perhaps that's what you're seeing?

Hi. Yes, I only see the icon after I move the sliders in the stable version of kstars but in the latest git I never get to see it because moving any of the sliders causes the crash: bt above. It crashes with ANY .fits file whether I created it with a dslr in kstars or not.
Thanks for taking a look.

Ubuntu 18.04 updated
Tried on an intel i3 with 16Gb, an intel i5 with 8Gb both using ssd drives and an AMD E2 with 4Gb and a mechanical hard drive, all using either yesterday's or today's git. The fitsviewer of stable version 3.3.9 works on all three.
TIA

So if I interpret the crash happens during the display of the scaled-down preview in the upper left (cute feature BTW!), and within some QT GL-routine(?)...
Just to be sure - did you do a full clean build from scratch, or use some old(er) CMake cache?

FYI, I am also looking at it, and that "cute feature--upper left preview" is actually some kind of bug I'm chasing down, perhaps a clue to the crashes.
I never programmed that, and it didn't happen previously :/

Unfortunately, I'm having issues with my build environment on my mac, so it may be a bit until I can fix that and then start debugging.