DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=11476>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=11476 File System Error Summary: File System Error Product: Apache httpd-2.0 Version: 2.0.39 Platform: PC OS/Version: Other Status: NEW Severity: Major Priority: Other Component: Build AssignedTo: bugs@httpd.apache.org ReportedBy: [EMAIL PROTECTED] This bug occurs randomly over time running Apache 2.039 and previous versions, but I have recently determined how to invoke the bug. System is XP Professional. The bug causes the blue screen of death, requiring a power down to restart the sytem and gives the following error message: PROCESS_HAS_LOCKED_PAGES Technical Information: *** STOP: 0x00000076 (0x00000000,0x819EBB30, 0x00000001, 0x00000000) To cause Apache to fail in this manner, one has merely to use Frontpage 2002 to publish a simple website to the machine running Apache (one that does not require any of the extensions to operate, just a few linked pages). Shortly after publishing Apache will stop serving. If you then use the applet to restart Apache, it will restart and begin serving correctly. After working for a minute or so, the system will crash with the above error message. As I mentioned this failure will appear over time on it's own. About the configuration here: My websites are all simple. I have one IP and multiple virtual sites on the machine. The configuration for Apache is almost as distributed with the exception of the mods required to activate the virtual sites. The XP Pro system runs only MDaemon and Apache and Zone Alarm Pro. Without Apache, the system runs continuously with no problems for extended periods of time (usually until I shut it down) and is power conditioned by APC UPS. The configuration of XP is minimal. All features not being used (most of them) have been removed. Again, Frontpage isn't the problem, the problem happens over time by itself, but I can make it happen quickly with frontpage. If you have trouble duplicating the problem please let me know. This problem is documented for Windows 2000 in Microsoft's database, but not for XP. In the W2000 article they attribute this failure to an I/O driver or sofware that fails to clean up after itself and eventually overloads the OS. They have procedures to figure out which one it is using registry edits, but this is not workable in XP due to different flags and naming conventions. On the sytem that I can repeatedly create the problem, all updates are current. The system is a 800 Mhz Compaq with 512 Mb of memory. /Len PS I will be happy to test any code you generate to fix the problem, but I will need a compiled package. I do not use C here. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
