Stored passwords wiped. AGAIN.

[Octopuss]

I know, but this has been going on for so long I just curse it out when I find out. More imporantly though, when I am prompted to save a password, it can easily have been months since the password was deleted, because again, what's the default amount of time a website login is kept in cookies? (or however it works)

[Octopuss]

Heh, first crash just as I reloaded Amazon.de
Passwords seem intact.

Code: Select all

Faulting application name: palemoon.exe, version: 6.8.0.9420, time stamp: 0x68f0c050
Faulting module name: mozjs.dll, version: 0.0.0.0, time stamp: 0x68f0c1e9
Exception code: 0xc0000005
Fault offset: 0x000000000037f9ba
Faulting process id: 0x2A70
Faulting application start time: 0x1DC85FBA63F9143
Faulting application path: C:\Program Files\Pale Moon\palemoon.exe
Faulting module path: C:\Program Files\Pale Moon\mozjs.dll
Report Id: 8d295915-7bb9-43d9-9b0d-dcdc2fc04a30
Faulting package full name: 
Faulting package-relative application ID: 

[Moonchild]

That looks like one of the pertinent crashes to desktop that were fixed for 34.0

[Octopuss]

I get these occasionally (totally random crashes to desktop) and have been for a long time. Often enough to feel suspicious about my PC (which is otherwise stable and passed 8-12 hours of multiple different stress tests) but still somewhat uncommon to always wave it off as a random crap that's impossible to troubleshoot.

Just curious, how do you even figure out what's causing these as a dev?

[Moonchild]

Off-topic:

Just curious, how do you even figure out what's causing these as a dev?

Having the crash address and module (in this case mozjs.dll) gets me quite far in finding out where the crash occurred.
I keep the object tree of release builds, which allows me to have all the symbols and compiler intermediates handy for the final release builds like what you're running, allowing debugging of running programs built in that tree.
Basically, the method is:

1. Look at the crash module (mozjs.dll) and the offset address (0x000000000037f9ba)
2. Run the release version of the browser
3. Fire up Visual studio and attach the debugger to the running browser
4. Pause execution in the debugger (making sure it's paused in our code, not a system call)
5. Look up the base address of the loaded module that crashed (in VS's modules pane) - This is needed because of ASLR.
6. Use a hex calculator to find the exact address in the running browser (add offset to base)
7. Jump to the address in the disassembly view. This will pinpoint the exact crash statement
8. Usually I then use "go to source code" for an easier view without raw assembly.

Once the exact crashing code is pinpointed, it's usually pretty clear what caused the crash if there's a problem in the code right around that point. If not, then a crash dump will be necessary because that will give both the exact call stack (all the nested function calls leading to the crashing function) and can often record the specific values passed into functions as well (there's a wealth more information in a dump than just having a crash address).

This doesn't always work, especially not when it's something deep inside JS, dealing with garbage collection, or some exotic shenanigans in C++ or if the code in question has been optimized away by the compiler into a binary blob without direct references.

I hope that's clear!

[Octopuss]

Off-topic:
Oh ok!
So let's say in the case of the most recent examples of these weird crashes that you managed to solve, was it some Mozilla code (which I assume what it is judging by the file name) that simply didn't play nice with PM or what kind of obscure problem?

[Octopuss]

Not related to the topic, but I've just had another weird instant crash.

Faulting application name: palemoon.exe, version: 6.8.0.9517, time stamp: 0x6970a7ed
Faulting module name: mozjs.dll, version: 0.0.0.0, time stamp: 0x6970a979
Exception code: 0xc0000005
Fault offset: 0x00000000003b6e48
Faulting process id: 0x40D0
Faulting application start time: 0x1DC8EA6F7BA7F33
Faulting application path: C:\Program Files\Pale Moon\palemoon.exe
Faulting module path: C:\Program Files\Pale Moon\mozjs.dll
Report Id: 0f6217e9-8d24-4221-8ee3-8f57dd295908
Faulting package full name:
Faulting package-relative application ID:

[Octopuss]

and another

Faulting application name: palemoon.exe, version: 6.8.0.9517, time stamp: 0x6970a7ed
Faulting module name: xul.dll, version: 6.8.0.9517, time stamp: 0x6970a987
Exception code: 0xc0000005
Fault offset: 0x000000000087dc29
Faulting process id: 0x3F8C
Faulting application start time: 0x1DC8FA229B1BCC6
Faulting application path: C:\Program Files\Pale Moon\palemoon.exe
Faulting module path: C:\Program Files\Pale Moon\xul.dll
Report Id: 69a9d61f-d202-4f7b-8814-9a7cccbad4ca
Faulting package full name:
Faulting package-relative application ID:

[andyprough]

Maybe a bad memory stick??

Or has it been a long time since you cleaned the internal fans and changed thermal paste?

[Octopuss]

Ugh, what? No.

[Bilbo47]

When PM doesn't fill in a password ... I click into username field, it usually shows up, then I press tab to get to password, and then PM usually fills it. [Otherwise] I use Keepass's keyboard shortcut

KeePass in particular, without any add-on, fills login fields only when the hotkey is pressed. One could test/prove this by ensuring KeePass is not running, then start PM, and visit a site that requires logging in whenever the browser was restarted. The site that works like that for me is PM forum. This would show how PM by itself works with auto-fill fields.

A different program KeePassXC works more tightly with FF forex while still not-being an add-on. Username field forex displays a KPCX icon, reminding user to first unlock the password vault so that password can be passed from vault to browser.

Other options like add-ons provide a bridge between the vault program and the browser, and they can further take over the browser's built-in auto-fill feature.

[Moonchild]

Not related to the topic, but I've just had another weird instant crash.

If not related to the topic, please don't post in it.

If you're having crashes, you can also just report them on the issue tracker (don't lump them together if the crash signatures are different! in general one issue per crash if they are in different modules or at different offsets) or alternatively put them in their own thread on the forum.

[Octopuss]

When PM doesn't fill in a password ... I click into username field, it usually shows up, then I press tab to get to password, and then PM usually fills it. [Otherwise] I use Keepass's keyboard shortcut

KeePass in particular, without any add-on, fills login fields only when the hotkey is pressed. One could test/prove this by ensuring KeePass is not running, then start PM, and visit a site that requires logging in whenever the browser was restarted. The site that works like that for me is PM forum. This would show how PM by itself works with auto-fill fields.

A different program KeePassXC works more tightly with FF forex while still not-being an add-on. Username field forex displays a KPCX icon, reminding user to first unlock the password vault so that password can be passed from vault to browser.

Other options like add-ons provide a bridge between the vault program and the browser, and they can further take over the browser's built-in auto-fill feature.

I don't understand what are you telling me. I know how Keepass works, I've been using it for years.

[Octopuss]

Not related to the topic, but I've just had another weird instant crash.

If not related to the topic, please don't post in it.

If you're having crashes, you can also just report them on the issue tracker (don't lump them together if the crash signatures are different! in general one issue per crash if they are in different modules or at different offsets) or alternatively put them in their own thread on the forum.

Where is the issue tracker though? I don't see any link on the main website. There is nothing in the FAQ section of the forums either.

[jobbautista9]

From the contact page:

Please post in the public boards for any technical support questions, unconfirmed bugs or general feedback, taking care to use the board that best matches your type of question or feedback. If you have a security issue to report, please use the info found on this website in the standard .well-known/security.txt location. If you are reporting a confirmed bug for our developer community to look at, please go to https://repo.palemoon.org/ -- Front-end browser issues belong in MoonchildProductions/Pale-Moon, while the majority of issues dealing with everything else belong in our platform repo MoonchildProductions/UXP.

[Mæstro]

info found on this website in the standard .well-known/security.txt location.

Swedish is specified with Sweden’s country code, presumably in contrast to Finland, but Dutch is not specified with Holland’s, as opposed to Belgium for Flemish. How curious…

[andyprough]

Ugh, what? No.

I'm not sure what this response is supposed to communicate, but if I was having these kinds of crashes I'd want to make sure I'm not having memory issues or overheating. There are programs for all OS's that allow you to monitor CPU temperature and to test your memory sticks. And if you haven't cleaned your fans and changed your thermal paste for a long time, that can have a major impact on proper cooling.

[Octopuss]

From the contact page:

Please post in the public boards for any technical support questions, unconfirmed bugs or general feedback, taking care to use the board that best matches your type of question or feedback. If you have a security issue to report, please use the info found on this website in the standard .well-known/security.txt location. If you are reporting a confirmed bug for our developer community to look at, please go to https://repo.palemoon.org/ -- Front-end browser issues belong in MoonchildProductions/Pale-Moon, while the majority of issues dealing with everything else belong in our platform repo MoonchildProductions/UXP.

Tracker and posting in forums are two totally different things. I was thinking there was a Github page or something, but I guess it works completely differently with PM.

Ugh, what? No.

I'm not sure what this response is supposed to communicate, but if I was having these kinds of crashes I'd want to make sure I'm not having memory issues or overheating. There are programs for all OS's that allow you to monitor CPU temperature and to test your memory sticks. And if you haven't cleaned your fans and changed your thermal paste for a long time, that can have a major impact on proper cooling.

It's supposed to mean it's irrelevant. My PC is rock stable, which I know for a fact. If there were any such problems,I wouldn't get a (edit) just random occasional crashes with one specific program that doesn't do anything terribly specific.
If I can pass 12 hours of multiple different stress tests, I think it's safe to assume the program itself (or in this case whatever inherited Firefox garbage or something) is the culprit.

But you do have a point this could be an indicator of a hardware problem under different circumstances.

[Moonchild]

Off-topic:

info found on this website in the standard .well-known/security.txt location.

Swedish is specified with Sweden’s country code, presumably in contrast to Finland, but Dutch is not specified with Holland’s, as opposed to Belgium for Flemish. How curious…

Primarily because I only really know Swedish as spoken in Sweden (not the other territories, like Finland where the variant is högsvenska), and have no trouble with Flemish or even South-African Dutch variants close to Afrikaans or literally any flavour of English, so it's all good (so not specified). And it tends to be clearer that it's Swedish if specifying the country code (which everyone knows) while "sv" might be mistaken for something else (country code for El Salvador, or Fips-10 for Svalbard , and some might mistakenly think Slovenian too).

[andyprough]

It's supposed to mean it's irrelevant. My PC is rock stable, which I know for a fact. If there were any such problems,I wouldn't get a (edit) just random occasional crashes with one specific program that doesn't do anything terribly specific.
If I can pass 12 hours of multiple different stress tests, I think it's safe to assume the program itself (or in this case whatever inherited Firefox garbage or something) is the culprit.

But you do have a point this could be an indicator of a hardware problem under different circumstances.

Sorry, I looked up your graphics card just now and that's recent vintage, I'm often talking to people with much older hardware on this forum but that's not you. I shouldn't have assumed you were using old equipment.

Are you using antivirus of any sort? I see that those programs are sometimes implicated in similar application crashes. For example in the discussion of this report of Chrome crashing on Windows: https://learn.microsoft.com/en-us/answe ... correctly-(0xc