https://bugs.winehq.org/show_bug.cgi?id=56223
--- Comment #5 from Bernhard Übelacker bernhardu@mailbox.org --- Created attachment 75931 --> https://bugs.winehq.org/attachment.cgi?id=75931 stdout of application and winedbg with MR4890
Maybe it does not need to be loaded at all. Or not in full.
With MR4890 stdout and the backtrace looks like attached.
Without the pdb in place it does show all 5 frames in xul.dll without further information.
With pdb and MR4890 it shows the first 3 frames with line information, and only the frames 3 to 6 without.
I assume if the address space exhaustion would not happen it would be able to show also debug information for the other frames.