OMUDCClassLinker.cpp#68

When LabVIEW 8.6 launches it says I have some vi's not linked to any library. It asks if I want them linked to the class they should belong to.
When I do I get a crash and the error log below.
#Date: Tue, Feb 24, 2009 7:38:57 AM
#OSName: Windows NT
#OSVers: 5.1
#AppName: LabVIEW
#Version: 8.6
#AppKind: FDS
#AppModDate: 06/26/2008 01:25 GMT
c:\builds\penguin\labview\branches\Saturn\dev\source\objmgr\OMUDClassLinker.cpp(3196) : DAbort: Should never have already existing class when patching the thing that is loading the class!
$Id: //labview/branches/Saturn/dev/source/objmgr/OMUDClassLinker.cpp#68 $
0x00E98AAA - LabVIEW <unknown> + 0
0x00E99AA3 - LabVIEW <unknown> + 0
0x00D3D553 - LabVIEW <unknown> + 0
0x0107753D - LabVIEW <unknown> + 0
0x01077F8F - LabVIEW <unknown> + 0
0x01078823 - LabVIEW <unknown> + 0
0x010788CE - LabVIEW <unknown> + 0
0x005FABA6 - LabVIEW <unknown> + 0
0x00A8FAE7 - LabVIEW <unknown> + 0
0x00A88F3C - LabVIEW <unknown> + 0
0x00A891D9 - LabVIEW <unknown> + 0
0x00A9040E - LabVIEW <unknown> + 0
0x00A90514 - LabVIEW <unknown> + 0
0x00A8CD7F - LabVIEW <unknown> + 0
0x00A8CE3F - LabVIEW <unknown> + 0
0x011461FE - LabVIEW <unknown> + 0
0x010F52E0 - LabVIEW <unknown> + 0
0x010F54FC - LabVIEW <unknown> + 0
0x0110FD6A - LabVIEW <unknown> + 0
0x0112A211 - LabVIEW <unknown> + 0
0x0112AD04 - LabVIEW <unknown> + 0
0x0109BB64 - LabVIEW <unknown> + 0
0x01110B81 - LabVIEW <unknown> + 0
0x011191CA - LabVIEW <unknown> + 0
0x01119D57 - LabVIEW <unknown> + 0
0x0111A110 - LabVIEW <unknown> + 0
0x0111AD41 - LabVIEW <unknown> + 0
0x0111AF2A - LabVIEW <unknown> + 0
0x0111B3AA - LabVIEW <unknown> + 0
0x0111B4A8 - LabVIEW <unknown> + 0
0x01080718 - LabVIEW <unknown> + 0
0x01080748 - LabVIEW <unknown> + 0
0x01080748 - LabVIEW <unknown> + 0
0x010807C5 - LabVIEW <unknown> + 0
0x010964B6 - LabVIEW <unknown> + 0
0x0109943D - LabVIEW <unknown> + 0

I don't think I have to repair the installation. It is LabVIEW 8.6 not 8.6.1. I think I understand what I did to cause the problem. It's something that reflects some of my mindset when I program. I do some up front design and planning, but when I start to program, other things come out and I make changes on the fly as I go.
The sequence of events is this...
1. Create a class
2. Added 4 booleans
3. Created some dynamic vi's by right clicking on the class in the project window. Save the newly created VIs.
4. Delete the booleans from the class definition and add some numbers and strings instead.
5. Do not delete the original dynamic vi's
6. Close LabVIEW and go home.
7. Next morning re-launch the project file and when LabVIEW tries to link the vi's to the class it doesn't know
what to do. So it asks if I want to add, remove or cancel re-linking the original vi's. If you tell it to relink or even cancel, LabVIEW dies.
8. The message: "DAbort: Should never have already existing class when patching the thing that is loading the class!" appears.
Perhaps you should just add a check for an insane object between the CRT and the chair!
Thanks. While I don't like getting crashes, this one I think is understandable.
Jamey

Similar Messages

Error in visualizing a Data Form "WDEFGenerator.cpp"

Hi,
I have migrated an HFM application from version 4.01 SP2 to version 11.1.2.1
Everything works fine appart from an error in visualizing a Data Form:
In the previous version of HFM this error was not verified.
If I disable the option SuppressNoDataRows I get no errors but I would like to keep this option enabled.
Does anyone know what could be the problem?
The error I'm getting is:
Error Reference Number: {3783BC27-A47D-463A-9F21-5E1C2B55A775};User Name: hypadmin@Native Directory
Num: 0x80070057;Type: 0;DTime: 6/19/2012 4:41:11 PM;Svr: BMI-2K8-HFMPA;File: WDEFGenerator.cpp;Line: 1407;Ver: 11.1.2.1.103.3505;
Num: 0x80070057;Type: 0;DTime: 6/19/2012 4:41:12 PM;Svr: BMI-2K8-HFMPA;File: WDEFGenerator.cpp;Line: 3284;Ver: 11.1.2.1.103.3505;
Num: 0x80070057;Type: 0;DTime: 6/19/2012 4:41:12 PM;Svr: BMI-2K8-HFMPA;File: WDEFGenerator.cpp;Line: 3166;Ver: 11.1.2.1.103.3505;
Num: 0x80070057;Type: 0;DTime: 6/19/2012 4:41:12 PM;Svr: BMI-2K8-HFMPA;File: CHsvWebFormGeneratorACM.cpp;Line: 3687;Ver: 11.1.2.1.103.3505;
Num: 0x80070057;Type: 0;DTime: 6/19/2012 4:41:12 PM;Svr: BMI-2K8-HFMPA;File: CHsvWebFormGeneratorACM.cpp;Line: 3389;Ver: 11.1.2.1.103.3505;
Num: 0x80070057;Type: 0;DTime: 6/19/2012 4:41:11 PM;Svr: BMI-2K8-HFMPW;File: CHsvWebFormsACV.cpp;Line: 569;Ver: 11.1.2.1.103.3505;
And the data form script is:
ReportType=WebForm
ReportLabel=1_1_12_1
ReportDescription=Trade Receivables > 12 months
BackgroundPOV=S#ACT.w#<Scenario View>.V#<Entity Currency>.A#[None].I#[ICP None].C1#[None].C2#[None].C3#[None].C4#[None]
SelectablePOVList=Y{[Hierarchy]}.P{[Second Generation]}.E{GRBRA000.[Base]}
C1=C1{FL_CURR.[Base]}
R1=A#3_03_01.I#[ICP Entities],AddMember:I{CONS}
R2=A#3_03_01.I{CONS}
R3=A#3_03_02.I#[ICP Entities],AddMember:I{ASS}
R4=A#3_03_02.I{ASS}
R5=A#3_03_03.I#[ICP Entities],AddMember: I{PARENT}
R6=A#3_03_03.I{PARENT}
R7=A#3_03_04,NoSuppress
R8=A#3_03_1.I#[ICP Top],CustomHeaderStyle:font: bold,NoSuppress
FormRowHeight=20 px
PrintNumRowsPerPage=10
PrintNumDataColsPerPage=3
SuppressNoDataRows=True
ShowLabels=True
SuppressColHeaderRepeats=False
HeaderOptionAccount=ShowLabel,ShowDescription,Length:50
HeaderOptionICP=ShowDescription
HeaderOptionCustom1=ShowDescription
HeaderOptionCustom2=ShowDescription
Thanks
Best Regards

Hi
Check they have the "Data Form Write Back from Excel" role in Shared Services.
See p.133 of the security guide for more info -
http://docs.oracle.com/cd/E17236_01/epm.1112/hss_admin_1112200.pdf
Regards
jpr

CPP Assertion Error when navigating in Obiee 11g

Hi,
I have a report which uses SQL filters and I am trying to navigate from this report to another page.
And I see the following error :
Dashboard Display Error
Assertion failure: isXsiTypeSqlExpression(rExpr) at line 67 of C:\ADE\aime_bi\bifndn\analytics_web\main/project/webreport/exprformulautils.cpp
Error Details
Error Codes: ACIOA5LN
Some forums mentioned that re-creation of saved SQL filters would help but it didn't.
Has anyone faced similar errors ?
Thanks for any pointers.
- Sujana

Sujana,
This is a bug in 11g, apply patch 12561330.
Rgds,
Dpka

After System Update last night, the system will not boot with IOPlatformExpert.cpp:1504 error

I have had Lion for a 2, 3 months on the iMac 27 inch purchased last October (2011). Last night I chose to update the system, and deselected iMoves update because it was 1GB, and chose only 4 updates, including iTunes, Safari (i think)... But the update says error, and ask to restart the system (it won't restart itself, so I waited 30 minutes, and then pressed the Power button for 10 seconds, to let it power down, and press Power again to power it up).
However, after that, the system failed to boot up, showing a
panic(cpu 0 caller .....)" "Unable to finder driver for this platform: \"ACPI\". ... xnu-1699.26.8/iokit/Kernel/IOPlatformExpert.cpp:1504
This is not typical of the upgrade process. So I searched the Internet forIOPlatformExpert.cpp:1504 and some people said it is a hard drive error, but then I powered down and pressed Options when booting up, and was able to boot to Windows 7 (bootcamp)... and was able to boot to the "Recovery", which let me choose
Restore from Time Machine Backup
Reinstall Mac OS X
Get Help Online
Disk Utility
what should I do now to fix it so that it can boot again?

This error is caused by one of the updates you applied, namely the Thunderbolt Software Update 1.2. Many people have been affected by it, including me. I did what Linc Davis has suggested above to fix it. The most extensive discussion about the problem, with ways to fix the problem, is here:
https://discussions.apple.com/thread/4020399?start=0&tstart=0

Adobe Media Encoder (CS5) has encountered an error (WinFile.cpp-759)

I have a 714 MB Xvid file that I want to split into smaller pieces. I have gone successfully through a similar process earlier with a larger Xvid file using the same version of Adobe Media Encoder (CS5). It appears that no matter which output video format I choose, the process crashes with the following error message shown in a new pop-up dialog:
"Adobe Media Encoder has encountered an error. [..\..\Src\Win\WinFile.cpp-759].
(Even the source program file line number 759 in the above error message is always the same, regardless of my chosen output file format.)
The only option available from this point onwards is the "Continue" button. When I click Continue the program terminates with the Windows program crash message "Adobe Media Encoder CS5 has stopped working. A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available. <Debug> / <Close program>"
My search for other similar problem reports revealed that some user(s) has/have experienced a very similar problem in CS4, but the source line number was slightly different in CS4. Both problems are probably caused by the same error in Adobe's software. The small difference in source line numbers is probably due to some (minor) and probably unrelated changes to this C++ source module (WinFile.cpp).
It might of course be the case that this particular input video file has some rare encoding or other embedded problem. However, the fact that I can view the video without problems using Windows Media Player does not support this theory.
Apart from this message board I could not find any other avenue to report this bug to Adobe (without paying for support - which I am obviously not going to do as this is clearly a programming bug in the software). Hopefully some Adobe developer responsible for Media Encoder maintenance will read this forum from time to time and would subsequently inspect the source module for any obvious defects. I could supply the source video file with which this problem can be reproduced at will.
Regards
Jouni Juntunen

CS4 Adobe Media Encoder & FMLE are two different softwares - you can post your query here:http://forums.adobe.com/community/ame

Adobe Media Encoder CS4 Error: WinFile.cpp-754

When encoding video from one format to another (no matter what is source and what is result file format) I have an error after some time or in the begining of the process. "Adobe Media Encoder has encountered an error ..\..\Src\Win\WinFile.cpp-754"
Version of Encoder is 4.2.0.006 (updated).
I can't encode any files. What is the problem?

Any update on this?
I get WinFile.cpp-754 on CS4 and WinFile.cpp-785 on CS5 trying to encode the same AVI file.
I'm trying to load a 59.94 fps AVI file into PremierPro CS4 and need to convert it to something else (correct?)

Adobe Media Encoder Error with MPEG2 Formats [../../src/Command.cpp-2519]

I am trying to use some of my presets using MPEG2 format and it is giving me this error: [/Volumes/BuildDisk/builds/ame602_mac/main/app/frontend/prj/mac/../../src/Command.cpp-251 9]. I try the system presets that use MPEG2 and I get the same error. I notice if I try to make a new preset, I do not even have the option to choose MPEG2. I only get MPEG4 or MPEG4 (Legacy). I am using AME 7.0.2; if anyone has an idea on why I can't use MPEG2 please let me know.
Thanks,
Mike

Hi mboory,
Please mention the exact version of Media Encoder CS6 that you are using and also the version of operating system. Please check the below link as well.
http://forums.adobe.com/message/4402558
Regards,
Vinay

Adobe Media Encoder error when encoding: winfile.cpp-759

Mods: Please move this to the appropriate thread wasn't sure to move it to Premiere or Flash
I receive this error when trying to encode AVI to H.264 using Adobe Media Encoder CS5 (64bit):
When searching through the forums, several suggestions for CS4 and current releases that I have tried are:
clearing the media cache through AME, and the folder location in %APPDATA%\Adobe\Common\
installing K-Lite Codec pack
changing the media cache files folder to a separate disk entirely
updating to the latest version (at the time of post ver 5.0.1.0)
uninstalling and re-installing AME (as an error might have occurred during updates)
verifying that the CPU has SSE support and is enabled
I expanded my search to google which gave similar errors (winfile.cpp-754, winfile.cpp-758, etc.) and a few responses were uninstalling any Nero products (don't have any burning programs on this computer - unless you count Windows)
The system that I have is:
MS Windows 7 64-bit
Intel Core 2 Quad Q6600 @ 2.40GHz
2x 1.0GB Dual-Channel DDR2 @ 800MHz
512MB GeForce 9600 GHz
2x 250GB HDD Mirrored
External USB 500GB HDD
Any ideas as to what the cause of this is?
LK.

The information about installing codecs packs is true. It usually does more damage to your codecs already present with software already installed on your computer, and the registry settings even after removing it. That is why it is in good practice to do full image back ups monthy, saving the latest 3 for when I utilize last resort methods such as codec packs.
Adobe CS5 software has been working fine on my computer ever since its installation July. I forgot to mention that I have successfully used Premiere Pro CS5 for editing a dozen files ranging from SD small res to HD 1080i. This also includes just using AME CS5 itself for transcoding files for supported playback on different devices. I notice a greater difference in speed when using a more up to date machine that uses a GTX 285 card for GPU playback - a lot faster and smoother.
I have a 2nd, slightly older computer, that houses an extra drive I put in there to use as a scratch disk. I occasionally add that disk to the computer that has CS5 currently installed as a scratch disk for editing video. The external USB drive is used to store the final product and my backups.
This error has only come up 1 time out of the 49 files I have encoded that usually run 10 minutes to 1.5 hours. I had 9 AVI files in the encoding queue and it always stopped at this 1 particular file. I skipped the file and encoded the rest successfully, but I want to know why it causes an error in AME because this has never happened before. I have even used it on a more up-to-date machine spec wise, thinking that there is a 1% possibility that it doesn't like my computer. The same error was produced. The 9 files that I did encode are roughly the same video and audio format - just this one is the error.
I gave the file to my friend who was supposed to analyze before I got home - I usually assist them in PC problems and built his better-than-mine PC.
Any other suggestions for this error and/or a solution?
Lk

Adobe Media Encoder error [..\..\Src\RenderFrame.cpp-199]

Adobe Media Encoder error [..\..\Src\RenderFrame.cpp-199]
I'm trying to utilize Prelude to actually TRANSCODE some R3D material. Since R3D clips are spanned, Prelude can 'reassemble' them. (I don't understand why AME can't do this since Prelude uses AME... but...)
I get this error when trying to start the transcode in Prelude... any help out there?
Thanks!

Hi mboory,
Please mention the exact version of Media Encoder CS6 that you are using and also the version of operating system. Please check the below link as well.
http://forums.adobe.com/message/4402558
Regards,
Vinay

What is memory.cpp at line 1038?

We have been running the same test in LabVIEW for a few years. Now all of a sudden, we are starting to get a memory.cpp error at line 1038. The test normally runs days at a time (~2 weeks), but we are getting this error after about 18-24 hours. Any ideas of what could cause this? Could this be caused by any Windows XP hotfixes? We are using LabVIEW 7.1 on a windows xp machine.

I've already checked out that particular site for info. And we do open and close files in our tests. And we do have quite a few loops. But it has worked with no issues for a few years and much longer time spans (and also more open/close files and loops). So after the error occurred on our only two machines (with exact set up) that run LabVIEW 7.1 (the rest are still on 6), we rolled one back to a date before all of the hotfixes occured and we have had no problems since. The second machine had an issue with rolling back so IT came and reinstalled XP. The problem is that they install an updated version and we cannot install an older one. It has Service Pack 3 in it and I think there are some hotfixes that came along with it that are the source of the problem. But I can't gaurantee it. Hopefully we'll figure it out soon.

Inconsistency between R3 and APO. - not getting reconciled in CCR or CPP.

Hi,
We have a PO that is not getting reconciled in CCR and CPP.
it give the message
Unit of conversion from H to KG for the Product "ABCD" is not possible.
this PO has 3 products and off which only one is not getting reconciled. rest two are showing correctly in APO and R3.
The conversion is not maintained in material master for the rest for the two products also....
i have a similar set up in my quality environment. i tired to change the PO with some qty and it refelcts in APO immediately..
Any idea on where the conversion is not happening correctly???
Thanks
Aswath

Hi,
Have u activated detailed application CIF log. Can you check the error details in APO using t-code /n/SAPAPO/C3 or in ECC using t-code CFG1.
Can you also try to send the queue using /n/SAPAPO/CPP. CCR will show no error only when there are no queues in SMQ1 or SMQ2 of both the systems and also no queue pending in postprocessing.
Best regards,
Vaibhav

JNI Invocation: open file in Java, write file in CPP

Hello,
Warning: I am a dunce, bad CPP code ahead!
Using JNI invocation, I am trying to read a binary file in Java and write it in CPP.
Everything compiles and runs without error, but the input and output jpg files are of course different.
TIA to any help,
kirst
(begin ByteMe.java)
import java.io.*;
public class ByteMe
    // Returns the contents of the file in a byte array.
    public byte[] getBytesFromFile(String strInfo) throws IOException
        System.out.println("Testing:" + strInfo);
        File file = new File("1.jpg");
        InputStream is = new FileInputStream(file);
        // Get the size of the file
        long length = file.length();
        // Create the byte array to hold the data
        byte[] bytes = new byte[(int)length];
        // Read in the bytes
        int offset = 0;
        int numRead = 0;
        while (offset < bytes.length
               && (numRead=is.read(bytes, offset, bytes.length-offset)) >= 0) {
            offset += numRead;
        // Ensure all the bytes have been read in
        if (offset < bytes.length)
            throw new IOException("Could not completely read file "+file.getName());
        // Close the input stream and return bytes
        is.close();
        return bytes;
    public ByteMe()
          //System.out.println("in constructor");
}(end ByteMe.java)
(begin ByteMe.cpp)
#include <stdlib.h>
#include <string.h>
#include <jni.h>
#include <windows.h>
// for file operations:
#include <fstream>
int main( int argc, char *argv[] )
     JNIEnv *env;
     JavaVM *jvm;
     JavaVMInitArgs vm_args;
     JavaVMOption options[5];
     jint res;
     jclass cls;
     jmethodID mid;
     jstring jstr;
     jobject obj_print;
     options[0].optionString = "-Xms4M";
     options[1].optionString = "-Xmx64M";
     options[2].optionString = "-Xss512K";
     options[3].optionString = "-Xoss400K";
     options[4].optionString = "-Djava.class.path=.";
     vm_args.version = JNI_VERSION_1_4;
     vm_args.options = options;
     vm_args.nOptions = 5;
     vm_args.ignoreUnrecognized = JNI_FALSE;
     // Create the Java VM
     res = JNI_CreateJavaVM(&jvm,(void**)&env,&vm_args);
     if (res < 0)
          printf("Can't create Java VM");
          goto destroy;
     cls = env->FindClass("ByteMe");
     if (cls == 0)
          printf("Can't find ByteMe class");
          goto destroy;
     jmethodID id_construct = env->GetMethodID(cls,"<init>","()V");
     jstr = env->NewStringUTF(" from C++\n");
     obj_print = env->NewObject(cls,id_construct);
     // signature obtained using javap -s -p ByteMe
     mid = env->GetMethodID(cls, "getBytesFromFile", "(Ljava/lang/String;)[B");
     if (mid == 0)
          printf("Can't find ByteMe.getBytesFromFile\n");
          goto destroy;
     else
          jbyteArray jbuf = (jbyteArray) env->CallObjectMethod(obj_print,mid,jstr);
          jlong size = jsize(jbuf);
          printf("size is: %d\n", size); // size shown in output is
          std::ofstream out("data.jpg", std::ios::binary);
          out.write ((const char *)jbuf, 100000);
     destroy:
         if (env->ExceptionOccurred())
            env->ExceptionDescribe();
    jvm->DestroyJavaVM();
}(end ByteMe.cpp)

Hello,
Me again. Well, not such a dunce after all. Here is code that works correctly, and compiles with no errors and no warnings.
Will much appreciate help with clean-up code.
TIA,
kirst
(begin ByteMe.java)
import java.io.*;
public class ByteMe
    public long getFilezize(String strInfo) throws IOException
          // demonstrates String parameter passed from CPP to Java:
          System.out.println("(getFilesize) Hello world" + strInfo);
          File file = new File("1.bmp");
          InputStream is = new FileInputStream(file);
          // Get the size of the file
          long length = file.length();
          is.close();
          return length;
    // Returns the contents of the file in a byte array.
    public byte[] getBytesFromFile(String strInfo) throws IOException
        System.out.println("(getBytesFromFile) Hello world" + strInfo);
        File file = new File("1.bmp");
        InputStream is = new FileInputStream(file);
        // Get the size of the file
        long length = file.length();
        System.out.println("length is: " + String.valueOf(length));
        // Create the byte array to hold the data
        byte[] bytes = new byte[(int)length];
        // Read in the bytes
        int offset = 0;
        int numRead = 0;
        while (offset < bytes.length && (numRead=is.read(bytes, offset, bytes.length-offset)) >= 0)
            offset += numRead;
        // Ensure all the bytes have been read in
        if (offset < bytes.length)
            throw new IOException("Could not completely read file "+ file.getName());
        // Close the input stream and return bytes
        is.close();
        return bytes;
    public ByteMe()
          //System.out.println("in constructor");
}(end ByteMe.java)
(begin ByteMe.cpp)
          Signature obtained with command:
               "C:\Program Files\Java\jdk1.5.0_15\bin\javap.exe" -s -p ByteMe
               Compiled from "ByteMe.java"
               public class ByteMe extends java.lang.Object{
               public long getFilezize(java.lang.String)   throws java.io.IOException;
                 Signature: (Ljava/lang/String;)J
               public byte[] getBytesFromFile(java.lang.String)   throws java.io.IOException;
                 Signature: (Ljava/lang/String;)[B
               public ByteMe();
                 Signature: ()V
     Compiled VC++ 2005 Express, run on Vista
#include <stdlib.h>
#include <string.h>
#include <jni.h>
// file operations
#include <fstream>
int main( int argc, char *argv[] )
     JNIEnv *env;
     JavaVM *jvm;
     JavaVMInitArgs vm_args;
     JavaVMOption options[5];
     jint res;
     jclass cls;
     jmethodID mid;
     jmethodID sizeid;
     jstring jstr;
     jobject obj_print;
     jlong filesize;
     options[0].optionString = "-Xms4M";
     options[1].optionString = "-Xmx64M";
     options[2].optionString = "-Xss512K";
     options[3].optionString = "-Xoss400K";
     options[4].optionString = "-Djava.class.path=.";
     vm_args.version = JNI_VERSION_1_4;
     vm_args.options = options;
     vm_args.nOptions = 5;
     vm_args.ignoreUnrecognized = JNI_FALSE;
     // Create the Java VM
     res = JNI_CreateJavaVM(&jvm,(void**)&env,&vm_args);
     if (res < 0)
          printf("Can't create Java VM");
          goto destroy;
     cls = env->FindClass("ByteMe");
     if (cls == 0)
          printf("Can't find ByteMe class");
          goto destroy;
     jmethodID id_construct = env->GetMethodID(cls,"<init>","()V");
     printf("%s\n",id_construct);
     jstr = env->NewStringUTF(" from C++!\n");
     if (jstr == 0)
          // Normally not useful
          printf("Out of memory (could not instantiate new string jstr)\n");
          goto destroy;
     obj_print = env->NewObject(cls,id_construct);
     //BEGIN BLOCK to get file size
     sizeid = env->GetMethodID(cls, "getFilezize", "(Ljava/lang/String;)J");
     if (sizeid == 0)
          printf("Can't find ByteMe.getFilezize\n");
          goto destroy;
     else
          printf("got here\n");
          filesize =(jlong) env->CallObjectMethod(obj_print,sizeid,jstr);
          printf("got filesize\n");
     // END BLOCK to get file size
     // BEGIN BLOCK to write file
     mid = env->GetMethodID(cls, "getBytesFromFile", "(Ljava/lang/String;)[B");
     if (mid == 0)
          printf("Can't find ByteMe.getBytesFromFile\n");
          goto destroy;
     else
          jbyteArray ret =(jbyteArray) env->CallObjectMethod(obj_print,mid,jstr);
          // Access the bytes:
          jbyte *retdata = env->GetByteArrayElements(ret, NULL);
          // write the file
          std::ofstream out("data.bmp", std::ios::binary);
          //out.write ((const char *)retdata, 921654);
          out.write ((const char *)retdata, (long)filesize);
     // END BLOCK to write file
     destroy:
         if (env->ExceptionOccurred())
            env->ExceptionDescribe();
    jvm->DestroyJavaVM();
}(end ByteMe.cpp)

LV crashes when I try to save a VI - "fpsane.cpp line 269 error"

Dear LV users:
“Fpsane.cpp, line 269 error”
I have this error when I modify the VI and try to save it. Often I run it once and save it without problem. When I modify it again and try to save it, the error appears and LV crashes.
First I made a 6.0.2 upgrade and later I followed the “solving troubles” procedure at NI home page, like empty the TEMP directory and so on.
Later I sent my VI to NI support and I received the confirmation that they were able to reproduce the error, but not able to isolate it. Also they wrote that “Maybe can be a problem with the charts” and “it could be a bug in LV 6.0.2 which is fixed in LV 6.1”.
They saved my VI as a 6
.1 version and there were no problems (any error).
The problem is:
“ LV 6.1 is the next release (newest version) of LV and it will be released this year (the date is not fixed). That's not an update like LV 6.0.2 but a new version of LV. It must be purchased”
So I have a trouble here. I have some VIs that contains some parts in common. Now they are crashing too. I’m not confident anymore to make tests and modifications, since LV will crash again. What I’m doing after run my VI is exiting LV and open the VI again. Only after I can realize (and save) the modifications. This way is really a pain in a neck....
Please, can someone tell me a good way to isolate this problem or to solve it? I really don’t want to wait LV 6.1 nether to buy it to solve this “bug”....
Thank you in advance
Rodolfo
OS: Nt4 sp 6
LV 6.0.2

Dear LV users
Sorry for not have included the VI.
"test time save format.vi" is a learning program that contains some ideas to be used in another one. The error (fpsane.cpp) that appears here also was detected in LV 6. On the first time after grouping/edit some controls.
This error occurs when you modify the VI and try to save it. Often you run it once and save it without problem. When you modify it again and try to save it, the error appears. This is the same problem that happened with 2 other VI, even with one LV original example (after grouping).
The same error happened in another computer (also running NT4). All libraries were rebuilt during the installation of LV 6.02 and the TEMP directory is empty.
I hope that this vi will help us.
Thanks ag
ain
Rodolfo
Attachments:
Test_time_save_format.zip ‏92 KB

Fatal Internal Error: "image.cpp", line 13192 when trying to insert a cursor to graph

NOTE: This IS a duplicate post from the Breakpoint. Text slightly changed. The post in Breakpoint can be deleted. All comments should be placed in this thread.
I resolved the "Fatal Internal Error: "image.cpp", line 13192 when trying to insert a cursor to graph", but would like to share to find out if others have seen this and to determine whether this is a bug, or if it's time to redo my PC, or buy a new one..
I have an existing graphs (qt 6) which originally had 2 cursors. This occurred while trying to add the third cursor.
Up until attempting to add the last cursor, the program worked great, and I had been running tests for a while. However, I do recall seeing this problem when creating the original cursors, but not to this extent. Plus I don't remember the original error message from that time.
I needed to add one more cursor to the existing graphs. As soon as I add a new cursor and set it's properties, I get a nasty error message and without warning LV8.2 simply closes itself (well, the only warning was the error message. Tried it 3 times, same result.
Here are the steps:
Shut down the PC, went for a coffee, rebooted the PC. Opened the LV project, opened the VI. Immediately went to the graph properties to add the new cursor by doing the following steps:
Right click graph indicator icon on block diagram.
Select Properties.
Click on cursor tab.
Click on Add
Select Cursor 2 (3rd one, newly created)
Change color
Select cursor as a line
Remove checkmark for "show cursor"
Click OK
I need to do this to 3 other graphs, same steps. And as soon as I get to the step before clicking OK, I get the error message.
I managed to get an additional one done, by immediately saving after each step (yep going in & out of the properties). But I've had this problem before when creating the first two cursors.
Is it a bug? Anyone else seen this? Using LV8.2. And the message is right about LOOSING ALL unsaved work!!!!
Here are more observations:
Tried creating a new one on the second graph. As soon as I clicked on the color, it crashed!
See the error explanation below. It is really clear, now anyone can solve it    LOL!!... According to the error log, there's a bad image out there
.\manager\image.cpp(13192) : DAbort: bad image in ValidateImage
$Id: //labview/branches/Europa/dev/source/manager/image.cpp#47 $
0x007A81E8 - LabVIEW <unknown> + 0
0x007A7BDB - LabVIEW <unknown> + 0
0x00829D74 - LabVIEW <unknown> + 0
0x008546CD - LabVIEW <unknown> + 0
0x00C054E6 - LabVIEW <unknown> + 0
0x0081B9C8 - LabVIEW <unknown> + 0
0x0081EB9A - LabVIEW <unknown> + 0
0x0084D9D4 - LabVIEW <unknown> + 0
0x00854663 - LabVIEW <unknown> + 0
0x00C054E6 - LabVIEW <unknown> + 0
0x0085F7A1 - LabVIEW <unknown> + 0
0x00BBACDD - LabVIEW <unknown> + 0
0x00C06A2F - LabVIEW <unknown> + 0
0x0085AA46 - LabVIEW <unknown> + 0
0x00C06A2F - LabVIEW <unknown> + 0
I observed the title bar after making changes to the properties. I noticed that 3 out of 4 times, while changing the properties of the graphs to include the cursor, and saving after each & every step, that there were no stars appearing on the title bar to indicate "unsaved changes". Saving was also much slower than usual. I suspect, the program never got to placing the star before saving occurred. However, I am noting everything.
After creating the cursors, saving was and is normal, and the program runs well..   I have run tests without problems.
Does anyone have a clue at what causes this? Has anyone seen this before?
Thanks,
RayR

Hi Donovan,
I can't remember seeing this elsewhere. When I get a chance, I'll create a new (blank) vi with new graphs and will repeat the steps.
I will let you know if I see this in the new vi.
Thanks!
RayR

Internal error: "memory.cpp", line 593 with PXI 8175

Hi,
I have created a program with Labview RT 7.0 which makes acquisition, storage and display of data with PXI controllers 8175.
I used Datasocket for the data display on a deported computer.
Because of the number of the Datasocket tags used, instead of sending values all the time, I'm sending value for the deported computer only if the user needs to see it.
For example : if the user needs to see data, so only Datasocket tags for data display will be active, and if the user needs to see parameters values, so only parameters datasockets tags will be active. And, if the display program is in "standby" mode, almost all datasocket aren't active.
So when the user needs to see data values, he opens the data values window of the display program, and then, the datasockets tags for data value are now active, but : sometimes at this moment, the PXI stops with an "internal error "memory.cpp" line 593"!
The only solution is to manually reboot the PXI, the programmatically reboot doesn't work in this case of error. But it is far away from the displaying computer.
The error happens regularly after a 2 weeks period of standby. So I though about a memory overflow, I checked all the arrays, and none of them is growing to the infinity.
If someone knows about this problem, I will be very happy to learn about how to get rid of it!!!
Best Regards,
G Liagre
Best regards,
G Liagre

Hi Rob, Hi Matthieu,
Thank you for your reply.
I found in the database many reply about this error, but none of them were helpfull for me.
I tryed your link to the knowledge data base, but the error described there is for dll association in LabView and interface nodes.
I didn't used any interface node in my code.
The problem is that I cannot test my program on the PXI because I don't have access to it rightnow (only by remote desktop, and with a 56k modem..)
Let me give you a part of this huge code.
I suspect this part of the code to be the one which create the problem, but it's not sure.
If you find something obviously wrong, tell me!
Best regards,
G Liagre
Best regards,
G Liagre
Attachments:
Communication.zip ‏931 KB

OMUDCClassLinker.cpp#68

Similar Messages

Maybe you are looking for