Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Joe, you have a <a href="http://en.wikipedia.org/wiki/Memory_leak" rel="nofollow noreferrer">memory leak</a>. </p> <p>You're probably trying to use some memory that has been deleted.</p> <p>See <a href="http://www.codersource.net/c++_memory_leaks.aspx" rel="nofollow noreferrer">this article</a> for common causes of memory leaks, and how to identify them, otherwise, search for "C++ memory profiler" + your compiler/platform, it'll give links to Memory profilers suitable for your compiler and platform, these will help track down the memory leak by watching how your program uses memory as it runs.</p> <p>Hope this helps.</p> <p><strong>EDIT</strong></p> <p>How to track it down? This is off the top of my head, there may be better advice else where . . .</p> <p>Find where the code crashes, it'll be when accessing the contents of some pointer (or deleting a pointer). The problem is that that pointer has either a) never been assigned b) is already deleted. Go through all references to pointers of that type, are they used in copy ctors/assignment operators? </p> <p>If so, are it's contents being copied or just the pointer? If just the pointer then is the containing class trying to delete the pointer? If so the first class to die will succeed, the second will throw an access violation.</p> <p>If you don't explicitly code copy ctors and operator=, then you should hide them (declare private prototypes but don't implement them), this stops the compiler from generating default implementations for you.</p> <p>When you hide them you'll get compiler errors everywhere they're being used, it might be that you can clean these up, or that you need to implement the copy ctor and operator= for each class.</p> <p>I'm on vacation from tomorrow or two weeks, email me direct today (follow the link on my SO user page) if you've any questions on this.</p>
    singulars
    1. This table or related slice is empty.
    1. POAccessViolationException in Release mode (C++)
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USBinary Worrier
    1. USBinary Worrier
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POAccessViolationException in Release mode (C++)
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThanks. I think you're right. We've had lots of problems with leaks (I guess it's par for the course). We're using the MS memory leak tools: _CrtSetReportMode( _CRT_WARN, _CRTDBG_MODE_FILE); _CrtSetReportFile( _CRT_WARN, _CRTDBG_FILE_STDERR); _CrtSetBreakAlloc( 665); _CrtMemState state; _CrtMemCheckpoint( & state); Any thoughts on how to track this down?
      singulars
      1. PO
      1. USJoe
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload