/kbin meta

2 readers

1 users here now

Magazine dedicated to discussions about the kbin itself. Provide feedback, ask questions, suggest improvements, and engage in conversations related to the platform organization, policies, features, and community dynamics. ---- * Roadmap 2023 * m/kbinDevlog * m/kbinDesign

founded 1 year ago

[Possible bug] kBin keeps freezing on Firefox (kbin.social)

submitted 1 year ago by Balssh@kbin.social to c/kbinMeta@kbin.social

8 comments fedilink hide all child comments

As the title says I've noticed that in the past day kBin often freezes up when I view a thread (Firefox pops up asking me if I want to stop the tab or not). I use Firefox on EndeavourOS but I didn't have any problems with it for the past 2 weeks.

Is anyone else encountering this/is it a new bug?

you are viewing a single comment's thread
view the rest of the comments

[–] shazbot@kbin.social 1 points 1 year ago (1 children)

Itemize what extensions you are running and try creating a vanilla prefix (firefox -P), then testing it there, and use process of elimination to narrow down which one(s) may be the root cause.

[–] Balssh@kbin.social 1 points 1 year ago (1 children)

Could you be more specific? I kind of get what you are saying, but I didn't test extensions until now so it's kind of an alien language.

[–] shazbot@kbin.social 1 points 1 year ago (1 children)

Well, if you aren't running browser extensions (add-ons) in your browser, then that can't be the cause. Sometimes extensions may conflict with the browser and drag performance, so it can be good to get closer to a vanilla state, but sounds like you already are there.

[–] Balssh@kbin.social 1 points 1 year ago (1 children)

Sorry for misunderstanding, I should've been more clear: I do use extensions, namely uBlock, Tampermonkey and bitwarden, but I was also using them when everything ran smooth.
What I meant I didn't quite understand was "try creating a vanilla prefix (firefox -P), then testing it there".

[–] shazbot@kbin.social 2 points 1 year ago

You can create a new prefix/profile with no extensions in it and use this as a "control" to test whether it works without those. Then, on your normal profile, start by enabling only one extension, then two, etc., to try to drill down to see if it's localized to a particular one.