Basilisk remains active after exit (Linux)

[fatboy]

Good Day,

I have Basilisk installed via the tarball extraction method on two different Linux computers. Both are Debian based, mxlinux and Antix Linux. The issue below happens on both machines.

I first noticed this issue when I was using the photonic theme, I would quit Basilisk and noticed that it kept running in the background and refused to launch. Another issue I had was, after you install an addon that requires a browser restart, you click restart and nothing happens. Again, due to basilisk running in the background. It could also be that basilisk takes "long" to terminate, after 5 min of waiting one can relaunch basilisk after closing it.

The error console shows no errors?

EDIT: This issue also seems true for Pale Moon. Must be the latest update which introduced a regression

Thanks

[moonbat]

Must be the latest update which introduced a regression

No regression as far as Pale Moon is concerned, it quits just fine.

[fatboy]

I want to upload a screenshot, but I can't. http code error

[Mæstro]

Try uploading to Cockfile or Catbox.

[Moonchild]

Off-topic:

I want to upload a screenshot, but I can't. http code error

Sorry about that. Should be fixed now. too tight checks on user posting ;P

As for not shutting down... I believe basilisk also uses the process watchdog which will crash itself after like a minute if the process refuses to close. That should(?) also be active on Linux, allowing you to restart it without having to manually kill it.
It's possible an extension is preventing proper shutdown too; see if any of the ones you are using could be the issue?

[Basilisk-Dev]

I was able to replicate this once with the current Basilisk release on Fedora 37. In the instance in which I was able to replicate it I had multiple sites open including YouTube, the Pale Moon Forum, eBay, the Pale Moon repo, Reddit, and GitHub. I had about 30 tabs open. Sadly I didn't think to take a list of the sites I had open when I did it, but looking at my browser history for today those are all of the sites I visited today.

I had to manually kill the basilisk process.

I haven't been able to replicate this again, I tried a clean profile, I tried running my profile in safe mode, and I tried running in my regular profile with all of my extensions enabled.

[fatboy]

Here is the message I am getting

EDIT: So it seems that the restart issue happens within the first minute of quitting. Like Moonchild said with the process terminating after a minute. However, this still creates an issue when one needs to restart the browser after a new addon has been installed.
Or when you change theme and need to restart (Pale Moon seems fine when I need to restart after theme change, but Basilisk still has this running process issue).

EDIT: When switching from the default Basilisk theme to Photonic, the browser restarts, but switching from photonic to default is where the browser refuses to restart and I have to wait for the background service to kill itself before launching Basilisk again

[Wastelander]

I experience the same issue, but only when I change the theme to Photonic, switching back to default resolves the hang.

[Lootyhoof]

Seems to be a regression specific to 2023.01.26, but I'm not entirely sure why since Pale Moon isn't affected. Odd..

[BobbyW]

Seems to be a regression specific to 2023.01.26, but I'm not entirely sure why since Pale Moon isn't affected. Odd..

It's probably due to the simple fact that PM & Basilisk are now two completely independent ventures, whereas at one time they were linked under the same roof.....so there will probably be more differences as time goes on......as I see it Basilisk will most probably continue to be "Beta", & as long as it still works well & breathes, I have nothing to complain about here.

At this time I would like to thank Basilisk-Dev for rescuing Basilisk , & making it the fine browser it is today.....hopefully for a long to come

[Wastelander]

Unfortunately, this affects PM 32 on Linux too. Fresh install, no other addon than Photonic theme.

[Wastelander]

I tried the browsers on Windows and Photonic does not have any issues, unfortunately it's something related to Linux.

[EchedeyLR]

It is surprising to me that by reading some interesting threads I see an issue I have been experiencing.

I am also experiencing it with the Photonic theme, but I am sure that is related after installing an extra recommended addon in the theme.

I am using Pale Moon in its latest version.

[Wastelander]

I am sure that is related after installing an extra recommended addon in the theme.

Nice to see that this thread is still alive. Which addon are you referring to? I experience this issue on a clean profile, with no addon installed apart from Photonic theme.

[EchedeyLR]

I am unsure but Stylem could be causing the issue from my side.

However, something seems related to the Photonic theme here which I am using too. In another testing, it seemed that is just Photonic to be the one causing the issue itself.

[Lootyhoof]

As it doesn't seem to affect other themes (at least on the Pale Moon aspect) I can only assume this is because Photonic makes extensive use of SVG for images instead of e.g. PNG. I guess there has been a regression in UXP causing this.

I unfortunately haven't really had the time as of late to delve further into that, though.

[Wastelander]

Hey @Lootyhoof nice to see you back, actually the issue also appears using ONLY Stylem without Photonic, don't know if this detail might help digging deeper into the issue.