Visual studio 2010 program doesn't work on windows 7 64 bit...but works fine on xp.
-
Friday, May 11, 2012 7:22 PM
Hi,
I have one tool which we developed on visual studio 2010. there are basically two parts of my project, one is UI part which i wrote in VB and algorithm part which is in C++ on back end. When we compile C++ part it creates a .dll which is used by my front end VB program.
Now my problem is little weird since i am compiling and deploying this tool on windows xp machine but some of the users are using windows 7 64 bit machines and after running the program for about 5-10 minutes, it crashes on windows 7 with following error
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.************** 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.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: 2.0.50727.5448 (Win7SP1GDR.050727-5400)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/ mscorlib.dll
----------------------------------------
IAT
Assembly Version: 0.9.1.67
Win32 Version: 0.9.1.67
CodeBase: file:///C:/Users/e50410/AppData/Local/Apps/2.0/ 1R14Z8CG.4XD/XP8YL8NJ.RXZ/iat. ..tion_0000000000000000_0000. 0009_0f28d7f9c15b672d/IAT.exe
----------------------------------------
Microsoft.VisualBasic
Assembly Version: 8.0.0.0
Win32 Version: 8.0.50727.5420 (Win7SP1.050727-5400)
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: 2.0.50727.5453 (Win7SP1GDR.050727-5400)
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: 2.0.50727.5446 (Win7SP1GDR.050727-5400)
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: 2.0.50727.5458 (Win7SP1GDR.050727-5400)
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: 2.0.50727.5420 (Win7SP1.050727-5400)
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: 2.0.50727.5420 (Win7SP1.050727-5400)
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: 2.0.50727.5420 (Win7SP1.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__ b77a5c561934e089/System.Xml. dll
----------------------------------------
Microsoft.VisualBasic.Compatibility
Assembly Version: 8.0.0.0
Win32 Version: 8.0.50727.5420
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft. VisualBasic.Compatibility/8.0. 0.0__b03f5f7f11d50a3a/ Microsoft.VisualBasic. Compatibility.dll
----------------------------------------
Axmscomctl
Assembly Version: 10.0.4504.0
Win32 Version: 10.0.4504.0
CodeBase: file:///C:/Users/e50410/AppData/Local/Apps/2.0/ 1R14Z8CG.4XD/XP8YL8NJ.RXZ/iat. ..tion_0000000000000000_0000. 0009_0f28d7f9c15b672d/ Axmscomctl.DLL
----------------------------------------
mscomctl
Assembly Version: 10.0.4504.0
Win32 Version: 10.0.4504
CodeBase: file:///C:/Windows/assembly/GAC/mscomctl/10.0.4504.0__ 31bf3856ad364e35/mscomctl.dll
----------------------------------------
Microsoft.VisualBasic.PowerPacks.Vs
Assembly Version: 10.0.0.0
Win32 Version: 10.0.30319.1
CodeBase: file:///C:/Users/e50410/AppData/Local/Apps/2.0/ 1R14Z8CG.4XD/XP8YL8NJ.RXZ/iat. ..tion_0000000000000000_0000. 0009_0f28d7f9c15b672d/ Microsoft.VisualBasic. PowerPacks.Vs.DLL
----------------------------------------
bzbey0lg
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5453 (Win7SP1GDR.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__ b77a5c561934e089/System.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.i am completely clue less for this error since this program works fine on xp but doesn't work on windows 7. can anyone give me an idea how to resolve this problem? it am struggling to resolve this since two weeks but not having any luck.
Thanks in advance for the help....
gops
- Changed Type Jack Zhai - MSFTMicrosoft Contingent Staff, Moderator Monday, May 21, 2012 2:11 AM Not a VS debugger issue.
All Replies
-
Monday, May 14, 2012 10:22 AMModerator
Hi gops,
Thank you for posting in the MSDN forum.
Just-In-Time debugging launches Visual Studio automatically when an exception or crash occurs in an application running outside Visual Studio. This enables you to test your application when Visual Studio is not running and begin debugging with Visual Studio when a problem occurs.
Based on your description, it works well on the XP, but it doesn’t work on window 7, I’m afraid that it is related to your window like this thread:
If possible, I suggest you post this issue http://answers.microsoft.com/en-us/windows/forum/windows_7 for better support. Thanks for your understanding.
Best Regards,
Jack Zhai [MSFT]
MSDN Community Support | Feedback to us
-
Monday, May 14, 2012 9:37 PM
Hello Jack,
Thank you for replying my post question but it seems like it's a visual studio problem not windows 7. actually today i did a small test on windows 7 pc, i tried to call my dll file from the commad prompt instead of UI side. on that way i didn't see that error happening any time, i can see that my task get complete at the end without any errors. So there is something from the UI side which is written in VB.
Also i am getting the error on the screen that do not have enough memory to run this. I still think something needs to be change in visual studio 2010.
can you please try to take a look further? Really appreciate your help.
-
Tuesday, May 15, 2012 5:28 AMModerator
Hi gops,
Glad to receive your reply.
There is something from the UI side which is written in VB.
Do you mean that it generated this issue when you run the VB app, if so, we could make sure that it is related to this specific VB app, if possible, you could post this issue in the development forum Visual Basic General for better support.
Not enough storage is available to process this command
Based on this article. And do one of the following: (1) reduce the number of running programs; (2) remove unwanted files from the disk the paging file is on and restart the system; (3) check the paging file disk for an I/O error; or (4) install additional memory in your system.
Best Regards,
Jack Zhai [MSFT]
MSDN Community Support | Feedback to us
-
Tuesday, May 15, 2012 6:55 PM
Hi Jack,
Thank you for your suggestion to put this to the VB support form. i will definitely put that over there. but the error which i am getting is nothing to relate the memory on windows 7 pc since i have approx 200 GB of free space in my hard drive and have 4 GB of RAM so i think it should be ok with the memory. i still believe that i am missing any microsoft dll to my build which is compatible for window7 even though i am building it on windows xp.
gops
-
Wednesday, May 16, 2012 5:30 AMModerator
HI gops,
Glad to receive your reply.
Maybe you could try to create a new similar app in the window 7 64bit and check it. In addition, you could try to change the Plarform target “Any CPU”, and then clean and rebuild your app to check it.
Thank you for your suggestion to put this to the VB support form. i will definitely put that over there.
If still no help, I’m afraid that I didn’t have the good idea. Since this issue is not the VS debugger tool issue, and you also post this issue in the VB development forum. I will change this issue to “General Discussion”. Maybe other community members could help. Thanks for your understanding.
Have a nice day,
Jack Zhai [MSFT]
MSDN Community Support | Feedback to us
-
Wednesday, November 28, 2012 11:23 PM
Hi Jack,
Sorry to re-initiated this post after long time but i was stuck with some other work for quiate a few months..
So since last few days i started looking at this issue one more time. when i was debugging, i found out that in VB, it enters into the DrawImage Function and then it's stop working from there.
So let me be more specific about my problem. I loading around 20 images which are usually 8MP large, so i am loading this large images by this function to rescale it to 640x480 so that it can fit on my app window. so it runs good for 12 images or sometimes few more than that but after that it crashes with the above error. Is this something to do with the nested images which i am loading? for your info i am copying little bit of my code.
tempBitmap = New Bitmap(640, 480, System.Drawing.Imaging.PixelFormat.Format24bppRgb)
tempBitmap.SetResolution(myfrmMain.myfrm4_Image.imgWidth, myfrmMain.myfrm4_Image.imgHeight)
bmGraphics = Graphics.FromImage(tempBitmap)
bmGraphics.InterpolationMode = InterpolationMode.HighQualityBicubic
bmGraphics.DrawImage(myfrmMain.myfrm4_Image.Picture1.Image, New Rectangle(0, 0, 640, 480), New Rectangle(0, 0, myfrmMain.myfrm4_Image.imgWidth, myfrmMain.myfrm4_Image.imgHeight), GraphicsUnit.Pixel)
myfrmMain.myfrm3_IATOptions.txtWidth.Text = myfrmMain.myfrm4_Image.imgWidth
myfrmMain.myfrm3_IATOptions.txtHeight.Text = myfrmMain.myfrm4_Image.imgHeight
myfrmMain.myfrm4_Image.Picture1.Image = tempBitmap
bmGraphics.Dispose()Do you think anything obviously wrong with this?
Any help will be highly appreciated...
Thanks
gops

