search

GrandOrgue / grandorgue

GrandOrgue software
Other
149 stars 39 forks source link

GO crash on startup #1772

Closed Psi58 closed 5 months ago

Psi58 commented 5 months ago

GOcrash240110.zip New for me, flagging it in case it is a more widespread issue.

Previously (3.12) I had GO running happily on 2 laptops, both running W10. Installed 3.13, works fine (almost...*) on one, but on the older machine crashes after momentarily showing the GO menu bar. I've tried installing as admin, cleaning/updating everything on the machine (including "tidy up leftovers" in BC Uninstaller) - no change. Completely uninstalled GO, tried to reinstall 3.12 (which previously worked) - same issue.

This machine is maxed out with only 128GB SSD and 16GB RAM, so it just may be a resources issue? I've got a more beefy replacement machine on order, so hopefully this isn't a long-term problem for me. But I'm raising it in case whatever the cause is affects other users.

Relevant eventviewer log items attached. They don't mean much to me...

*: 1 sampleset that previously loaded OK now crashes while loading. Still investigating this.

oleg68 commented 5 months ago

Could you post here a crash dump file? Usually it appears in the AppData\Local\CrashDumps subdirectory of the home user directory.

Psi58 commented 5 months ago

Sure. However, it wasn't in that location (Windows Error Reporting was turned off). I've turned it on, and now have the attached in C:\ProgramData\Microsoft\Windows\WER. Is this what you need? WER.zip Thanks.

Larioant commented 5 months ago

@oleg68 hi, the same problem happens to me. I attach .dmp file
GrandOrgue.exe.9592.dmp

JPIL04 commented 5 months ago

bonjour, Même problème....Crash au démarrage . je lance GO, la barre de menu s'affiche , ainsi que la fenêtre avec l'avancement du chargement....et au bout d'une vingtaine de secondes, tout disparait - arrêt de GO avant même que le premier fichier WAV ne se charge. Cela est arrivé une diziane de fois , depuis, je crois, la version 12 ou 13....J'utilise l'orgue de Alessandria de Piotr Grabowski. Je n'avais jamais eu de problème avant . Le premier plantage remonte vers le mois de avril, mai 2023 a peu près ! La seule solution d'y remédier est de réinstaller l'orgue dans un nouveau répertoire : décompacter le fichier source....et repartir avec l'orgue de base, comme pour la première fois. Heureusement, j'ai sauvegardé les combinaisons et paramêtres, ce qui m'évite de tout reparamêtrer à chaque fois en faisant une importation des "settings" ! ci joint le fichier dmp du dernier bug, pas plus tard que samedi dernier !!! GrandOrgue.exe.13416.dmp

oleg68 commented 5 months ago

@Larioant @JPIL04 Thank you for the dump files. Could you also tell the exact version number of GrandOrgue the dumps belong to.

oleg68 commented 5 months ago

WER. Is this what you need? WER.zip Thanks.

Unfortunally, no, it is not. I need a .dmp file.

Larioant commented 5 months ago

@oleg68 GrandOrgue v.2.12.1-1 Thank you for your time and effort on this project.

Larioant commented 5 months ago

Même problème....Crash au démarrage ........ @JPIL04 Cela m'est arrivé aussi comme tu dis, à partir de la version 12 ou 13, je ne m'en souviens plus. J'ai tout essayé, désinstaller, supprimer les entrées GO du registre, changer de dossier, cela n'a pas résolu le problème. C'est à peu près au moment où j'ai changé d'ordinateur pour passer à Win11 que je pensais que le problème venait du nouveau système d'exploitation.

It happened to me too as you say, from version 12 or 13, I don't remember. I tried everything, uninstalling, deleting GO entries from the registry, changing folders, it didn't fix the problem. It was right around the time I changed computers, switching to Win11, I thought the problem was with the new operating system.

eturpault commented 5 months ago

I do have also regularly GrandOrgue crashes on my Windows PC when I launch the application or when I open the Settings panel or when I load a sample set. Here for example a crash dump corresponding to a crash occurring when opening the Settings panel with GO v3.13.3-1.2 GrandOrgue.exe.9400.dmp

Psi58 commented 5 months ago

WER. Is this what you need? WER.zip Thanks.

Unfortunally, no, it is not. I need a .dmp file.

Sorry, here it is GrandOrgue.exe.6480.dmp. v3.13.2-1.

(For anyone else as clueless as me at how to create crashdumps see here).

oleg68 commented 5 months ago

@JPIL04

ci joint le fichier dmp du dernier bug, pas plus tard que samedi dernier !!! GrandOrgue.exe.13416.dmp

A quelle version de GO correspond ce .dmp exactement?

oleg68 commented 5 months ago

@eturpault @Psi58 @Larioant @JPIL04 Could you try to reproduce this crash with the standard release 3.13.3-1 https://github.com/GrandOrgue/grandorgue/releases/tag/3.13.3-1 without installing, just extract the .zip and run it?

If you manage to get crash several times, please attach several crash dumps with the inormation what was your last action caused the crash.

oleg68 commented 5 months ago

@Larioant

GrandOrgue v.2.12.1-1 Thank you for your time and effort on this project.

Such version of GrandOrgue does not exist.

Larioant commented 5 months ago

@oleg68 sorry for the error: it was v.3.13.1-1

Larioant commented 5 months ago

I extracted the folder of your link grandorgue-3.13.3-1.windows.x86_64.zip but by clicking on the executable GrandOrgue.exe (without installation), the program does not start and detects the following error:

13/01/2024 15:11:58: 15:11:58: Error: can't create file 'C:\Users...\Documents\GrandOrgue\Cache\F4118D328148BF61F71CA006AB6A3F001E25A577.idx' (error 2: The file could not be found specified.) 01/13/2024 15:11:58: 15:11:58: Error: Failed to write to 'C:\Users...\Documents\GrandOrgue\Cache\F4118D328148BF61F71CA006AB6A3F001E25A577.idx'

where am I wrong?

Psi58 commented 5 months ago

Rebooted, re-downloaded https://github.com/GrandOrgue/grandorgue/releases/download/3.13.3-1/grandorgue-3.13.3-1.windows.x86_64.zip, unzipped, ran GrandOrgue.exe. 3 runs, each time the same behaviour. GrandOrgue.exe.6656.dmp GrandOrgue.exe.8648.dmp GrandOrgue.exe.10728.dmp

oleg68 commented 5 months ago

@Psi58 All your crashes were related to the ASIO drivers inside RtAudio.

Could you test GrandOrgue after disabling RtAudio: asio Settings->Audio-> SoundPorts ? Do the crashes still occur?

Psi58 commented 5 months ago

@oleg68 can you explain how I can do that? Obviously I can't change anything from within GO because of the crashes, and I can't find anywhere to edit the RtAudio settings anywhere else on my system. (I've tried searching in Settings, and the Device Manager). Sorry if it's a stupid question, and thanks for your assistance. In case it's relevant my MIDI/audio interface is Behringer UMC204HD, and I route the audio through Voicemeeter as a graphic equaliser, using the UMC ASIO driver. Perhaps I should temporarily uninstall this?

eturpault commented 5 months ago

I forgot to mention that I observe crashes since years, it is not linked to a recent SW version, I never took time to report it but as there is currently an opened issue about it, I jump in. My assumption is that it has a link with the audio interface, as crashes occurs in my side randomly on one of the following use cases : application launch, settings window open or close, audio interface change, panic button press, sample set loading. Here are crash dumps got with release 3.13.3-1, executed from the unzipped archive, the PortAudio WASAPI audio interface is used (only PortAudio is selected in my SoundPorts audio settings) :

oleg68 commented 5 months ago

@Psi58 I managed to reproduce the problem. Seems RtAudio broke ASIO support since GrandOrgue 3.13.2 (after this change: https://github.com/GrandOrgue/grandorgue/commit/53f49376b40de33676909276e90f470f3829f5cc). As a workaround I suggest to use PortAudio with ASIO.

I can't change anything from within GO because of the crashes, and I can't find anywhere to edit the RtAudio settings anywhere else on my system.

  1. Download a working version of GrandOrgue, for example, 3.12.2 as a zip file. Unpack it to some directory.
  2. Run GrandOrgue from this directory, go to Settings->Audio, deselect the RtAudio: asio sound port and change the device to something other, ex. PortAudio: asio: ...
  3. Press OK. Exit from GrandOrgue
  4. Run GrandOrgue 3.13.3 again. It should work.

In case it's relevant my MIDI/audio interface is Behringer UMC204HD, and I route the audio through Voicemeeter as a graphic equaliser, using the UMC ASIO driver

No, switch to using PortAudio with asio instead of RtAudio.

Psi58 commented 5 months ago
  1. Download a working version of GrandOrgue, for example, 3.12.2 as a zip file. Unpack it to some directory.
  1. Run GrandOrgue from this directory, ...

Perhaps there is some remnant of the previous configuration that I need to remove?

oleg68 commented 5 months ago

@Psi58 GrandOrgue configuration is stored in the file \AppData\Roaming\GrandOrgueConfig

If 3.12.2 also crashes, so rename GrandOrgueConfig to GrandOrgueConfig.save and try to run 3.13.3. It takes by default another device (not asio) so it should not crash.

oleg68 commented 5 months ago

@eturpault I've analyzed all the dumps you provided. Unfortunally all of them occure in external libraries, not in GrandOrgue itself. So it is quite difficult to investigate them.

How often the crashes occur?

Psi58 commented 5 months ago

@Psi58 GrandOrgue configuration is stored in the file \AppData\Roaming\GrandOrgueConfig

If 3.12.2 also crashes, so rename GrandOrgueConfig to GrandOrgueConfig.save and try to run 3.13.3. It takes by default another device (not asio) so it should not crash.

Thanks - that works (3.13.3). It's opened a PortAudio: MME device by default.

oleg68 commented 5 months ago

@Psi58 I tried to fix the rtaudio/asio/crash. Please try the intermediate build from https://github.com/oleg68/GrandOrgue-official/actions/runs/7514477505 (will be available about 40 minutes later) with RtAudio and ASIO.

Psi58 commented 5 months ago

It works initially. But then closing GO and all windows and reopening it opens but hangs ("Not responding"). Still "not responding" after I rebooted and tried again.

eturpault commented 5 months ago

@oleg68 : the crash occurrence is not always the same, the dumps that I provided today have been captured in less than 5 minutes. I observe that crashes are easier to obtain within the minute following GrandOrgue start. After it is more difficult to reproduce. So I have to ask GO to start without any organ. My Windows PC is not connected to my organ console, I use it to check ODF generated by OdfEdit, so these crashes are not a real problem for me.

JPIL04 commented 5 months ago

bonjour, je reprends le train en marche...j'ai ouvert GO/alessandria ce matin....pas de crash Je suis allé dans l'onglet Audio et j'ai décoché Rt audio, puis j'ai redémarré GO/ Alessandria et là : Crash ! GrandOrgue.exe.11988 save .dmp je viens de téléchargé le fichier http:\ grandorgue-3.13.3-1.3.windows.x86_64.exe.zip..;je vais voir si ça marche !

oleg68 commented 5 months ago

bonjour, je reprends le train en marche...j'ai ouvert GO/alessandria ce matin....pas de crash Je suis allé dans l'onglet Audio et j'ai décoché Rt audio, puis j'ai redémarré GO/ Alessandria et là : Crash ! [GrandOrgue.exe.11988 save .dmp]

Quelle version de GrandOrgue c'etait?

JPIL04 commented 5 months ago

La dernière versionn de la semaine dernière ! v3.13.3-1. Je suis en train de re décompacter pour la 10ième fois les fichiers source de piotr grabowski, en espérant que cele fonctionne comme les autres fois...croisons les doigts !

JPIL04 commented 5 months ago

pour être précis, entre temps, j'ai installé la version 13.3-1.3....mais ça ne marchait pas mieux... GrandOrgue.exe.12808.dmp

JPIL04 commented 5 months ago

bon...la réinstallation a fonctionné, comme d'habitude.... ci joint copie d'écran du re-démarrage ...

![Uploading écran démarrage après réinstallation alessandria GO V3.13.3-1.3.JPG…]()

oleg68 commented 5 months ago

There are at least two different causes of craches

JPIL04 commented 5 months ago

merci oleg68 pour ses infos.

concrètement, que dois-je faire pour éviter le crash lié au crescendo ?

oleg68 commented 5 months ago

merci oleg68 pour ses infos.

concrètement, que dois-je faire pour éviter le crash lié au crescendo ?

J'ai essaye de corriger ce crash. Pouriez-vous tester la version intermediaire de https://github.com/oleg68/GrandOrgue-official/actions/runs/7521220624 (elle sera disponible dans 40 minutes)?

JPIL04 commented 5 months ago

Merci beaucoup pour votre travail....je viens d'installer la version V3.14.0-0.2 j'ai lancé Alessandria et pas de crash au démarrage. Tout semble normal ! je vous tiens au courant quoiqu'il arrive ....mais en tout cas, merci beaucoup Oleg.

Larioant commented 5 months ago

@oleg68 With version v3.14.0-0.2 I didn't have any crashes the problem seems solved, Thanks.

JPIL04 commented 5 months ago

@.*** , Merci beaucoup pour votre travail....je viens d'installer la version V3.14.0-0.2   j'ai lancé Alessandria et pas de crash au démarrage. Redémarrer plusieurs fois jusqu'à hier soir.... Tout semble normal ! je vous tiens au courant quoiqu'il arrive ....mais en tout cas, merci beaucoup Oleg.

@jpil04

De : "Oleg Samarin" A : "GrandOrgue/grandorgue" ,"JPIL04" ,"Mention" Envoyé: dimanche 14 Janvier 2024 18:45 Objet : Re: [GrandOrgue/grandorgue] GO crash on startup (Issue #1772)  

 

There are at least two different causes of craches

in @Psi58 's case rtaudio/asio causes the crash
in @JPIL04 's case a crescendo causes the crash: It is attempted to load it's position when it has not yet been initialised

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.***>

JPIL04 commented 5 months ago

@oleg68 . juste une remarque à propos de la mise à jour ....je constate que le temps de chargement de l'orgue a doublé par rapport à avant. est-ce qu'il y a une explication à cela ???

oleg68 commented 5 months ago

@JPIL04

je constate que le temps de chargement de l'orgue a doublé par rapport à avant. est-ce qu'il y a une explication à cela ???

Parce que c'est une version intermediaire. Elle a ete cree sans optimisation comme toutes les outres versions intermediaires.

JPIL04 commented 5 months ago

Merci pour cette réponse,  et encore bravo pour cette version qui semble fonctionner parfaitement.  Depuis l'installation,  je n'ai pas eu de plantage ! Trop cool...vivement la version définitive ! Le 19 janv. 2024 20:10, Oleg Samarin @.***> a écrit : @JPIL04

je constate que le temps de chargement de l'orgue a doublé par rapport à avant. est-ce qu'il y a une explication à cela ???

Parce que c'est une version intermediaire. Elle a ete cree sans optimisation comme toutes les outres versions intermediaires.

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

oleg68 commented 5 months ago

@Psi58 I tried to fix the hang when using rtaudio:asio. Could you test the new version: https://github.com/oleg68/GrandOrgue-official/actions/runs/7595418087 ?

Psi58 commented 5 months ago

Thanks @oleg68 . I've tried again, still getting stuck at 'Not responding' as described in the attached. NB this is a very resource constrained machine that I'm no longer actively using - perhaps it works in other environments? 3.14.0-0.4.pdf

oleg68 commented 5 months ago

@Psi58 Thank you for the test and the pdf report what happened.

I see that you are using Voicemeter. I'll do more research.

oleg68 commented 5 months ago

@Psi58 #1788 fixed a crash with RtAudio/Asio. But the hang with voicemeter still exists. I created a separate issue: #1789

oleg68 commented 5 months ago

Fixed with #1783 and #1788

Created a related issue #1789

eturpault commented 2 months ago

Since GO v3.14.0 I don't observe anymore crashes that I reported in https://github.com/GrandOrgue/grandorgue/issues/1772#issuecomment-1890107559, thanks @oleg68 !