search

Stellarium / stellarium

Stellarium is a free GPL software which renders realistic skies in real time with OpenGL. It is available for Linux/Unix, Windows and macOS. With Stellarium, you really see what you can see with your eyes, binoculars or a small telescope.
https://stellarium.org
GNU General Public License v2.0
7.72k stars 820 forks source link

Crashes of Stellarium 1.1 (1.22.4 based on Qt 6.4) #2874

Closed smoinard18 closed 1 month ago

smoinard18 commented 1 year ago

Hello,

Multiple craches while connected to a ASCOM telescope (real EQ6R-pro ASCOM, or simulated ASCOM). Works well few minutes and crashed randomly while capturing video on another software, no special action in Stellarium.

Hope the following informations will help... Returning to 0.22.1.

Note that the provided log has been generated with a simulated ASCOM telescope (same crashes with a real connected telescope).

Platform and operating system:

Windows 11 Pro 21H2 build 22000.181.0, 64bits up to date

What kind of graphics card do you have? Driver version?

Intel Iris Plus Graphics. Driver Intel 27.20.100.9365

Which version of Stellarium causes problems:

stellarium-1.1.1-qt6-win64.exe - Stellarium 1.1 (1.22.4 based on Qt 6.4)

The LOGFILE: See joined file log.txt

Stef log.txt

10110111 commented 4 months ago

It it's possible to just use IP, it would be the best. I suppose this would also make the support of such devices not tied to Windows.

gzotti commented 4 months ago

Yes, I think this is what they are trying to do with Alpaca, i.e. opening up to cross-platform communication. Just I have not studied the details. (Will there be INDI/Alpaca communication? Will systems finally become compatible?)

10110111 commented 4 months ago

Anyone affected, please try ascom-crash-fix branch. It contains some workarounds that may help fix the crashes. If you still experience a crash, please tell the exact scenario, and try reproducing it with the GSS simulator, since I don't have the real hardware.

BTW, for some reason my "Scope Simulator" window no longer appears after I closed it once. Any idea how to make it open again? Otherwise I can't unpark the simulated scope.

gzotti commented 4 months ago

I hope @kantn8r, @itsgps, @StarFlea, @HilliBilli13 are reading this?

itsgps commented 4 months ago

I hope @kantn8r, @itsgps, @StarFlea, @HilliBilli13 are reading this?

Yes - just caught up, not quite in a position to test for a couple of reasons...I get far less Astro time during winter here due to winter work, but also the weather is just not condusive anyway. But also - I switched over prodominately to using StellarMate for Portable use, because it was a bit more ALL-IN-ONE for me.

But doesn't mean not willing to test anything...just wouldn't be for a few months.

StarFlea commented 4 months ago

Yes, I read an it sounds exciting! ;-) But I don't have an idea anymore!

All I can say is, that the crash is independent from GSS. It also occurs when ASCOM telescope simulator "ScopeSim.Telescope" or the "ASCOM.Simulator.Telescope" are used, even if the GSS is not running!

kantn8r commented 4 months ago

I've read through it but do not understand it. I'm not sure what the ascom-crash-fix is. Also, I'm not using ASCOM Alpaca and don't plan on using ASCOM Alpaca until I have to. The QT5 builds continue to work for me. I'm just an end user so can only report problems and have no idea how to troubleshoot the QT6 issue with ASCOM.

When you have a new QT6 fix implemented please let me know and I will test it. I'm using a Losmandy G11G / Gemini2 mount with the L5 firmware.

gzotti commented 4 months ago

@10110111 it seems a Qt6-based installer package needs to be linked into this discussion.

10110111 commented 4 months ago

@alex-w Could you prepare a build for this branch, so that anyone could download it similarly to the weekly builds?

10110111 commented 4 months ago

OK, here's a test build: stellarium-24.1-d2753bb-qt6-win64-ascom-test.exe. Anyone affected please run it in all scenarios when Stellarium crashed with ASCOM, and check whether this version crashes.

StarFlea commented 4 months ago

OK, I checked it. It crashes again... For testing I connected with ASCOM Telescope Simulator for .NET (ASCOM.Simulator.Telescope).

When I switch to an other Windows-Frame (e.g. Explorer) and back to Stellarium, the crash occurs...

10110111 commented 4 months ago

Tried with ASCOM.Simulator.Telescope too now, no crashes here. Did you start the correct version of Stellarium? Maybe you have multiple installed, and started not the one I linked to above?

StarFlea commented 4 months ago

Version is correct: 24.1.165-d2753bb [HEAD]

StarFlea commented 4 months ago

I tested with ScopeSim.Telescope... There is a reproducable crash too.

kantn8r commented 4 months ago

Thank you StarFlea, you saved me from wasting my time. As mentioned in my prior response, when a QT6 fix is implemented, I'd be happy to test. Any fix needs to be tested with ASCOM.Simulator.Telescope or equivalent before proposing it to the end users.

10110111 commented 4 months ago

when a QT6 fix is implemented, I'd be happy to test

When it's implemented, it will be past the time to test, you will just be using it. And without testing of the versions that I post in this issue the fix will not be implemented.

Any fix needs to be tested with ASCOM.Simulator.Telescope or equivalent before proposing it to the end users.

If you read my posts more carefully, you'll notice that I have tested my proposed fixes, and failed to get any crash with them. So the ball is on the end-users' side.

10110111 commented 4 months ago

@StarFlea

Well, I can't reproduce this.

If you could test it on a Windows virtual machine and reproduce the crash (and tell how you did this), this would be very useful. This is the Windows environment I'm using to debug this, and so far I've failed to get a crash with the test version I linked to above.

kantn8r commented 4 months ago

For me it's more about maintaining all the settings I've made in Stellarium for my kit. There are a lot of important subtle settings for doing an EAA session that don't translate between the different fixes/versions when installed and uninstalled and reinstalled. How do I ensure that all the settings/features are not lost when testing?

StarFlea commented 4 months ago

Well, I usually need to switch the windows-frames a few times before I provoke the crash. It doesn't happen immediately. It can take a few minutes...

I'll try it with the virtual machine. I use Windows 10 productively.

10110111 commented 4 months ago

How do I ensure that all the settings/features are not lost when testing?

First, on uninstalling you are asked whether you want to keep the settings or remove them. Then, to make really sure that you don't lose your settings even if your computer gets broken, you should back them up. The location is documented in section 5 of the User Guide (and also showed in the Help dialog inside the app).

kantn8r commented 4 months ago

I'll start backing up my settings.

I'd be happy to purchase a SharpCap Pro license for you or other developers working on fixes to the QT6 / ASCOM / Telescope Control crash. I'm assuming you have a Windows 10 or 11 computer to run SharpCap. It's also possible that you don't need SharpCap Pro to test this issue. Regular SharpCap is free.

Anyone testing should be running ASCOM and a telescope simulator with some other camera control software like SharpCap. All you need to do is cycle between windows a few times and QT6 will crash. It does not always crash immediately.

When you get to a point where QT6 does not crash after many cycles it will be ready for me to test.

StarFlea commented 4 months ago

I was able to reproduce the crash into the virtual machine!

A part of the truth may be that you have to run Stellarium in window-mode (not full-screen mode). I was only able to reproduce the crash after I copied the config.ini from my productive installation to the virtual machine...

I attached it as txt-file... config.txt

StarFlea commented 4 months ago

CORRECTION: My config has nothing to do with it!

Now it crashed in the basic configuration! Window-mode seems to be the problem!

StarFlea commented 4 months ago

I will now describe again what I did in the virtual machine:

  1. .NET 3.5 activated in Windows Control Panel
  2. ASCOM Platform 6.6 SP2 installed
  3. Stellarium installed in the debug version 24.1.165-d2753bb [HEAD]
  4. Stellarium started and telescope control activated
  5. New telescope set up (ASCOM.Simulator.Telescope = Telescope Simulator for .NET)
  6. Full screen mode deactivated and settings saved
  7. Restarted Stellarium (in window mode) and telescope connected
  8. After several window changes between Stellarium and Windows Explorer, the crash is triggered
10110111 commented 4 months ago

OK, with your config file and instructions I'm able to reproduce the crash.

StarFlea commented 4 months ago

The config file doesn't matter. It also works in the basic configuration.

github-actions[bot] commented 1 month ago

Hello @smoinard18!

Please check the fresh version (development snapshot) of Stellarium: https://github.com/Stellarium/stellarium-data/releases/tag/weekly-snapshot

github-actions[bot] commented 1 month ago

Hello @smoinard18!

Please check the latest stable version of Stellarium: https://github.com/Stellarium/stellarium/releases/latest

StarFlea commented 2 weeks ago

Is there a chance that the problem is obsolete with the newly released ASCOM Platform 7?

10110111 commented 2 weeks ago

I don't think so. The issue is in the incompatibility between Win32 COM and Qt6. Until someone implements support for Alpaca in Stellarium, the Qt6 build will not work with ASCOM.

gzotti commented 2 weeks ago

I cannot say what causes the issue, but it's more future proof to just go directly to ASCOM's successor, Alpaca, without further wasting our time. @StarFlea, you can just reactivate the exclusion in CMakeFiles and build and try if you really want.