Closed Bug 34310 Opened 25 years ago Closed 25 years ago

assert: !"I/O method is invalid" at priometh.c:65

Categories

(Core :: Networking, defect, P3)

PowerPC
Mac System 8.5
defect

Tracking

()

VERIFIED WORKSFORME

People

(Reporter: Brade, Assigned: gordon)

References

()

Details

(Whiteboard: [NEED INFO]1d ?)

Running a build from this morning, I get the following assert: !"I/O method is invalid" at priometh.c:65 The stack crawl (partial) looks like this: PR_Read nsSocketTransport::IsAlive(unsigned in, int*)+00090 nsHTTPHandler::RequestTransport(nsIRUI* nsHTTPChannel*, unsigned int, unsigned int, nsIChannel**, unsigned int)+00440 nsHTTPPipelinedRequest::WriteRequest()+00154 nsHTTPChannel::Open()+00B24 nsHTTPHandler::ReleaseTransport(nsIChannel*, unsigned int)+003FC nsHTTPServerListener::OnStopRequest(nsIChannel*, nsISupports*, unsigned int, const unsigned short*)+003A8 ...
Is it happening all the time? The stack looked as it normally should.
Assignee: ruslan → warren
warren, gordon - you've MACs. Can you take a look real quick? IsAlive method was there for a while and I didn't touch it recently. Can you set a breakpoint in IsAlive (in PR_Read) and see if fd looks ok?
I wrote up this bug report when it first happened so I'd be able to provide the stack information. Unfortunately I haven't been able to reproduce this on a second attempt.
I just finished my brand-new build and I can't even load www.cnn.com - there's something very wrong with layout and pages keeps on reloading all the time (on NT). It wasn't the case on Friday. I think we're looking into some unrelated bustage somewhere.
=> gordon
Assignee: warren → gordon
Target Milestone: --- → M16
Moving to M17 which is now considered part of beta2.
Target Milestone: M16 → M17
Keywords: beta2
Whiteboard: 1d ?
Keywords: nsbeta2
Can PDT get a retest on this please? Need to know results with latest build. Thanks!
Whiteboard: 1d ? → [NEED INFO]1d ?
Kathy, have you seen this since it was reported. I've never seen this assert in any of my builds.
no, I haven't seen this bug since I filed it
Okay, I'm going to mark this one WORKSFORME. If we see it again, we'll take care of it then.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → WORKSFORME
Marking Verified.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.