Re: re:IWMReader and HTTP Stream: Memory Leak?

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

"jmoney" <jmorrill@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:XK2dncMqwJcsEDrfRVn_vg@xxxxxxxxxxxxxxx
> I also noticed on it sends me two WMT_CONNECTING status on the
> OnStatus() callback and right before the second WMT_CONNECTING I get
> about 15 trace messages that say:
>
> First-chance exception at 0x086c7db6 in WindowsMedia.SDK.exe:
> 0xC0000005: Access violation writing location 0x00000000.
>

That's the way things are. Early versions of wmvcore.dll didn't suffer from
that things, but the latest one does. Although nobody likes these messages,
things works. (Not all things, but it is usable. MS will not fix some things
and there is nothing you can do about it).

--
It is practically impossible to teach good programming to students that have
had a prior exposure to BASIC: as potential programmers they are mentally
mutilated beyond hope of regeneration. (Edsger Dijkstra 1930-2002)


.

Relevant Pages

  • re:IWMReader and HTTP Stream: Memory Leak?
    ... OnStatus() callback and right before the second WMT_CONNECTING I get ... about 15 trace messages that say: ... Prev by Date: ...
    (microsoft.public.windowsmedia.sdk)
  • Re: timeSetEvent() wraps after inteval of 429496
    ... setting a period of 430000 which generate a callback in 504ms. ... > The actual exports for these time functions are in winmm.dll, and this bug ... You can always use IReferenceClock. ... had a prior exposure to BASIC: as potential programmers they are mentally ...
    (microsoft.public.win32.programmer.mmedia)