2018.11.04 File menu bar, address bar, blank window Topic is solved

[Isengrim]

Also, I have no idea if this helps, but I downloaded a "portable" copy of firefox 63 (32 bit) and ran it, it works fine.

No, Firefox and Pale Moon are now too different to be reasonably comparable.

I tried building and running both Basilisk and Pale Moon today, for Windows and Linux, and saw no issues. A very strange bug indeed...

[chutsetien]

I’ve encountered the same problem.

I have a Core i9-8950HK CPU, a 64GB memory and a nVidia Quadro P5200 video card. The system of mine is Windows Server 2019 Essentials bd.17763.55. No antivirus software installed (just use the Windows default).

[Moonchild]

Note that "no antivirus installed" is not the same as "using Windows antivirus", please.
If you temporarily disable Windows' AV (defender/MSE/whatever it is called for your system) and then install a fresh copy, does it run?

Having the same happen in Pale Moon means it must be a platform issue if it's a browser code issue, which is strange for the type of behavior seen. Browser init problems like this are almost exclusively caused by chrome javascript erroring out.

One other thing to do, possibly:
Please check if there is a difference between the contents of the zip packed file and what is in your installation folder (compare zip contents with c:\program files\basilisk)

[FranklinDM]

I can confirm the same issue on Basilisk, Pale Moon (latest unstable), and even on the latest build of Interlink. I'm currently running on Windows 10 build 1511, Intel Integrated Graphics. The only antivirus that this laptop has is Windows Defender (which is disabled).

FWIW I first encountered this issue with Interlink but thought that something might have gone wrong with the installation process. However, I wasn't able to reproduce this problem in my main PC (runs dual boot Windows 10 and Windows 7) and in a VM (Ubuntu/Win7/Win10) running on this exact same machine.

EDIT: I've found something weird: DOM Inspector runs fine while I was testing out the broken Basilisk - I was able to open it using the Ctrl+Shift+Right Click shortcut. Visiting pages also work except that JS on these pages doesn't seem to work.

[Moonchild]

Tracking with https://github.com/MoonchildProductions/UXP/issues/865

So it seems like part of the JS engine is having an issue? But only on SOME systems?

[Moonchild]

What build date Interlink has the issue, FranklinDM?

[FranklinDM]

Interlink 52.9.6880 - this is the one that I got from the Binary Outcast site. The Technical Preview (52.9.6846) isn't affected.

[JustOff]

Here is the copy of the previous unstable - palemoon-unstable-20181024044650.win32.zip, does it have the same issue?

[FranklinDM]

Nope, the issue is not present in this unstable version.

[kelendral]

I will add the following:
I have this issue with my Basilisk install when using 2018-11-04 on my Windows 7 Machine. On my Windows 10 machine the exact same profile and install work fine.

When I say exact same:
I copied the following folders from my Windows 10 install to my Windows 7 install.

This normally works just fine. This is how I've been keeping the 2 systems synchronized for my Pale Moon and Basilisk installs for a while now.

On windows 7 I get the same issue as mentioned in this thread. Rolling the installed folder back to 20180927 (without downgrading or doing anything to the profile) works on the Windows 7 machine. This agrees with many others that it is not something in the profile itself but rather something installed at the machine or OS level that is causing the difference/issue.

[Moonchild]

kelendral: are there any specific differences in installed third party software on either machine?

I've made a fully fresh build from the latest commit to the tree to verify (32-bit browser) and there are no issues whatsoever with this on my Windows 7 x64 workstation.
The binary is here: ftp://archive.palemoon.org/trybuilds/basilisk-a0a37ffd4.win32.zip
Please let me know if this is displaying the issue or not? If so, after you've had the issue, please compare contents of the zip with what you installed and report any differences in files and/or size of files, if present (to make sure something hasn't interfered and removed essential components while starting it).

[New Tobin Paradigm]

These builds of Pale Moon and Basilisk originate at an earlier commit (2c045d9c5) before a series of patches that are suspect. Please compare and contrast with the latest tip build above.

http://repository.binaryoutcast.com/artifacts/issue865/basilisk-2c045d9c5.win32.zip
http://repository.binaryoutcast.com/artifacts/issue865/palemoon-2c045d9c5.win32.zip

[chutsetien]

Note that "no antivirus installed" is not the same as "using Windows antivirus", please.
If you temporarily disable Windows' AV (defender/MSE/whatever it is called for your system) and then install a fresh copy, does it run?

Having the same happen in Pale Moon means it must be a platform issue if it's a browser code issue, which is strange for the type of behavior seen. Browser init problems like this are almost exclusively caused by chrome javascript erroring out.

One other thing to do, possibly:
Please check if there is a difference between the contents of the zip packed file and what is in your installation folder (compare zip contents with c:\program files\basilisk)

Hi Moonchild,

Thanks for your reply! I just rollback to the previous version. Sorry, but I need this basilisk profile to work. So I’ll stick with that old version for a while.

[trava90]

Rolling back to the previous version is not going to help anybody solve the problem...

[chutsetien]

It was so weird that when I re-installed it on a virtual machine of mine with the same os (edition/version/build) and the same profile folder, it works fine. So weird!

[chutsetien]

Rolling back to the previous version is not going to help anybody solve the problem...

I need to use this browser to work, okay? I don’t use Basilisk to entertain myself. I use this very browser and its very profile (which is fixed long before) to carry out a very specific and routine work. Before helping others, I NEED TO WORK, is that so hard to understand?

[Moonchild]

Please try to stay calm.

Of course it's very understandable that you have to roll back if you need it for your work. But please also try to understand that we need your help to understand what to work on. None of the people in our dev team can reproduce the issue. I really wish we could -- it would make things 1000x easier. So, when you have time to do so, we kindly ask that you try to work with us to figure out the cause of these problems so they can be fixed.

[kelendral]

There are probably quite a number of software differences between the Windows 7 and Windows 10 machines.
However, as far as security software, both run the same application and both have it set disabled, run on demand.

I should note I see the recommended attempts are all with the 32bit version (which I will give a shot on the Basilisk install). I do normally only use the 64bit versions.

These builds of Pale Moon and Basilisk originate at an earlier commit (2c045d9c5) before a series of patches that are suspect. Please compare and contrast with the latest tip build above.

http://repository.binaryoutcast.com/artifacts/issue865/basilisk-2c045d9c5.win32.zip
http://repository.binaryoutcast.com/artifacts/issue865/palemoon-2c045d9c5.win32.zip

I am typing this on Basilisk 2018-11-06 32bit without issue on my Windows 7 machine.

I cannot say if that worked as I had not tested other 32bit builds on the Windows 7 machine but I can say the 32bit version linked here worked on a machine where the 64bit 2018-11-04 did not.
Basilisk 2018-11-04 32bit and 64bit both had issues on my Windows 7 machine.
Basilisk 2018-11-06 from basilisk-2c045d9c5.win32.zip as posted works fine on the same Windows 7 machine.

[Macca]

kelendral: are there any specific differences in installed third party software on either machine?

I've made a fully fresh build from the latest commit to the tree to verify (32-bit browser) and there are no issues whatsoever with this on my Windows 7 x64 workstation.
The binary is here: ftp://archive.palemoon.org/trybuilds/basilisk-a0a37ffd4.win32.zip
Please let me know if this is displaying the issue or not? If so, after you've had the issue, please compare contents of the zip with what you installed and report any differences in files and/or size of files, if present (to make sure something hasn't interfered and removed essential components while starting it).

This had the same issues.

These builds of Pale Moon and Basilisk originate at an earlier commit (2c045d9c5) before a series of patches that are suspect. Please compare and contrast with the latest tip build above.

http://repository.binaryoutcast.com/artifacts/issue865/basilisk-2c045d9c5.win32.zip
http://repository.binaryoutcast.com/artifacts/issue865/palemoon-2c045d9c5.win32.zip

Tobin's seemed to work without a hitch, so you might want to look deeper into those suspects.

[New Tobin Paradigm]

So it does look like it is in the range of commits we thought.. One or both of us will be flooding you with builds to test to see if we can find the right commit.

As an aside, when stuff like this happens this is a big part of what we all do. Testing builds and rebuilds incrementally in sequence or by high/low comparison to narrow it down to one or more commits. Congratulations, you guys are now developmental testers!

Stand by...