https://bugs.winehq.org/show_bug.cgi?id=52619
--- Comment #20 from Eric Pouech eric.pouech@gmail.com --- it looks like the launcher (neoplelauncher.exe) is a 32bit app
this explains why gecko 32bit is used
when an exception occurs, as the faulting process is a 32bit one, winedbg (wine's internal debugger) is also started in 32bit mode
unfortunately 32bit winedbg fails on out of memory conditions when loading the gecko PDB files
this can be worked around by starting the 64bit version of winedbg and running inside it the 32bit launcher
wine drive_c\windows\system32\winedbg.exe <pathto>/neoplelauncher.exe
this should allow to get a proper backtrace of the exception
the OOM when loading 32Bit gecko files should be reported in a different bug report
notes: - tried locally using iexplore.exe instead of neoplelauncher.exe - this fails with 32bit winedbg - but succeeds with 64bit winedbg (in both cases using gecko 32bit and theirs relevant pdb files)