Closed Bug 32002 Opened 26 years ago Closed 26 years ago

PR_Poll assertion breaks table regression tests

Categories

(Core :: Networking, defect, P3)

x86
Windows NT
defect

Tracking

()

VERIFIED FIXED

People

(Reporter: karnaze, Assigned: ruslan)

References

()

Details

On a 5:30 am build, when loading file:///s|/mozilla/layout/html/tests/table/core/misc.html in Viewer, I get the following stack and can not recover. This is a recent regression and does not occur on a build of last night around 6pm. NTDLL! DbgBreakPoint@0 address 0x77f76148 PR_Assert(const char * 0x0033b824 ??_C@_0BJ@LHIK@?$CB?$CCI?1O?5method?5is?5invalid?$CC?$AA@, const char * 0x0033b840 ??_C@_0L@KLDB@priometh?4c?$AA@, int 72) line 448 _PR_InvalidInt16() line 72 + 35 bytes _PR_MD_PR_POLL(PRPollDesc * 0x0118ee60, int 2, unsigned int 2610055) line 131 + 42 bytes PR_Poll(PRPollDesc * 0x0118ee60, int 2, unsigned int 2610055) line 115 + 17 bytes nsSocketTransportService::Run(nsSocketTransportService * const 0x01189154) line 414 + 24 bytes nsThread::Main(void * 0x0118a680) line 83 + 26 bytes _PR_NativeRunThread(void * 0x0118f3b0) line 399 + 13 bytes _threadstartex(void * 0x0118b700) line 212 + 13 bytes
*** Bug 32005 has been marked as a duplicate of this bug. ***
I'm pulling a fresh tree now and will take a look. Does this test use socketTransport at all?
It works for me (NT 4.0SP6). What platform is it crashing on?
It was WinNT. I'll repull again sometime today.
I still can't reproduce it nomatter what I do.
I saw this yesterday, repulled this morning and it's still here! Mozilla does run if I give an argument to load a file url but immediately when I try accessing the net I get this assert and then mozilla exits... (WinNT 4SP3)
I just rolled back some of my keep-alive changes from earlier this week. Could anyone try and see if the crash still occurs because I couldn't reproduce it at all.
Yeeess! That did it (for me at least), I updated netwer/base/src and rebuilt netwerk and mozilla runs and I'm able to acces the net wothout any problem! Thank you ruslan :)
Hey, this cured the problem on my WinNT build, also.
I also applied the recent changes to netwerk/base to the build that was failing me, and it now works. I didn't think to mention in the description that I was using my home machine.
Closing this for now then
Status: NEW → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
verified
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.