There is something in FMOD that seems to continuously use a P4 command which ends up spawning 1000s of authentication tabs…
We have Perforce connected to FMOD as our source control. Perforce authenticates with Okta. So when FMOD attempts to use Perforce while Perforce’s ticket auth has expired, it will open a new Okta auth chrome tab every 10 seconds or so on loop… forever. The only way to stop it is to try to authenticate within the ten second window or force close FMOD.
Is there a way to have FMOD only attempt to authenticate ONCE and wait for a response?
Hi, apologies for the delayed response.
Could I get a few things from you?
- Your FMOD Studio version number
- If you’re using 2.02, which Perforce integration you’re using (i.e. standard vs legacy integration)
- A log from Window → Console → Logging with “Show verbose logging” enabled where the spam issue occurs
Just following up on this - were you able to resolve the authentication spam issue? If not, could I get you to provide me with the information I noted in my previous reply?
Hi Leah, apologies for the delay, I’ve been out of office for the week. No it’s still not fixed besides the work around of closing the app then authenticating. Let me get that information for your asap!
1 Like
No problem, thanks in advance!
- FMOD 2.02.22.
- Perforce integration is standard.
- Latest verbose logging during the error.
(I’ve asked the user to try and copy paste all the text to see if there is more context. But this is all I have from them for now)
Thanks for the additional information!
The log snippet unfortunately doesn’t reveal anything, so the full log from the user would be great. Besides copying the entire log, the user should be able to retrieve the full log from the relevant directory depending on their platform:
- Windows:
%HOMEPATH%\AppData\Local\FMOD Studio\Logs
- Mac:
~/Library/Application Support/FMOD Studio
- Linux:
~home/FMOD Studio/Logs
Following up on this again - were you able to get the full log from the user, or otherwise resolve the issue?
Hey Leah, for some reason the FMOD Studio folder doesn’t exist in our Application Support directory path. Do you know anywhere else it could be? I’ve been digging around and can’t seem to find it.
Apologies for the delayed response!
Its likely that you’re looking at the root /Library/Application Support/ directory instead of the ~ home directory one, which should be located at /Users/YOUR_USERNAME_HERE/Library/Application Support/. Take a look there instead and see whether the “FMOD Studio” directory is present.
Following up on this again - did you manage to locate the correct Application Support path? You can also get the user to copy the entire log directly from the Console in Studio, if that’d be easier.
Hi! The user I was able to get the user to open the proper location with “open ~/Library/Application\ Support/FMOD\ Studio”. Thanks!
They are going to collect proper logs the next time the issues happens. I will post them asap. Thank you!
I can’t upload to the forum due to my account being new. But here a link to the logs: [Removed by Admin]
Thanks again!
Thanks for uploading the log. Unfortunately, it hasn’t revealed any additional info, so I’ve taken the liberty of removing the link in case it contains any confidential info.
That said, I’ve done some digging into the standard Perforce integration, and can see that a regular command, likely “p4 login -s”, is occuring, which is probably what is triggering extra authentication when the existing ticket auth has expired.
The standard Perforce integration’s code, which contains the bulk of the logic around p4 calls, can be found in your FMOD Studio install directory at ./scripts/Perforce.sc.js. As a start, I’d recommend modifying line 138 to increase the -vnet.maxwait time, and see whether that provides a simple workaround.
Otherwise, the script makes use of the same Scripting API as Studio’s regular scripts and console, and is also entirely customizable, meaning that you can add console.log() calls to help track down where the issue is occurring and implement a fix.
If the simple workaround isn’t enough, please let me know, and I’d be happy to see what else can be done.
Thank you for removing that and providing additional info!! Extending the wait time seems like a good start. I will do that for the user asap and let you know if we have any luck. Thanks!
1 Like
For some reason the Scripts directory is empty. I’ve looked around and can’t seem to find the Perforce.sc.js file anywhere.
Apologies - on Mac, you’ll need to right click on the FMOD Studio application, select “Show Package Contents”, and find the script in there:
Still no luck unfortunately. We bumped the 10 up to 60 and if FMOD is left open in the background this will keep happening. I’m going to see if I can remove the timeout on P4’s end. Though it would be nice if there was another solution. Please let me know if you have any other ideas. I appreciate your help.
