FossaMail x64 doesn't work

[pollo]

Hi,

I just tried v27, for the first time.
I have v25.2.4 x64 installed on windows 7 pro, and working well for a long time.

I used the installer, installing to the same location of the previous version (upgrade), and when trying to open Fossa, I get: "FossaMail has stopped working" (a windows message).
I get this for both, the portable (zip) and the installer.

Using the x32 works with no problems.

Please advise.

[Moonchild]

Please include the exact output of your crash e.g. using AppCrashView.

[pollo]

There's no crash report for this error.

I attached the error screen I get to this post.

Hope it helps.

[New Tobin Paradigm]

That dialog box doesn't exactly look right...

[pollo]

That is the only thing I get. It is not cropped in any way.

[Moonchild]

Please use AppCrashView to get a crash report.

[pollo]

Please use AppCrashView to get a crash report.

I did. The first time you asked, and as I said:
There's no crash report for this error on AppCrashView.

The only thing I got was the screen I attached.

[Moonchild]

I'm afraid we can't do anything to help you in that case. The appcrash window should have more details about the crash, and appcrashview should have an error report to display. Did you by any chance disable system services like the Windows Error Reporting serivce?

[pollo]

I'm afraid we can't do anything to help you in that case. The appcrash window should have more details about the crash, and appcrashview should have an error report to display. Did you by any chance disable system services like the Windows Error Reporting serivce?

No, I didn't.

In addition to my question here, I was also looking for a solution online, and based on something I found, I did the following:

Opened the properties of FossaMail.exe, and set the compatibility mode to "Windows 7".

Doing that, it works.

However, I don't know if that means I simply forced the program to run as x32.
If that's the case, then I can simply run the x32 itself.

When fossamail runs with that change, I do not see in the "about" the (x64) I used to see next to the app name in v25.
Edit:
Sorry, you should have said "Event Viewer", and here's what I found there:

Faulting application name: FossaMail.exe, version: 27.0.0.6232, time stamp: 0x58862e37
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x000000006fff0d2a
Faulting process id: 0x1304
Faulting application start time: 0x01d281e91c29893f
Faulting application path: C:\Portable\Internet\Email\FossaMail-27.0.0.win64\FossaMail-win64\FossaMail.exe
Faulting module path: unknown
Report Id: 59d75c4d-eddc-11e6-806c-005056c00008

[pollo]

As in my previous report of v27 x64:
When I try to open fossamail x64, I get the attached error.
In Event viewer I get this report:

Faulting application name: FossaMail.exe, version: 38.0.0.6255, time stamp: 0x58a3a103
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x000000006fff0d2a
Faulting process id: 0x1e60
Faulting application start time: 0x01d289c7e9513cf0
Faulting application path: C:\Portable\Internet\Email\FossaMail-win64\FossaMail.exe
Faulting module path: unknown
Report Id: 27115fc2-f5bb-11e6-806c-005056c00008

If I open FossaMail.exe properties and set the compatability mode to "Windows 7", it works without a problem

OS:
Windows 7 pro
Note:
Fossamail v25 x64 works without any problems.

Error screen:

fossamail-38-error.jpg

[New Tobin Paradigm]

0xc0000005 is an memory access violation error.. Make sure you aren't using some insane sandboxing and/or security software that may be preventing normal operation. Also, check to see if your ram is ok..

[Moonchild]

It's still unknown why you get this (very limited) error with no details of the crash.
It's also peculiar that you don't get this crash when setting Compatibility Mode to Windows 7 while being on Windows 7, unless something external hooks into it or controls its run-time operation that wants to make it run in an older compatibility mode (which would predictably cause issues because FossaMail will use Win 7 capabilities that may not be present in older compat modes).

Also, changing compatmode doesn't "magically" transform the program to a different architecture. You're still running the 64-bit version.
The about box in v27/v38 will not show the bit-ness, but help -> troubleshooting information will show it.

By the way, including that (copy as text) would probably help to understand the environment you're working in.

[Moonchild]

Merged the two topics - no reason to have two threads for the same thing.

[pollo]

help -> troubleshooting (accounts info deleted)

Application Basics

Name: FossaMail
Version: 38.0.0
User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:3.0) Gecko/20100101 Goanna/20170215 FossaMail/38.0.0
Profile Folder: Show Folder

(Local drive)
Application Build ID: 20170215005340
Enabled Plugins: about:plugins
Build Configuration: about:buildconfig
Memory Use: about:memory

Mail and News Accounts

Extensions
Account Colors, 9.2, true, accountcolors@DW-dev
AttachmentExtractor, 1.3.5.1, true, {35834d20-efdb-4f78-ab77-9635fb4e56c4}
BiDi Mail UI, 0.9.8, true, {54e72d7b-ed31-4736-854f-f517358f21ee}

Important Modified Preferences

Name: Value

browser.cache.disk.capacity: 358400
browser.cache.disk.parent_directory: C:\Tmp
browser.cache.disk.smart_size_cached_value: 358400
browser.cache.disk.smart_size.first_run: false
browser.cache.disk.smart_size.use_old_max: false
extensions.lastAppVersion: 38.0.0
font.internaluseonly.changed: true
font.language.group: he
font.name.monospace.el: Consolas
font.name.monospace.tr: Consolas
font.name.monospace.x-baltic: Consolas
font.name.monospace.x-central-euro: Consolas
font.name.monospace.x-cyrillic: Consolas
font.name.monospace.x-unicode: Consolas
font.name.monospace.x-western: Consolas
font.name.sans-serif.el: Calibri
font.name.sans-serif.he: Calibri
font.name.sans-serif.tr: Calibri
font.name.sans-serif.x-baltic: Calibri
font.name.sans-serif.x-central-euro: Calibri
font.name.sans-serif.x-cyrillic: Calibri
font.name.sans-serif.x-unicode: Calibri
font.name.sans-serif.x-western: Calibri
font.name.serif.el: Cambria
font.name.serif.tr: Cambria
font.name.serif.x-baltic: Cambria
font.name.serif.x-central-euro: Cambria
font.name.serif.x-cyrillic: Cambria
font.name.serif.x-unicode: Cambria
font.name.serif.x-western: Cambria
font.size.fixed.el: 14
font.size.fixed.tr: 14
font.size.fixed.x-baltic: 14
font.size.fixed.x-central-euro: 14
font.size.fixed.x-cyrillic: 14
font.size.fixed.x-unicode: 14
font.size.fixed.x-western: 14
font.size.variable.el: 17
font.size.variable.tr: 17
font.size.variable.x-baltic: 17
font.size.variable.x-central-euro: 17
font.size.variable.x-cyrillic: 17
font.size.variable.x-unicode: 17
font.size.variable.x-western: 17
mail.openMessageBehavior.version: 1
mail.winsearch.firstRunDone: true
mailnews.database.global.datastore.id: f455af06-f6d3-4f04-91a1-c4a77196a2c
network.cookie.lifetimePolicy: 2
network.cookie.prefsMigrated: true
places.database.lastMaintenance: 1487143253
places.history.expiration.transient_current_max_pages: 104858
plugin.importedState: true
plugin.state.npauthz: 0
plugin.state.npdeployjava: 0
plugin.state.npfoxitphantompdfplugin: 0
plugin.state.npintelwebapiipt: 0
plugin.state.npintelwebapiupdater: 0
plugin.state.npspwrap: 0
plugin.state.npvlc: 0
print.printer_Foxit_PhantomPDF_Printer.print_bgcolor: false
print.printer_Foxit_PhantomPDF_Printer.print_bgimages: false
print.printer_Foxit_PhantomPDF_Printer.print_colorspace:
print.printer_Foxit_PhantomPDF_Printer.print_command:
print.printer_Foxit_PhantomPDF_Printer.print_downloadfonts: false
print.printer_Foxit_PhantomPDF_Printer.print_duplex: 3932222
print.printer_Foxit_PhantomPDF_Printer.print_edge_bottom: 0
print.printer_Foxit_PhantomPDF_Printer.print_edge_left: 0
print.printer_Foxit_PhantomPDF_Printer.print_edge_right: 0
print.printer_Foxit_PhantomPDF_Printer.print_edge_top: 0
print.printer_Foxit_PhantomPDF_Printer.print_evenpages: true
print.printer_Foxit_PhantomPDF_Printer.print_footercenter:
print.printer_Foxit_PhantomPDF_Printer.print_footerleft: &PT
print.printer_Foxit_PhantomPDF_Printer.print_footerright: &D
print.printer_Foxit_PhantomPDF_Printer.print_headercenter:
print.printer_Foxit_PhantomPDF_Printer.print_headerleft: &T
print.printer_Foxit_PhantomPDF_Printer.print_headerright: &U
print.printer_Foxit_PhantomPDF_Printer.print_in_color: true
print.printer_Foxit_PhantomPDF_Printer.print_margin_bottom: 0.5
print.printer_Foxit_PhantomPDF_Printer.print_margin_left: 0.5
print.printer_Foxit_PhantomPDF_Printer.print_margin_right: 0.5
print.printer_Foxit_PhantomPDF_Printer.print_margin_top: 0.5
print.printer_Foxit_PhantomPDF_Printer.print_oddpages: true
print.printer_Foxit_PhantomPDF_Printer.print_orientation: 0
print.printer_Foxit_PhantomPDF_Printer.print_page_delay: 50
print.printer_Foxit_PhantomPDF_Printer.print_paper_data: 9
print.printer_Foxit_PhantomPDF_Printer.print_paper_height: 11.00
print.printer_Foxit_PhantomPDF_Printer.print_paper_name:
print.printer_Foxit_PhantomPDF_Printer.print_paper_size_type: 0
print.printer_Foxit_PhantomPDF_Printer.print_paper_size_unit: 1
print.printer_Foxit_PhantomPDF_Printer.print_paper_width: 8.50
print.printer_Foxit_PhantomPDF_Printer.print_plex_name:
print.printer_Foxit_PhantomPDF_Printer.print_resolution: 2228274
print.printer_Foxit_PhantomPDF_Printer.print_resolution_name:
print.printer_Foxit_PhantomPDF_Printer.print_reversed: false
print.printer_Foxit_PhantomPDF_Printer.print_scaling: 1.00
print.printer_Foxit_PhantomPDF_Printer.print_shrink_to_fit: true
print.printer_Foxit_PhantomPDF_Printer.print_to_file: false
print.printer_Foxit_PhantomPDF_Printer.print_unwriteable_margin_bottom: 0
print.printer_Foxit_PhantomPDF_Printer.print_unwriteable_margin_left: 0
print.printer_Foxit_PhantomPDF_Printer.print_unwriteable_margin_right: 0
print.printer_Foxit_PhantomPDF_Printer.print_unwriteable_margin_top: 0
security.disable_button.openCertManager: false
security.disable_button.openDeviceManager: false

Graphics

Adapter Description: Intel(R) HD Graphics 4000
Vendor ID: 0x8086
Device ID: 0x0162
Adapter RAM: Unknown
Adapter Drivers: igdumd64 igd10umd64 igd10umd64 igdumd32 igd10umd32 igd10umd32
Driver Version: 9.17.10.2867
Driver Date: 9-26-2012
Direct2D Enabled: false
DirectWrite Enabled: false (6.2.9200.17568)
ClearType Parameters: Gamma: 2200 Pixel Structure: R ClearType Level: 100 Enhanced Contrast: 50
WebGL Renderer: false
GPU Accelerated Windows: 0

AzureCanvasBackend: skia
AzureSkiaAccelerated: 0
AzureFallbackCanvasBackend: cairo
AzureContentBackend: cairo

JavaScript

Incremental GC: 1

Accessibility

Activated: 0
Prevent Accessibility: 0

Library Versions

Expected minimum version
Version in use

NSPR
4.10.10
4.10.10

NSS
3.19.5.0 Basic ECC
3.19.5.0 Basic ECC

NSS Util
3.19.5.0
3.19.5.0

NSS SSL
3.19.5.0 Basic ECC
3.19.5.0 Basic ECC

NSS S/MIME
3.19.5.0 Basic ECC
3.19.5.0 Basic ECC

[Moonchild]

You may want to start by not using a 5 year old video driver
Older Intel drivers are known to be pretty bad in their x64 form. So if you use an x64 application on them, they may crash.

[pollo]

Is that the reply for this problem?

Because the latest Thunderbird works well.

[Moonchild]

If you're not willing to go through the steps of first eliminating the most likely causes, then by all means, stop and use Thunderbird instead.

[half-moon]

FossaMail x64 runs fine on my computer.