Winocc.cpp line 329 - using CWGraph in MFC OCX project

I'm trying to create my own custom ActiveX control for use in a third party application. My control consists of a dialog window (CDialog derived) that I use for data display. This works fine, but if I drop a CWGraph control onto my dialog, the control crashes the app with an assert in winocc.cpp Line:329. Is what I'm attempting possible? Can anyone tell me why it crashes? I'm using VS2005. I've included a dummy project that shows the problem. I'm still sort of new to VC++ so I may very well have missed something obvious.
Thanks-
Attachments:
MyTestOCX.zip ‏4258 KB

Hi codeman,
Have you tried replacing your CWGraph control with any other common Visual Studio controls, like a button. I don't think that it is the CWGraph that is causing your application to crash. I think it is some of your code behind the project. I'd like to see if we can verify the operation with a different kind of control.
Regards,
Marty H.
National Instruments

Similar Messages

LV 6.1, 3D Surface Graph sometimes collapses (doesn't work stably); plus blocks use of remotely controlled panel by LV run-time engine (error #26:"window.cpp", line 11518

1) "3D Surface Graph" does not work stably; sometimes it changes its properties (e.g. plot style) without me doing anything prior to that; a couple of times it lost a complete sense so that I had to delete the graph and install it again
2) I tried to remotely run a VI which contains a 3D Surface Graph in it. It turns out, the use of the "3D Surface Graph" somehow blocks the remote control over the panel. As a result of that, I got the following error message: Error #26: "window.cpp", line 11518 (with LabVIEW version 6.1).
3) Is it possible to plug into the 3D Surface Graph a few plots at
the same time since there is a built-in control "plot number" (somehow by bundling them up or putting into an array - I tried both but didn't work) or it can be done merely by use of 'case' structure preceding the Graph, where case structure decides which plot to pass into the 3D graph?
Attachments:
3D_Graph_ver_1.bmp ‏214 KB

Hello mjoler,
Thank you for contacting National Instruments.
The following example will show you how to plot multiple 3D plots on a single 3D graph. Modeling your VI after the example may also alleviate the instability that you have been experiencing.
http://sine.ni.com/apps/we/niepd_web_display.display_epd4?p_guid=B123AE0CBA19111EE034080020E74861&p_node=DZ52038
As far as the error you are receiving, it's difficult to say what could be causing this. ActiveX controls embedded on a front panel sometimes do not display on a remote client because they draw and operate almost completely independent of LabVIEW. If possible, try remotely controlling your VI with a client computer that has a complete installation of LabVIEW. The error could also be a bu
g. Try downloading the evaluation version of LabVIEW 7.0 from http://www.ni.com/labview. By doing this, we can determine if it is a bug in the older version that has been fixed in the latest version.
Let me know how this goes.
Matthew C
Applications Engineer
National Instruments

Error #3: "memory.cpp", line 639; VI used to work, now it stopped

Hello,
I am running LabVIEW 6.0.2. I have a rather complicated VI that used to work just fine. I have run it a bunch of times without any problems. I have not changed anything at all, and now it gives me Error #3: "memory.cpp", line 639 every time I run it. Does anybody know what could have happened?
Thanks,
Corey

Corey,
Not without seeing the code.
Perhaps there is some memory leakage going on, or open references that cannot be resolved.
Also, check your memory to make sure it is still working (view your RAM amount).
Other possibilities include possible conflicts with software running in the background, or software you recently installed.
Check your task bar, and make sure your virus protection and anything else unecessary is off. These can eat memory and processor time.
Other than that, navigate to the site where the bug tells you to (don't remember off the top of my head) and report it to NI.
Good luck

Memory leak using CWGraph

I have a memory leak problem using the CWGraph control.
I have an SDI application (MFC using Measurement Studio) and I generate dynamicaly a dialog containing a 2D Graph, and I use the OnTimer() of the dialog to generate data and to update the graph, with a timer of 50ms. In OnTimer() function I have a loop to generate
and to update two plots on the graph. When I call a method of the graph (for example for changing the color of the plot or for updating a plot (using PlotXvsY)), I have a periodic increasing of memory with a fixed amount of memory (4k). In the same OnTimer() function I update also some CWSlide controls without memory leaks.
If I comment the line that call a method of graph
(ex. m_Graph.Plots.Item(1)....), the code works wi
thout memory leaks.
I'll apreciate any suggestion about this problem.

I had the same memory leak problem with my program as well. I do not think it is because of using CWGraph. Memory leaks occur when you allocate memory and did not free them. The problem will accumulate and crashed randomly (sometime it crashed when you just move mouse around). Try this: if the program does not crash (memory leak crash) on the first time it compiles and runs, it is probable has nothing to do with the CWGraph. On the second and third run, if you did not free variable, the program will usually crashed. If your program crashed on the first time it runs, the problem might be something else.

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

Labview version 6.1 failure:"linker.cpp", line 2302

I have the labview version 6.1 failure:"linker.cpp", line 2302 fault.
Does any one can help me please ?
Solved!
Go to Solution.

Actually HeapPeak existed as far back as LabVIEW 4 or maybe even 3. However it is not usually helpful for linker errors as that is something in the LabVIEW compiler itself. HeapPeak can be sort of useful for Insane errors to locate the element that the compiler considers insane (and consequently delete and/or rewire it).
If this is a recent error on a VI that used to work before, it is most likely related to a corruption to the VI and the best course of action is to replace the VI from a backup (source code revision control would be a great advantage here). If it is something where no previous (working) state is known about, then it is going to be a tough cookie. This version is 14 years old and eventhough I still have some installation of that version somewhere it is several years ago that I started that up for more than some accidential reasons. I'm pretty sure NI would need to do some archeological work nowadays to come up with a system they could use to replicate such an error and the OP would need to be a pretty high profile customer that they would go through that sort of effort.
Maybe it is related to this error. It is the closest available in the publically accessible list of errors. A complete recompile of the entire source code tree is definitely one of the first actions to try. It may fix the problem or run into even more errors that could maybe point into a more specific location. Upgrading to a more recent LabVIEW version is another possibility although hampererd by the fact that the currently shipping version isn't officially supporting XP anymore and that the Vision software is one piece of software that underwent serious changes in the course of time and an update from 6.1 to the most recent version is most likely not a seamless operation.
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Slide Show ERROR, Internal software\Vobulator\BlockPlanner\.cpp Line 217

I'm putting together a slide show DVD. There are a total of 7 slide shows containing 480 pictures. All pictures are jpg's about 1000X1600 pixels and 500KB-700KB each. I have 3 menus for navigation. Not all of the chapter menu buttons point to a "slide show", some of them point to a picture inside certain slide shows according to my client's requests. (example, slide show 1 contains 70 pictures. Chapter 1 points to "slide show 1" Chapter 2 points to "slide show 1 photo 50"). All slide shows are linked so that when the first slide show is over, it will automatically "end action" to the next slide show etc... All my settings are typical. NTSC 4:3 SD 720X480 progressive.
There are NO video files in my DVD at all. No timelines at all. No audio at all.
The Symptoms/problem that I'm getting is this, when I try to Preview my DVD and ALSO when I try to build my DVD, the build will go through and "build the slide shows" then after it does that, this will come up
I've read some of the previous posts (one of them is in French for cryin out loud. Had to use Bing translator and it sounds all weird). What I can gather is this,
Re: internal software error: .\Vobulator\BlockPlanner\BlockPlanner.cpp, line 217
I found out it was due to selecting an image file as the video layer
in a menu, causes the error everytime. I just paste the image in with
'edit in photoshop' instead now. But thanks."
Another person said just about the same thing... The only problem is, I have no idea what this means. I don't know what it means to "select an image file as the video layer in a menu..."
Hardware/software is as follows:
custom build:
i5 processor (4 core) 2.6ghz
8 GB RAM 1333MHz
300GB C: drive (2X150 GB 10K RPM Raptors)
1.2TB D: drive (2X7,200 RPM 640GB WD's)
Burner is LG Super multi
secondary burner is Sony Commercial Blu-Ray burner
Video card is Saphire Build (Radeon 5450 PCI-E 16X)
Windows 7 X64 Pro
All Adobe is CS5 Production package.
If I'm leaving anything out, please let me know.
HELP! and Thanks. I'd really love to fix this without rebuilding the whole DVD. Take long time.
TEX

You really gain nothing by posting the same thing twice... http://forums.adobe.com/thread/971701

File 'pcprocbinding.cpp', line 1028, function 'PCDBTableCollection::FindOptimizedColumn'

The cube was compiling ok. I was using sql Server 2012 Standard.
I upgraded to Sql Server 2014 Standard.
Now when compiling the cube, without any changes, I get this error :
Internal error: An unexpected error occurred (file 'pcprocbinding.cpp', line 1028, function 'PCDBTableCollection::FindOptimizedColumn').
Errors in the OLAP storage engine: An error occurred while processing the 'Fact Inventaire Sem Past Year' partition of the 'Fait Inventaire Semaine' measure group for the 'Canac DM Ventes Produits Semaine' cube from the CanacDMVentesCondense database.

Hi Karlrw,
Glad to hear that your issue had been solved, thank you for your sharing.
Regards,
Charlie Liao
TechNet Community Support

Internal software error: .\PGCStreamInfo.cpp, line 1413

Im designing a DVD teaching project within Encore DVD 2.0.0.48678 from the Creative Suite 2 Production Premium software system. The project is very large and complex. As of now there are only 2 separate timelines. 1st time line has 50 chapters. 2nd time line is not finished but currently has 15 chapters. Because its a teaching DVD, there are also chapter play list created for each individual chapter. I also have a countless number of menus and links to sub menus and additional video links from the chapter play list. All of my links are set and operational with all functions in the individual menus working properly. This is an ongoing project for 3 months now, with perfect results prior to today. I have used the "preview from here" function with no problems to test the links and verify the menu structures with flawless results for the past 3 months. Today I was giving a demo of my progress, when I selected the "preview from here" I received this new error message, "internal software error: .\PGCStreamInfo.cpp. line 1413". I have checked and rechecked links, buttons, playlists, chapters, end actions, timelines, basically everything I could imagine and have even tried a computer restore point from 5 days back, at this time still have not resolved this issue.
AMD Athlon 64 3000+
2.01 GHz 1.00 GB of RAM
Microsoft Windows XP Home Edition Version 2002 SP2
Gigabyte GeForce 7300 GT videocard
Thanks for any suggestion, if more info is needed to solve this, i can provide it.

There are a couple of other threads about a similar error which seem to point to a possible chapter playlist problem:
Internal Software error ..... When 'preview from here' or Build
Chapter Playlist play order bug?

I have encountered the new error "Fatal internal error fpinit.cpp line 7398

I get the error message "Fatal internal error fpinit.cpp line 7398".
I use:
TestStand 2.0
LabView 7.1
Vision 7.1
uEye USb Camera
I've included into my TestStand programm some new steps that control the uEye USB Camera.
I use following steps (all steps written in LabView):
- Initialze Camera
- Wait
- Close Camera
- Wait
I have the settings "Load dynamically" in TestStand"
If I use also the setting "Unload after sequence executes" and start the sequence I get somtimes a LabView error after running the Step for the Camera initialization. LabView is sometimes immediatlly closed. This happen at leased after 10 turns/starts of the programm. If I use the loop functions "Loop on selected steps" it happen only sometimes at the first loop. The initialize Camera Step is every time pass, if TestStand try to run the next step I get a error.( Sometimes I get also the message ActiveX Server got lost)
I detected also that sometimes in this case a constant in a other vi is emty.
Normally I use the setting "Unload when sequence file is closed" then I have the problem only sometimes at the first turn.
If the initialize Camera step is succesfull I have no problem with further camera steps.
Regards
Alexander
Attachments:
lvlog02-18-10-09-34-10.txt ‏1 KB
Copy of Error.jpg ‏76 KB
Copy of Error2.jpg ‏42 KB

Hi Alex,
I'd suggest to replace all ctl. with new ones.
Perhaps one of them is corrupt.
You will find a documentation about preferred execution system
in the LabVIEW help. I also attached this files.
Regards
DianaS
Attachments:
help1.gif ‏37 KB
help2.gif ‏11 KB

Receive "Fatal Internal Error: Linker.cpp, line 1926 when run executable.

Hi, I use invoke node to call multiple subvi.vit, it work fine under .vi but when run under an executable I receive this error:
Fatal Internal Error: 'linker.cpp", line 1926
LabVIEW Version 7.0 You will lose any unsaved work. For more assistance in resolving this problem, please relaunch LabVIEW, or contact National Instruments.
Any suggestion will be very appreciated

Hi David,
What you are seeing is a known issue when calling LabVIEW 7.0 VITs from
an executable or DLL if the VITs include any Express VIs. It can happen if you
try to load
multiple instances of that template VI using VI Server.
There are a couple of workarounds for this issue:
Take
all the express VIs that are inside the template VI and turn them into
static subVIs. You can do this by right-clicking on the express VI and
selecting "Open Front Panel"; then save the express VI as a normal
subVI.
Build the entire application into a single executable, which will force all of the express VIs to get compiled as static subVIs.
Don't use the runtime engine at all and always run your application in development mode.
Let me know if the workarounds fix your issue, thanks.
Good luck!
- Philip Courtois, Thinkbot Solutions

Failure : "load.cpp", line 4081

My main front panel VI will no longer open and I just get the error, Failure : "load.cpp", line 4081.
I am running an Eval version of 6.0.1 and was deciding whether to buy this product for a new project.
Given that I see from this forum that this error has been known for 9 months plus and I've lost a weeks
work I am not so sure.
It occured after I added some tab controls to the front panel, so beware.

Hi RCT,
This error occurs in LV 6.0.1. It seems that it is fixed in LV 6.0.2 and LV 6.1.
One thing you can do is ask NI to delete the insane objects for you. You have to redo your work you have done since the time the VI was correct until it got corrupt.
The other thing you can do is use a copy from a backup and redo the rest of the work.
Waldemar
Waldemar
Using 7.1.1, 8.5.1, 8.6.1, 2009 on XP and RT
Don't forget to give Kudos to good answers and/or questions

Failure: "might.cpp" line 815 on LabVIEW executable

Hi,
I have a program written in LabVIEW 6.1 on a Windows XP platform. The program includes an ActiveX container that shows an Internet Explorer content window (just like the "Using the Microsoft Web Browser ActiveX Control" example found on http://sine.ni.com/apps/we/niepd_web_display.DISPLAY_EPD4?p_guid=B123AE0CB9BF111EE034080020E74861&p_node=DZ52051&p_submitted=N&p_rank=&p_answer=&p_source=External
, but without the activex queue in that example).
After I built the executable, I was able to run the exectuable on the development machine without problem. However when my client runs it on his PC with LabVIEW runtime engine 6.1 installed, he gets the message:
Failure: "might.cpp" line 815
For assistance in reso
lving this problem, please record the procedeing information and navigate to www.ni.com/failure or contact national insturments.
I cannot find any information on might.cpp on the NI support site. Any idea of what can be done to fix this problem?
Thanks!
Dan

Hi dan,
you must contact NI support sending them the problem. "might.cpp" is a source module of LV and they can investigate the error.
Another thing you have to take into account is that LV stores the class ID and not the application. Has the client PC the same MS IE version installed? If not, the error could also result from different versions of the Active-X control.
As with the reporting Toolkit for MS Office you have to build a different version of your app for each different version of the control.
Waldemar
Waldemar
Using 7.1.1, 8.5.1, 8.6.1, 2009 on XP and RT
Don't forget to give Kudos to good answers and/or questions

Winocc.cpp line 329 - using CWGraph in MFC OCX project

Similar Messages

Maybe you are looking for