Re: Crash on unloading a vfw dll

The pop-up window that reports the crash reads like this:
"The instruction at "0x014f9790" references memory at "0x01524028". The
memory could not be "read".

There doesn't seem to be any problem with the codec when playing back
files, but it's become clear to me that playback and transcoding are
two very different creatures. Is there any way to prevent errors like
this from unloading vfw dlls in general?


One way to prevent similar issues and leaky pointers is to use smart
COM pointers. Look at http://tmhare.mvps.org/faqs.htm#com

Also, are your pointers global variables? Are you possibly manually
releasing objects before they should be?

.

Relevant Pages

  • Re: Crash on unloading a vfw dll
    ... There doesn't seem to be any problem with the codec when playing back ... One way to prevent similar issues and leaky pointers is to use smart ... (It uses the divx codec to decompress the source AVI stream, ...
    (microsoft.public.win32.programmer.directx.video)
  • Re: Recuerdos de la Alhambra - my take
    ... take lessons with a classical teacher (was learning on a classical ... Usually he has superb pointers that result in better phrasing and ... is in constant alternate picking motion. ... much easier to build speed with pick playing than with the ...
    (rec.music.classical.guitar)
  • Re: Why does the "".join(r) do this?
    ... > Is there a way to change the default codec in a part of a program? ... > (Meaning that different parts of program deal with strings they know are ... of pointers to functions that return pointers to ... > functions that return void. ...
    (comp.lang.python)
  • Re: Another promotional idea
    ... > but I have no interest in playing someone who is inferior in a 3 pt. ... pts. ... In the time it takes you to play a 9 point match (which you lose once in ... pointers against fish, than you are playing 9 pointers against good ...
    (rec.games.backgammon)
  • Re: 6.1 libpthread: pthread_create and _pq_insert_tail: Already in priority queue
    ... fails in its runtime system with: ... two pointers: ... I got this error when I was playing with threads/mutexes and my code was ...
    (freebsd-hackers)