IMAGE EDITOR UNHANDLED EXCEPTION

[Mark Brinkman]

I saved an impage as nxt image with 6 lighting channels and was able to see it while rendering quite well and control the lights of the lighting channels.

 

Now when I try to open the image using Image Editor, I get the following unbundled exception message. This is the 249 build. Is this a memory problem on this computer?

 

Message below:

 

----------------------------------------------------------------------

 

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
at ArPictureEditor.ImageDisplay.OnPaint(PaintEventArgs e)
at System.Windows.Forms.Control.PaintWithErrorHandling(PaintEventArgs e, Int16 layer, Boolean disposeEventArgs)
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.UserControl.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.3082 (QFE.050727-3000)
CodeBase: file:///C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
nXtImageEditor
Assembly Version: 1.0.4043.39224
Win32 Version: 1.0.249.0
CodeBase: file:///C:/Program%20Files/AccuRender%20nXt/nXtImageEditor.exe
----------------------------------------
msvcm90
Assembly Version: 9.0.30729.4148
Win32 Version: 9.00.30729.4148
CodeBase: file:///C:/WINDOWS/WinSxS/x86_Microsoft.VC90.CRT_1fc8b3b9a1e18e3b_9.0.30729.4148_x-ww_d495ac4e/msvcm90.dll
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3082 (QFE.050727-3000)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.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.

[Roy Hirshkowitz]

So I was able to reproduce this in XP-- looks like it's a simple case of the memory manager being less efficient in XP than in subsequent operating systems.  Using the /3GB switch in the boot.ini file I was able to successfully load this.  This switch allows 32 bit operating systems to devote 3GB of address space to each process instead of the default 2GB.  The ultimate solution for you is clearly a 64 bit OS, but this procedure will probably allow you to keep going for a while (until the images get too large for even this.)

 

The Rhino wiki page for doing this is here.  Follow the XP instructions. Don't worry too much about the warnings-- there are rare situations where this switch causes problems-- you're not likely to encounter these.  Just remove it (you may have to reboot in safe mode) if it does.

[Mark Brinkman]

OK, I'll try that, but it seems a little risky...

 

Curious, though that your instructions are to add this line to the "boot.ini":

 

multi(0)disk(0)rdisk(0)partition(2)\WINDOWS=“Microsoft Windows XP Professional” /fastdetect /NoExecute=OptIn /3GB

 

But when I opened the "boot.ini", it looked as if that instruction was already there:

 

[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /noexecute=optin /fastdetect /usepmtimer

multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional 3GB" /3GB /fastdetect

 

Any custom advise given the details of my "boot.ini" file? I'm not going to try this until the end of the day. Thanks.

[Roy Hirshkowitz]

You've already got two boot choices-- if you select the second one during boot up (with the 3GB in the title) you should boot up "large address aware".

[Mark Brinkman]

Thanks, this worked! Something our IT guy did not explain, but apparently they've had some need for it before...

 

Any thoughts on running a script in the image editor to get different light effects from different channels and animating an image?

[Roy Hirshkowitz]

It's been noted as a feature request.  Like I said, it is intriguing.