Skip to content
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

Incredibly Slow Performance Since 1.22 #199

Open
OnWingsOfValor opened this issue Jul 18, 2023 · 15 comments
Open

Incredibly Slow Performance Since 1.22 #199

OnWingsOfValor opened this issue Jul 18, 2023 · 15 comments
Labels
help wanted Extra attention is needed needs research

Comments

@OnWingsOfValor
Copy link

So, I dunno if it's just me, or not, but ever since the sidebar profiles feature got added, the performance for Rising has absolutely went into the trash. Logging in can be a gamble if it goes at a normal speed or will hang for a long period of time, and getting about half of the profiles I go to look at to load in-client takes upwards of a minute. It's...really frustrating, to say the least.

@hearmeneigh
Copy link
Owner

Are you on 1.23.5? It should address this very issue.

@OnWingsOfValor
Copy link
Author

I am, I've stayed up-to-date on both devices I use (Win10 desktop, Win11 laptop), and the issue's been A Thing on both of them.

@hearmeneigh hearmeneigh added help wanted Extra attention is needed needs research labels Jul 23, 2023
@hearmeneigh
Copy link
Owner

Anyone willing to help, this needs more information – I'm not seeing this issue on Win11.

@kazeookami
Copy link

kazeookami commented Aug 19, 2023

This is still an issue for me on Win11, as recently as 2 minutes ago. If I am looking at the console or a single Pm it's fine. If I am in a large channel it can end up bogging down my entire computer for a few seconds, or up to several minutes.

What can I provide to assist with this?

@hearmeneigh hearmeneigh pinned this issue Aug 19, 2023
@hearmeneigh
Copy link
Owner

@kazeookami

1 – Collect terminal logs

  1. Start F-Chat.exe from Command Prompt / terminal. This will let you see the logs it prints.
  2. Set F-Chat menu (cogwheel, top left) > Rising > System Log Level to Silly
  3. Let the chat run for 1-2 minutes
  4. Set the log level back to normal -- 'silly' can slow down the app
  5. Copy-paste the logs from the terminal.

    Warning The logs may contain information about you, your computer, internet connection, and/or your character.
    Make sure you black out any information you are not willing to share.

2 – Collect browser logs

(This may not work, I don't remember if it's disabled on the production build)

  1. Start F-Chat.exe normally
  2. After starting, press RIGHT CONTROL + RIGHT SHIFT + L to open Javascript console
  3. Let the chat run for 1-2 minutes
  4. Set the log level back to normal -- 'silly' can slow down the app
  5. Copy-paste the logs from the JavaScript console

    Warning The logs may contain information about you, your computer, internet connection, and/or your character.
    Make sure you black out any information you are not willing to share.

If you prefer to send the logs privately, send them as a note on F-Chat to FCR

@hearmeneigh
Copy link
Owner

hearmeneigh commented Aug 25, 2023

Oh, also: Please collect logs about when the issue is occurring. If you send me 20 minutes of logs and there's 10 seconds of the problem there, it'll be too hard to find...

@OnWingsOfValor
Copy link
Author

I attempted to do both of these things - and the first, both through Command Prompt and Terminal/Powershell. Neither option on the first seemed to print any kind of logs, and the JavaScript thing didn't open anything for me.

@hearmeneigh
Copy link
Owner

@OnWingsOfValor @kazeookami This slowdown issue should be addressed in the 1.24 release. Can you verify, please?

If you still see some slowdowns, please try collecting the logs again. You should be able to see the browser consoles if you start F-Chat.exe with --devtools parameter. You can find the log files here.

@OnWingsOfValor
Copy link
Author

@hearmeneigh Still having the issue, not entirely sure if I've collected the logs correctly, but. Here's something, at least.
Logs.txt

@digital-love
Copy link

This issue exists in Linux as well. I've tried Arch based distros, Ubuntu, Debian, Fedora, etc. Even with multiple desktop environments, GNOME, KDE, and Cinnamon. I believe that this is just a general issue with the client. I've got nothing much to present but I do have observations of how the issues begin.

Previewing links seems to slow it down over time, it happens a lot faster when viewing a YouTube video or an animation. The websites don't seem to be relevant, it's like the client just keeps loading everything into memory and won't unload it. This eventually leads crashing, sometimes even the desktop goes with it.

If you have any instructions that could help me contribute more useful information, let me know.

@kazeookami
Copy link

I swear I commented a couple weeks ago with confirmation the bug still exists.

Okay so I was not able to figure out how to get the terminal/browser logs when you first suggested it in august and being an ADHD gremlin i forgot to come back and ask for a more detailed explaination on how to not be stupid.

Last night and today the lag got so bad and I couldn't fight my way out of it, to the point I had to hard reboot the entire computer. So I revisited and saw your post from September 3rd and I was able to get the console for that to appear. Unfortunatley, I could not replicate the bug while those consoles were open. Which is rather odd seeing as I can 100% reliably replicate it any other time.

So, I went to the logs folder, deleted everything, and started F-chat up and replicated the bug right on cue, then fought my way out of it without provoking a crash, and zipped the logs. Overall the logs should have a time span of less than a whole minute. Here those are...
logs.zip

My method for being able to replicate this immense lag spike is pretty simple.
Launch and log into the client.
Go to a large room Typically 100 users is enough but sex drive LFRP makes it most easy to replicate
Hover mouse over the user list, and mouse wheel down.

Typically I will the spike within a few seconds. Then to fight my way out of it I try to get my mouse over to the PMs list and click on one. If I can succeed before the client white boxes, then it will switch to the PM and the lag will vanish in a second or two.

If I fail to get there in time and end up spending several minutes trying to get to a PM to click, the lag is so intense that it will actually slow down the clock in windows. One particular time where I was patient enough to let it play out for about 10 minutes to see if it would clear on it's own, the clock was 7 minutes behind by the time I broke free.

@MysteriousSwordsman
Copy link

I, too, am experiencing near computer freezing lag when in the Sex Driven LFRP rooms since I updated to the latest version. Is there anyway I can turn the side-loading profiles off to get better performance? Or would I have to downgrade to pre1.22 in order to do this?

I am trying to get the logs, but as stated by the person above me, it is not the easiest to do since it slows down the whole machine and crashes the application.

@TheTrueNeptune
Copy link

I also notice very slow performances with the client. Some profiles take up to 4 minutes to load partially. The little icons that show the profile pictures in chat also don't load for quite a long time. When I hover over a profile name and the preview window opens, it also takes almost 5 minutes for it to load.

@OnWingsOfValor
Copy link
Author

Yeah, the profiles seem to take even longer and longer to load as time goes on. I just tried to downgrade to 1.21.2, but I couldn't even log in on that, it never moved past the setting up spinny-circle.

@kazeookami
Copy link

Still an issue on 1.26.2 with no news in 4 months. I guess this is just a permanent issue now. May as well go back to regular f-chat client without Rising.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed needs research
Projects
None yet
Development

No branches or pull requests

6 participants