Have you noted any crashes when exiting Firefox 39.0b7?

Usher wrote:Have you noted any crashes when exiting Firefox 39.0b7?

Hi Usher, Sorry only just seen this, I don't know what your Timezone is, but mine GMT+7 which may explain some gaps in postings being viewed

IF you are referring to Firefox 39.0b7crashing.
It did fail to open properly one time only yesterday and asked if I wished to restore. This was not recorded in about:crashes

*** 1st EDIT ***
I have JUST noticed in My Windows Event Viewer loads of Errors regarding Firefox 39.0b7. Same message with all
Faulting application name: firefox.exe, version: 39.0.0.5647, time stamp: 0x558355f5
Faulting module name: mozglue.dll, version: 39.0.0.5647, time stamp: 0x558355f1
Exception code: 0xc0000005
Fault offset: 0x000024f5
Faulting process id: 0x1bf8
Faulting application start time: 0x01d0af2c63c1fa20
Faulting application path: C:\Program Files (x86)\Mozilla Firefox\firefox.exe
Faulting module path: C:\Program Files (x86)\Mozilla Firefox\mozglue.dll
Report Id: 37fea163-1b21-11e5-9754-c86000272216

I was unaware of these crashes because they ONLY occur when I exit Firefox 39.0b7 and it seemed to close normally and opens the next time correctly (except once as mentioned previously.
Thanks for drawing it to my attention Usher.

*** 2nd EDIT ***

OK, Usher I suspect you already were on to this, and that is why you asked.
I tested by disabling FDM Plugin 1.7.5.1 and then opening and closing Firefox 39.0b7 many times.
NO Windows Event Viewer errors were reported when Firefox closed each time.

I then enabled the FDM Plugin 1.7.5.1 again. Now Windows Event Viewer reports an Error each time Firefox 39.0b7 is closed.
Obviously there is an incompatibility between FDM Plugin 1.7.5.1 and firefox 39.0b7 even though FDM downloads work OK and Firefox seems to works OK until closed.

Hope this helps Usher
Kind Regards, Dave

dko wrote:Obviously there is an incompatibility between FDM Plugin 1.7.5.1 and firefox 39.0b7 even though FDM downloads work OK and Firefox seems to works OK until closed.

Thanks for confirmation.

Usher wrote:

dko wrote:Obviously there is an incompatibility between FDM Plugin 1.7.5.1 and firefox 39.0b7 even though FDM downloads work OK and Firefox seems to works OK until closed.

Thanks for confirmation.

Hi, Usher

Just noticed my FDM Plugin updated today 27th June 2015 to 1.7.5.2.

Firefox 39 Beta still crashes upon exit (which as before I am not aware of except via Windows Event Viewer
As before with FDM Plugin 1.7.5.1 when the FDM plugin is disabled Firefox 39 is not crashing upon exit.

HOWEVER the faulting module HAS changed from mozglue.dll with 1.7.5.1 plugin to ntdll.dll with 1.7.5.2 plugin)
Faulting application name: firefox.exe, version: 39.0.0.5653, time stamp: 0x558b476f
Faulting module name: ntdll.dll, version: 6.1.7601.18839, time stamp: 0x553e8808
Exception code: 0xc0000005
Fault offset: 0x00022322
Faulting process id: 0x1990
Faulting application start time: 0x01d0b0da59116e4d
Faulting application path: C:\Program Files (x86)\Mozilla Firefox\firefox.exe
Faulting module path: C:\Windows\SysWOW64\ntdll.dll
Report Id: cddbe180-1ccd-11e5-974f-c86000272216

Please note: Yesterday my Firefox 39 Beta 7 updated itself automatically, but details only say 39.0 there does not appear to be a 39 beta 8, and 39 has not been released so what it is now I have no idea. I did note last and current Windows Event Viewer crash reports that the Firefox Version has gone up from firefox.exe, version: 39.0.0.5647 to firefox.exe, version: 39.0.0.5653)

Hope this is useful
Dave

Xp sp3, Fx 38.06 & Fx 39.0 RC 5, FDM 3.9.6 build 1556

I just tried the Fx 39.0 RC 5 & FDM 3.9.6 build 1556 pairing on a fresh profile, and I get this type of message whenever I close the browser:

"The instruction at "0x7c90100b"referenced memory at "0x0000001c". The memory could not be "read". Click on ok to terminate the program."

If I disable the FDM plugin, the error does not appear.

No error on same profile when using Fx 38.0.6

Aside from that from the limited time testing it, no other issues so far.

oroville wrote:I just tried the Fx 39.0 RC 5 & FDM 3.9.6 build 1556 pairing on a fresh profile, and I get this type of message whenever I close the browser:
"The instruction at "0x7c90100b"referenced memory at "0x0000001c". The memory could not be "read". Click on ok to terminate the program."
If I disable the FDM plugin, the error does not appear.
No error on same profile when using Fx 38.0.6

The problem is already reported here: viewtopic.php?f=1&t=17249&start=15#p40938
Thanks for another confirmation.

General description of the problem:
If the plugin for Free Download Manager is enabled in Firefox and a download of a file is executed, when pressing Control+W to close the last (and only) opened tab in the browser, the Firefox browser will most likely crash on exit. When the crash occurs, the standard crash reporter of Firefox appears, prompting me to report the crash to Mozilla. If the FDM plugin for Firefox is disabled via the add-ons manager of the browser, the crash doesn't occur. I can't tell for sure if the crash will occur if the FDM monitoring of Firefox is disabled from within FDM, but I think I've tried it and it did crash. The problem is that sometimes it is hard to reproduce the crash and therefore it is hard to test.

Steps to reproduce the problem:
1. Launch FDM.
2. Make sure that the plugin for Firefox is installed and the monitoring of Firefox is enabled from FDM itself.
3. Open Firefox and go to an web page, from witch you can download a file via HTTP or FTP (doesn't matter witch page).
4. Click the file download link and make sure that FDM has started downloading the file.
5. You may wait for FDM to finish downloading the file or stop the download - I think the crash is likely to occur in both cases.
6. After that, go to the Firefox browser and press Control+W one or more times, until all opened tabs are closed and Firefox exits. The Firefox browser will most likely crash, displaying its crash reporter window.

Test environment:
- Operating system: Windows 8.1 Pro N, 64-bit, in Bulgarian with all locale settings set to "Bulgarian".
- Free Download Manager version: 3.9.6 build 1556, in english.
- Firefox version: 38.0.5, 32-bit, in bulgarian.
- FDM plugin for Firefox version: 1.7.5.1.
- FDM Options: Firefox monitoring is enabled; browser context menu integration is disabled; all options in "Video monitoring" are disabled.

If you need some more information from me about the issue, feel free to ask.

k_kolev1985 wrote:If the plugin for Free Download Manager is enabled in Firefox and a download of a file is executed, when pressing Control+W to close the last (and only) opened tab in the browser, the Firefox browser will most likely crash on exit.

The problem seems to be similar to the problem with Firefox 39 beta, but noone reported it for Firefox 38 so far. I suspect now that it may be a problem with some conflicting Firefox extension, not with Firefox itself. The most suspected are:
- tab managing extensions - Tab Mix Plus, Vertical Tabs, etc.
- other download helpers.

k_kolev1985 wrote:Test environment:
(...)
- FDM plugin for Firefox version: 1.7.5.1.

Some bugs are fixed in 1.7.5.2 version. Do as follows:
- close Firefox;
- turn on automatic updates in FDM;
- restart FDM - it should download and install updated plugin on the start;
- open Firefox and make sure the FDM plugin is updated;
- turn off other (possibly conflicting) extensions and restart Firefox;
- run your download/closing tests once again and report if it helped.

k_kolev1985 wrote:If you need some more information from me about the issue, feel free to ask.

Could you list your Firefox extensions with their version numbers, please?

Usher wrote:Some bugs are fixed in 1.7.5.2 version. Do as follows:
- close Firefox;
- turn on automatic updates in FDM;
- restart FDM - it should download and install updated plugin on the start;
- open Firefox and make sure the FDM plugin is updated;
- turn off other (possibly conflicting) extensions and restart Firefox;
- run your download/closing tests once again and report if it helped.

I've tried to update the plugin via your instructions, but when I opened Firefox, the FDM plugin was still 1.7.5.1. Is there another way to update the FDM plugin?

I'll later do the testing with all other extensions disabled, except for the one for FDM and we'll see what happens. If there no crashes, I'll begin to re-enable the extensions one by one and test after each enabled extension. But if someone could lead me as witch of the extensions listed below could be the culprit that would save me some time with the testing.

Usher wrote:Could you list your Firefox extensions with their version numbers, please?

OK, here they are:

BrowserProtect 1.1.3.1-signed
Free Download Manager plugin 1.7.5.1
LastPass 3.1.95
Linkification 1.3.8.1-signed
Navigational Sounds 1.2.4.1-signed
Open With 5.8.1.1-signed
Preserve Download Modification Timestamp 2011.03.21.22.1-signed
SaveLink 3.3.1-signed
uBlock Origin 0.9.9.2
UnMHT 7.3.0.5.1-signed
WebVisum 0.9.1
Logitech SetPoint 6.5 (disabled)

Guest wrote:I've tried to update the plugin via your instructions, but when I opened Firefox, the FDM plugin was still 1.7.5.1. Is there another way to update the FDM plugin?

I'll later do the testing with all other extensions disabled, except for the one for FDM and we'll see what happens. If there no crashes, I'll begin to re-enable the extensions one by one and test after each enabled extension. But if someone could lead me as witch of the extensions listed below could be the culprit that would save me some time with the testing.

That previous post was from me, but I've forgot to log in - sorry about that.

Anyway, I've tried with all other extensions disabled and Firefox still crashed. But the crash reporter took some time to appear. In witch time the CPU load was high. And when I tried during this time to launch Firefox, it told me that it was already running, so Firefox.exe was probably still in the RAM memory. So, the extensions are probably not the issue here. I can most reliably reproduce this issue with a large file (over 100MB) downloaded via FTP. Unfortunately however, the page and files in question are private and I'm not allowed to redistribute them. I'll try to find public examples with witch the bug is easily reproducible.

k_kolev1985 wrote:

Guest wrote:I've tried to update the plugin via your instructions, but when I opened Firefox, the FDM plugin was still 1.7.5.1. Is there another way to update the FDM plugin?

Anyway, I've tried with all other extensions disabled and Firefox still crashed. But the crash reporter took some time to appear. In witch time the CPU load was high. And when I tried during this time to launch Firefox, it told me that it was already running, so Firefox.exe was probably still in the RAM memory. So, the extensions are probably not the issue here. I can most reliably reproduce this issue with a large file (over 100MB) downloaded via FTP. Unfortunately however, the page and files in question are private and I'm not allowed to redistribute them. I'll try to find public examples with witch the bug is easily reproducible.

OK, I've managed to update the FDM plugin to 1.7.5.2 by re-installing FDM from its latest installer (last time I've updated it via the function for updates in the "Help" menu).

I've also found a reliable public page and file download with witch to reproduce the crash:
1. Go to the following web page: http://www.freedomscientific.com/Downloads/JAWS
2. Click on the "JAWS 16.0.3048 32-bit English - June 2015" link.
3. Some time after the download begins (wait until it reaches 15-20%), go to Firefox and close it completely.
4. Immediately after that, go to the downloading operation and stop it.
That should make the CPU go high and some time after that - the Firefox crash reporter should come up.
But with version 1.7.5.2 of the FDM plugin, I couldn't reproduce this, as I was definitely able with v1.7.5.1. Maybe the bug was fixed in the FDM plugin. I'll keep an eye on it and report if it occurs again.

@k_kolev1985, thanks for your reports.
As it's been written earlier, the bug is fixed only partially in 1.5.7.2 plugin - it still crashes Firefox 39.0 beta and RC releases on exit. We must wait for another fix

As you already know, it seems to be a problem with changes in Firefox API in your case, but you should also know, that almost all of your extensions are potentially conflicting with FDM plugin, depending on FDM settings - see below:

k_kolev1985 wrote:

BrowserProtect 1.1.3.1-signed
Linkification 1.3.8.1-signed
Open With 5.8.1.1-signed
Preserve Download Modification Timestamp 2011.03.21.22.1-signed
SaveLink 3.3.1-signed
uBlock Origin 0.9.9.2
WebVisum 0.9.1

You should consider using FDM with "ALT must be pressed" setting enabled. It may prevent some possible crashes and make Firefox more responsive so it's worth some testing, I think.

Usher wrote:As you already know, it seems to be a problem with changes in Firefox API in your case, but you should also know, that almost all of your extensions are potentially conflicting with FDM plugin, depending on FDM settings - see below:

k_kolev1985 wrote:

BrowserProtect 1.1.3.1-signed
Linkification 1.3.8.1-signed
Open With 5.8.1.1-signed
Preserve Download Modification Timestamp 2011.03.21.22.1-signed
SaveLink 3.3.1-signed
uBlock Origin 0.9.9.2
WebVisum 0.9.1

You should consider using FDM with "ALT must be pressed" setting enabled. It may prevent some possible crashes and make Firefox more responsive so it's worth some testing, I think.

For the extensions - OK. I may sacrifice some of them and disable them, if I find any conflicts between them and FDM's plugin.

I tried now "ALT must be pressed" option, but it doesn't work in my case. The reason: I'm mainly a keyboard user, due to my visual disability. If I press ALT+Enter ("Enter" is the alternative to the single left click), nothing happens. I must exactly press ALT and the left mouse button. Even using the screen reader's mouse simulation functionality via the keyboard doesn't work.

If FDM 3.9.6 build 1556 works OK with plugin 1.5.7.2 and Firefox 38.0.5, just wait for another plugin update.
I don't insist on intensive testing if they aren't needed, I'm only informing about possible problems and solutions that you and other users should be aware - now and in the future.