Out of Memory Exception

[DBusalacchi]

Running Windows 7 32 bit with 4G Physical Ram and 16G Swap File. Scanning 1T Drive, after scan is complete during selecting using Select by Location.

Error in Select by Master Folder: Exception of type 'System.OutofMemoryException' wsa thrown.

Export list, reboot computer, re-import list, then Select by Location produces same error.

[DigitalVolcano]

Sorry about this! Is there any chance you could email your export file to us to try and reproduce the error?
software AT digitalvolcano.co.uk

thanks

[drew]

Getting the same error

zzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz


************** Exception Text **************
System.ComponentModel.Win32Exception: Not enough storage is available to process this command
at System.Drawing.BufferedGraphicsContext.CreateCompatibleDIB(IntPtr hdc, IntPtr hpal, Int32 ulWidth, Int32 ulHeight, IntPtr& ppvBits)
at System.Drawing.BufferedGraphicsContext.CreateBuffer(IntPtr src, Int32 offsetX, Int32 offsetY, Int32 width, Int32 height)
at System.Drawing.BufferedGraphicsContext.AllocBuffer(Graphics targetGraphics, IntPtr targetDC, Rectangle targetRectangle)
at System.Drawing.BufferedGraphicsContext.AllocBufferInTempManager(Graphics targetGraphics, IntPtr targetDC, Rectangle targetRectangle)
at System.Drawing.BufferedGraphicsContext.Allocate(IntPtr targetDC, Rectangle targetRectangle)
at System.Windows.Forms.Control.WmPaint(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.ContainerControl.WndProc(Message& m)
at System.Windows.Forms.Form.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

zzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz

Win7 pro system - 32GB of DR3-2400 (PC3 19200) + 1 TB SSD RAID array - memory is not likely the issue

This may be the solution

http://nomagichere.blogspot.com/2008/03 ... on-is.html

[DigitalVolcano]

Thanks for the report and link, Drew. Was this exception during a 'Select' operation (as per the original poster) or during a scan? If so, which type of scan was it?

cheers.

[drew]

during deletion - no change over 3.05 and earlier

[drew]

part b (only three attachments allowed in settings)

may want to change - people don't usually flood support forums

[drew]

scan completes okay in my case

dc-49-3.06.jpg shows hang after selection / before deletion
ignoring warning works except when program stops responding





The other solution involved editing the IRPStackSize Registry Entry - http://social.technet.microsoft.com/For ... fcfe9243e8

Which did not help in my case

[drew]

It is a reproducible error, in my case if the search is > 3Gb or so.

Text from exception
zzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz

************** Exception Text **************
System.OutOfMemoryException: Exception of type 'System.OutOfMemoryException' was thrown.
at System.Windows.Forms.Control.WmPrintClient(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version:
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
DuplicateCleaner
Assembly Version: 3.0.0.6
Win32 Version: 3.0.0.6
CodeBase: file:///C:/Program%20Files%20(x86)/Duplicate%20Cleaner%20Pro/DuplicateCleaner.exe
----------------------------------------
Microsoft.VisualBasic
Assembly Version: 8.0.0.0
Win32 Version:
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version:
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version:
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version:
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Runtime.Remoting
Assembly Version: 2.0.0.0
Win32 Version:
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Runtime.Remoting/2.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll
----------------------------------------
System.Configuration
Assembly Version: 2.0.0.0
Win32 Version:
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Xml
Assembly Version: 2.0.0.0
Win32 Version:
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
QlmLicenseLib
Assembly Version: 5.2.0.18
Win32 Version: 5.2.0.18
CodeBase: file:///C:/Program%20Files%20(x86)/Duplicate%20Cleaner%20Pro/QlmLicenseLib.DLL
----------------------------------------
2akjbh8-
Assembly Version: 2.0.0.0
Win32 Version:
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
Ionic.Zip.Reduced
Assembly Version: 1.9.1.8
Win32 Version: 1.9.1.8
CodeBase: file:///C:/Program%20Files%20(x86)/Duplicate%20Cleaner%20Pro/Ionic.Zip.Reduced.DLL
----------------------------------------
Accessibility
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Accessibility/2.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

zzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz

Also, after folders have been removed they still show up in Scan Location

Any chance of recompiling as 64 bit?

[therube]

Heh, IRPStackSize, that rang a bell.

Not enough server storage to process command - Revisit

If it is common enough, you would think MS would have made an update to account for this by now.

Not to worry, Win 8 is around the corner & you can be sure things like this will no longer be an issue .

Any chance of recompiling as 64 bit?

Wonder if that would make any difference?
x64 is far from an end-all, IMO.

It just occurs quicker on x64 as the kernel stack is the same as x86 but I would assume this is because the pointer size is larger.

Technet: Pushing the Limits of Windows: Processes and Threads

IRPStackSize ... Which did not help in my case

So if not that specifically, then I'd guess the same class of error. Some resource, be it IRPStackSize/Lanman, GDI, memory, or whatever that is being depleted until applications no longer work correctly.


Troubleshooting Exceptions: System.OutOfMemoryException - Visual Studio 2005

[drew]

As expected, when run on 64-bit Windows with 256MB of RAM, Testlimit is only able to create 6,600 threads – roughly half what it created on 32-bit Windows with 256MB RAM - before running out of resident available memory.

64 bit programs runs more efficiently on 64 bit OS

Sales feature

Eventually it will have to be done before the end of the decade


Windows 8 - even the boys in Redmond can't get it to work
http://www.youtube.com/watch?v=N1zxDa3t0fg