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]

32 bit OS,  right?  It's very possible you're exceeding the 32 bit address space with a high-res, multi-channel, image. If you want me to try it out, you'll need to send the image here.  Use the upload link.

 

If your computer has not been set up for large address spaces (3GB) we may be able to solve the problem that way. Adding memory will not help this problem.

[Mark Brinkman]

It is 32 bit. I'm not sure about the large address space. I've uploaded the file, thanks.

[Roy Hirshkowitz]

Something else is likely going on here, Mark.  I was able to easily load this image in both the 32 bit and 64 bit versions of the image editor.  It allocated about 1GB of address space which means it should fit comfortably with or without the large address space business.  I have no idea what's going on at the moment-- but this is the second report of crashing in 32 bits (the other was w/ build 254) that could not be reproduced here.  Hopefully a subsequent build will fix this.  I will look into it a little more this coming week-- but without the ability to reproduce the problem my chances of finding something go down dramatically.

[Mark Brinkman]

I tried installing and re-installing nxt and still the same result.

Was wondering if you might have a separate install for the image editor? In the start menu when I select the nxt program group and find the image editor in the list, the program icon is a blank square. Is this the way it's supposed to look?

( I tried attaching a screen shot, but the image function on this message board is not working for me)

 

 



[Roy Hirshkowitz]

No-- no separate install for the image editor.  Have you tried 254?

[Mark Brinkman]

Just downloaded and installed build 254, and got same result with image editor. :(

[Mark Brinkman]

Still not sure if my image editor application installed properly. In the directory this is listed as a 318 KB application. Is this correct?

The problem, at least for me, seems to be the standalone application. While the image was rendering within Autocad I was able to take full advantage of the lighting channels, and see real-time results. Can you run the image editor within Autocad and load the previously rendered nxt image? (Similar to AR 3.1 that would produce .rad radiosity files?) Just a thought...

[Roy Hirshkowitz]

Like I said, I've got one other report of crashing in the 32 bit Image Editor.  Not reproducible yet so I'm still operating blindly.

 

Installation should not be a problem-- particularly if you always install to the same folder.  You can check the version in the Image Editor About Box if you're unsure.

[Mark Brinkman]

Roy-

This seems to be a problem with running the program on Windows xp. I tried 3 different computers, all with varying hardware configurations, mostly within the last 5 years, but all running windows xp. Every one of them produced the same unhadled exception error.

Then I decided to try it on a 3 year old laptop running Vista Home Edition, and lo and behold it worked!

Hope this helps you determine the cause, I'd like to run it on our office computers that run xp.

[Roy Hirshkowitz]

Thanks-- I'll check it out.

[Mark Brinkman]

Any update on this? Were you able to reproduce the error? I still cannot use the image editor in our office. I can reproduce the error on every computer I try here. Any help? Thanks.

[Roy Hirshkowitz]

Haven't gotten to it yet.