[jumper]

I've been rebuilding a test machine the last few days and now have Firefox 3.5.19 installed and SeaMonkey Setup 2.6.1 ready to go next.

I'm not getting a hang when printing with FF3.5, but rather a crash. Sometimes the error message is from the Mozilla Crash Reporter:

Firefox had a problem and crashed.
...
Details: The application did not leave a crash dump file.

and sometimes a standard system error dialog:

FIREFOX caused an invalid page fault
in module Kernel32.dll at 016f:bff7a388.
...

and sometimes both!

The source code is "only" 46466 KB, so I'll see if it might be helpful:

Index of ftp://ftp.mozilla.org/pub/mozilla.org/firefox/releases/3.5.19/source
Up to higher level directory
File: firefox-3.5.19.bundle 	 	 105198 KB 4/20/11 12:00:00 AM
File: firefox-3.5.19.bundle.asc 	      1 KB 4/20/11 12:00:00 AM
File: firefox-3.5.19.source.tar.bz2 	  46466 KB 4/20/11 12:00:00 AM
File: firefox-3.5.19.source.tar.bz2.asc        1 KB 4/20/11 12:00:00 AM 

---

Edit: While waiting for the download, I found the Mozilla Cross-Reference site.

This search in the FF3.5 source for "PrintDlg" indicates that FF3.5 is supposed to be using PrintDlgExA:

    * line 101 -- // For PrintDlgEx
    * line 104 -- #define GetPrintDlgExQuoted "PrintDlgExA"
...
    * line 188 -- return GetProcAddress(lib, GetPrintDlgExQuoted);
...
    * line 967 -- BOOL result = ::PrintDlgW(&prntdlg);
...
    * line 1301 -- HRESULT result = ::PrintDlgEx(&prntdlg); 

This post has been edited by jumper: 24 September 2012 - 09:01 PM

[jds]

jumper, on 24 September 2012 - 08:27 PM, said:

I've been rebuilding a test machine the last few days and now have Firefox 3.5.19 installed and SeaMonkey Setup 2.6.1 ready to go next.

I'm not getting a hang when printing with FF3.5, but rather a crash.

The cavalry to the rescue! Fantastic!

Perhaps the crash you're getting vs. the lock-up I'm getting is due to the differences between 3.5.19 and 3.5.20pre. I don't know what the differences are, but the respective packages are 7.9M and 11.1M in size, so that suggests lots of changes/additions. However, I'm sure the root problem will be the same.

Quote

While waiting for the download, I found the Mozilla Cross-Reference site.

This search in the FF3.5 source for "PrintDlg" indicates that FF3.5 is supposed to be using PrintDlgExA:

    * line 101 -- // For PrintDlgEx
    * line 104 -- #define GetPrintDlgExQuoted "PrintDlgExA"
...
    * line 188 -- return GetProcAddress(lib, GetPrintDlgExQuoted);
...
    * line 967 -- BOOL result = ::PrintDlgW(&prntdlg);
...
    * line 1301 -- HRESULT result = ::PrintDlgEx(&prntdlg); 

Aren't "PrintDlgW" and "PrintDlgEx" also being used, according to the above?

Joe.

[jds]

Some little progress ...

I tried printing in FF 3.5.20pre by loading it via Dependency Walker and clicking the "Start Profiling" function. When there were pauses in this process, I copied the information from the DW log and saved this away. To my surprise, the first time I tried this, it actually printed. It was the google page, and printed a bit strange - the google graphic and the two button texts were printed up-side-down. This was "Run 1" in the attached logs.

I then tried the same thing a few more times, including reboots, but FF always crashed. Two runs were captured, these are "Run 2" and "Run 3" in the attached logs.

I noticed for example that when function "IsTNT" is called in one instance, there was one (probably bogus) error code, whereas in another instance, there was a different (probably bogus) error code. From this I conclude that the error codes returned for missing functions in general are garbage, which may explain why I succeeded in printing once but not again.

The attached logs are in RTF format to preserve the colour coding and bold text from DW.

Joe.

 Debug_FF3_Printing.cab (14.72K)
Number of downloads: 5