Hi.
Unf. I am getting repeated hangs of GP (under Win 11).
All I know to do is use the task manager to kill it and completely start over. This is quite unsatisfying, because of both the workflow interruption, and the lack of any chance of diagnosis.
Is there any overt or hidden facility in GP that can assist either recovering from a hang, or diagnosing the cause of it?
Is there any way to have GP write logs in way that would help with this?
When do you get hangs?
While playing, or editing?
Do you use any Anti Virus Software?
You can enable logging in the temporary startup options.
Otherwise:
There are some options, but you need to narrow downâŚ
The hangs happen variously. I have seen it happen upon changing to SetList view. I have seen it happen after I have been over in Ableton Live editing data there. There does not seem to be one exact case or cause that I have observed so far.
Iâm using stock Win 11 Pro, no other separate AV software.
Does that happen when only GP is running?
Does is happen with the inbuilt Audio as with an external Audio Interface?
Good, thanks.
Where is the log file written to?
I donât see it listed here:
OK, was able to find from a wider web search:
C\Users\ACCTNAME\AppData\Local\GPErrorHandler\UnsentCrashReports\Gig Performer 5_5.0.23\Logs
but there is not a file there for today, even though I turned on the logging at the last startup.
Are those files only written on crash?
Is there a different location for as-it-happens logging?
Iâm in the hung state now. Can I cause an Error from here that will make the log file write?
Running? as opposed to not running? I donât quite understand.
There is always an audio interface connected.
I mean gp as only Software running using the audio interface
In the current hang, Live was also running. I know that same scenario happened yesterday also. Going forward I will try to observe specifically if a hang takes place w/o Live or another program running that uses the audio interface.
FWIW, quitting Live did not clear the hang.
BTW, Live was not actually doing anything, not even playing back. It was just sitting there (so I could edit a MIDI file in it).
Am I mistaken in thinking that GP is designed for and expected to be able to run side-by-side with DAWs?
It wasnât explicitly designed with that in mind but other than restrictions on Windows systems where multiple applications can not always share resources, it certainly can.
So presumably you werenât getting hangs until something you were doing changed. Focus on what changed at the point when hangs started happening.
Can sampling the GP process help? â LINK
Thanks. I have now made a .DMP file of the hung GP process.
It is too big to post here, but I can arrange to dropsend it if anyone knows how to take a useful look at it.
I repeat what I wrote above
Focus on what changed, when this started happening!
Just a thought
Did you have a network device connected in the past (typically a NAS) and youâre still having a reference to it? For example shortcuts with an UNC (\\servername\sharename\path) or a permanent mount using ânet use driveletter \\servername\sharenameââŚ
Windows might try to connect to it at unexpected times which may lead to erratic behavior
I do have a NAS connected, but Iâm not pointing GP at it in any way at all, to my knowledge.
That said, I was able to in run Analyze wait chain, and the message from it does include the words ânetwork I/Oâ, FWIW.
Of course if every aspect of all changes and timing of hangs were well known, I might be able to undo something specifically identified. Unf., there is no bright and shining line here. I wish there were.
I was able to get as far as downloading and running WinDbg on a mini-dump I created of GP while it was hung this morning, which is to say Iâm in well over my head wrt. Windows internals, etc.
Perhaps this picture has some meaning to someone here.
In my case, it does make me wonder, what is GigPerformer RubberBandStretcher ?
Here is the mini-dump, FWIW.
GigPerformer5.zip (15.9 MB)
