Windows error 0x00000282, 642

Detailed Error Information

PORT_NOT_SET[1]

MessageAn attempt to remove a processes DebugPort was made, but a port was not already associated with the process.
Declared inwinerror.h

This appears to be a raw Win32 error. More information may be available in error 0x80070282.

HRESULT analysis[2]

This is probably not the correct interpretation of this error. The Win32 error above is more likely to indicate the actual problem.
FlagsSeveritySuccess

This code indicates success, rather than an error. This may not be the correct interpretation of this code, or possibly the program is handling errors incorrectly.

Reserved (R)false
OriginMicrosoft
NTSTATUSfalse
Reserved (X)false
FacilityCode0 (0x000)
NameFACILITY_NULL[2][1]
DescriptionThe default facility code.[2][1]
Error Code642 (0x0282)

Possible solutions

0

iTunes crashes with "Attempt to allocate 1073741824 bytes for NS/CFData failed" error

macos
itunes

Get rid of SafariAdBlock and any other InputManagers you've thrown on your system. If you need help finding them, run this:

http://khiltd.com/software/consultants_canary

answered on Super User Apr 5, 2010 by Hasaan Chop
0

iTunes crashes with "Attempt to allocate 1073741824 bytes for NS/CFData failed" error

macos
itunes

Are you reading any http net-radio or video streams using iTunes?

The _ZN14HTTPReadStream11streamEventEm function appears in the callstack shortly after __CFRunLoopDoSources0 is called. The latter probably examines the status of known streaming sources and subsequently calls the former upon noticing that there is indeed something worth streaming.

I can only assume that there are invalid data inside the stream which the streaming code doesn't handle properly, leading to an absurd memory allocation instead of ignoring the faulty data.

Try to notice which audio/video sources you are playing from when this bug appears. If you can pinpoint one that systematically causes it, you should then include its URL in your next Apple Crash Report.

Note that this crash implies up to two bugs in iTunes' code:

  • Failure to handle invalid data (this one is only probable).
  • Failure to properly handle Out Of Memory exceptions.

(and I'm pretty naive to reply to a one year old question, but well, you never know :) )

answered on Super User Dec 24, 2010 by Laurent Giroud

Comments

Leave a comment

(plain text only)

Sources

  1. winerror.h from Windows SDK 10.0.14393.0
  2. https://msdn.microsoft.com/en-us/library/cc231198.aspx

User contributions licensed under CC BY-SA 3.0