PDA

View Full Version : Closed Out FGU to the Main Screen and Logging Popped Up with an Error?


Netjera
April 13th, 2021, 08:40
Wasn't sure if this error meant anything that I had to worry about. Wanted to throw it up here to see if it's something that should be submitted as a bug?

https://gyazo.com/68b1153dc41470f8abdf80fe032efeb3
Moon Wizard
April 13th, 2021, 17:16
That error is sort of a hook I specifically left in to notify us when things didn't get cleaned up correctly for Lua objects (and thus general cleanup indirectly).

While I have seen a couple scenarios where this happens still, I haven't found the steps to reproduce the scenario. If you have steps that cause every time, I would appreciate them.

Thanks,
JPG
anathemort
April 13th, 2021, 17:43
I see this fairly often when the GM exits FG before the player(s). I'll try to get a log capture next time it occurs.
Moon Wizard
April 13th, 2021, 22:56
We know about the GM exiting before players (if the GM closes uses operating system X button, instead of return to launcher). We haven't figured out how to stop that one yet.

We're looking for any other scenarios.

Thanks,
JPG
anathemort
April 15th, 2021, 19:54
I'm sending an email to support-files with logs from a session where we just got bumped and got the cleanup error. Unfortunately as we were (are) mid-session, I couldn't get the DM logs. The DM had just shared an image with us and had a network hiccup, as indicated by the fact that in the lobby, they were offline for about 30 seconds before reconnecting to the cloud network.
Moon Wizard
April 15th, 2021, 23:52
Thanks for the logs. It looks like a GM disconnect scenario; which is known to generate these errors currently. When the GM returns to lobby by choice, the player client is able to perform cleanup fully. It's something on our list to look at long term.

Regards,
JPG
Netjera
April 21st, 2021, 10:06
That error is sort of a hook I specifically left in to notify us when things didn't get cleaned up correctly for Lua objects (and thus general cleanup indirectly).

While I have seen a couple scenarios where this happens still, I haven't found the steps to reproduce the scenario. If you have steps that cause every time, I would appreciate them.

Thanks,
JPG

I haven't been playing with anyone, I've been working on my campaign, using a private instance connected to the cloud. I'll try to pay attention when I exit and see if I can get it to happen again. :)