Pale Moon forum

Hey,
I'm having crash while accessing url: ks3-cz.travian.com with palemoon 26.0.1 (x64) with message:

Trying to allocate an infallible array that's too big
Segmentation fault (core dumped)

There seems to be a bug on bugzilla@mozilla about this https://bugzil.la/892930 but of course I don't know if root cause is the same.

If any more info is needed, I'll be happy to provide.

EDIT: you have to have account and log into your village in order for crash to appear

Moderator Note: Please use meaningful titles as demonstrated in the forum rules Section 4b.

This doesn't seem to be an issue on Windows.. So yeah, Travis will have to check it out..

Can you please provide more information such as distro, extensions, plugins, etc.

Also, Has 26.0.1 actually been released yet?

Sure Oh, I should've probably mentioned that it works fine on Windows, sorry :/

Distro: Archlinux
Extensions: uBlock Origin, Pentadactyl
Plugins: None
Monitor setup: dualhead

regarding 26.0.1: I'm using AUR package https://aur.archlinux.org/packages/palemoon/ , which builds 26.0.1_Release tag from https://github.com/MoonchildProductions/Pale-Moon , so I would say it was released? Or at least it has release tag in git.

EDIT: CXXFLAGS="-march=x86-64 -mtune=generic -O2 -pipe -fstack-protector-strong --param=ssp-buffer-size=4" might be useful too? I don't know if palemoon uses environment CXXFLAGS or it defines it's own.

This should NOT have been released by them... Please go back to 26.0.0 in the mean time..

This should NOT have been released by them

Can you please expand on that? I though that existence of release tag means it was released? If you could explain it to me a bit, I'll post it to the AUR package notifying them to downgrade to 26.0.0 (but I need some argument).

In the mean time I'm building 26.0.0 to see if this bug is there too.

Just because it is tagged in the repo does not mean it is released.. It still goes through a last minute internal testing.. Only when we release ourselves for general linux and of course Windows is it actually considered released.

There is a flaw in 26.0.1 that may or may not be related to the issue here. (I don't know how it presents its self on Linux) that has caused us to scrap release and draft a new one (26.0.2) to be released soon.

Matt A Tobin wrote:There is a flaw in 26.0.1 that may or may not be related to the issue here

It is, the crash does not occurre in 26.0.0.

wolf_ wrote:

Matt A Tobin wrote:There is a flaw in 26.0.1 that may or may not be related to the issue here

It is, the crash does not occurre in 26.0.0.

Assuming it is the same thing.. Guess we shall know in a few days But do please keep us updated.

For the record, I'm unable to reproduce the issue with the url given with v26, v26.0.1, or v26.0.2 on my Manjaro box.

do you actually have account there? you have to log in and see you village in order for crash to appear