-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GO crash on startup #1772
Comments
Could you post here a crash dump file? Usually it appears in the |
Sure. However, it wasn't in that location (Windows Error Reporting was turned off). |
@oleg68 hi, the same problem happens to me. I attach .dmp file |
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. |
Unfortunally, no, it is not. I need a .dmp file. |
@oleg68 GrandOrgue v.2.12.1-1 Thank you for your time and effort on this project. |
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. |
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 |
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). |
A quelle version de GO correspond ce .dmp exactement? |
@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. |
Such version of GrandOrgue does not exist. |
@oleg68 sorry for the error: it was v.3.13.1-1 |
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.) where am I wrong? |
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. |
@Psi58 All your crashes were related to the ASIO drivers inside RtAudio. Could you test GrandOrgue after disabling |
@oleg68 can you explain how I can do that? |
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.
|
@Psi58 I managed to reproduce the problem. Seems RtAudio broke ASIO support since GrandOrgue 3.13.2 (after this change: 53f4937). As a workaround I suggest to use PortAudio with ASIO.
No, switch to using PortAudio with asio instead of RtAudio. |
Perhaps there is some remnant of the previous configuration that I need to remove? |
@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. |
@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? |
Thanks - that works (3.13.3). It's opened a PortAudio: MME device by default. |
@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. |
It works initially. |
@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. |
bonjour, je reprends le train en marche...j'ai ouvert GO/alessandria ce matin....pas de crash |
Quelle version de GrandOrgue c'etait? |
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 |
Merci beaucoup pour votre travail....je viens d'installer la version V3.14.0-0.2 |
@oleg68 With version v3.14.0-0.2 I didn't have any crashes the problem seems solved, Thanks. |
***@***.*** , 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: ***@***.***>
|
@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 ??? |
Parce que c'est une version intermediaire. Elle a ete cree sans optimisation comme toutes les outres versions intermediaires. |
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: ***@***.***>
|
@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 ? |
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? |
@Psi58 Thank you for the test and the pdf report what happened. I see that you are using Voicemeter. I'll do more research. |
Since GO v3.14.0 I don't observe anymore crashes that I reported in #1772 (comment), thanks @oleg68 ! |
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.
The text was updated successfully, but these errors were encountered: