Error: ticktime.cpp-207

I'm getting an error in Premiere Pro CS5.5. While my project is loading and the status bar at the bottom shows that a file GOPR0139.MP4 is loading a popup window opens saying Premiere Pro has encountered and error. [..\..\src\TickTime.cpp-207]. This file is in one of my project bins, however I have not placed it in the timeline yet. After I close the error window the program doesn't crash and I'm able to work on my project. Following this I'll frequently see in the status bar at the bottom an indicator bar saying Conforming GOPR0139.MP4 and GO010136.MP4. GO010136.MP4 IS in my timeline however as I said before GOPR0139.MP4 is NOT.
Anyone know why I am getting this error and how to fix it? I'm using Premiere Pro CS5.5 on a Windows 7 machine.
Thanks!

This error happens with almost every project I work on. My typical project is several sequences eventually all combined into one master sequence. Those individual sequences range from just regular edits of 50-100 clips with music and dissolves and a few color correction and stabilizer effects added to a few multicam sequences. I ran about 30 tests to see if I could narrow down what the cause is and I'm still stuck, although if you read this post until the end you'll find that maybe I'm onto something. NOTE: The above workaround of importing this troubled project into a new project did NOT work like it had in the past with this error.
As you know the error in the screenshot earlier in this post occurs when you re-open a project or try to export it to AME. When the error came up, I had to hit "continue" 384 times for the project to open! (Yes, I counted). The project then opened and I could work normally. But everytime I re-opened I'd have to hit continue the same number of times or more! (Now I have to hit continue 396 times for it to open!).
MY TESTING:
I imported individual sequences into a new project, one at a time, then saved and reopened the new project and the error did not pop up for most of them. BUT... I have one "Main" video sequence with about an hour of footage and 350 clips and several multicam sequences nested in it, and another "Highlight Video" sequence with about 125 clips of those clips and one nested multicam sequence. So I tried just importing only the highlight video sequence and now I only had to hit continue 20 times instead of 396 with the project that had the "main" video sequence. So I tested further.
1) I removed the 15 or so nested clips from this Highlight Video sequence that were pulled from a longer multicam sequence and the error went away.
So was it those specific clips?
2) Well I then re-synced those clips and made a new multicam sequence which I imported into the Highlight Video sequence and the issue was NOT there so I figured it wasn't the clips individually.
So was the fact that the original MC sequence was nested in this sequence?
3) Instead of NESTING the original sequence into this highlight video sequence, I copied and pasted the clips from the original multicam sequence into the Highlight Video Sequence the issue did NOT occur...BUT...
4) If I then took those copied clips and right-click and nested them the error did NOT occur...BUT as soon as I right clicked and ENABLED that nested video as a Multicam clip and saved the project, the error DID occur upon reopening. Same result..."...TickTtime.cpp-207" popus up and you have to hit continue 20 times upon opening and it opens.
Strange. Annoying. Frustrating.
So somehow the original multicam sequence is causing the issue right? If I started a new one with the same clips importing and right clicking and "Nest" the video and then right click and "enable multicam" it works fine with no error messages upon reopening. UNFORTUNATELY, I'm not usually opening and closing projects all the time so I don't know when this issue is occuring since it doesn't crash PP or anything.
So, not sure how the number of times I have to hit continue relates to all this. Obviously the bigger sequence has several nested multicam sequences and I have to hit continue 396 times so I don't know where that number is coming from. Its very frustrating and since the "workaround" above does NOT work this time, its a real pain in the ***.
Finally, I thought maybe its somehow the COMBINIATION of the added multicam sequence to the rest of the 125 or so clips that are in that Highlight Sequence. Why do I think this? Well...
Nesting the original multicam sequence into this Highlight Sequence caused me to have to hit "CONTINUE" 20 times upon reopening (once I had saved it and closed it out). Take away the nested MULTICAM sequence and it opens with NO errors. Hmm. Interesting. So I tested further...
5) I took away the 2nd half of the clips (about 50 or so) from the sequence and left in the original multicam sequence that caused the errors before (again, error occurs upon reopening a project) and by doing this the error DID occur BUT, I only had to hit CONTINUE 16 times now, not 20 like before.
6) So I instead deleted the first half of the clips (about 75 or so) and left the 2nd half of the clips as well as this original multicam sequence and guess what? NO ERRORS! Strange. So maybe it is the combination of clips and a nested multicam sequence. Like I said before, when I made a new multicam sequence with the same clips and nested it into this sequence the error did not occur, but taking the original fully edited multicam sequence and nesting that into this sequence the error DID occur...unless I deleted some of these clips. So I'm at a total loss. I guess I could continue and delete clips in smaller groups to try to identify which clips when combined with this multicam sequence are causing the error but I need a break. My mind is starting to unravel after doing so many tests.
Did any of this make sense? I tried to be as descriptive and thorough as possible in my troubleshooting to find what is causing this annoying error to occur.

Similar Messages

TickTime.cpp-207

Is there an update coming soon to fix the "TickTime.cpp-207" error in Premiere Pro 6.03 (Windows 7)? This happens when I use the warp stabilizer.

Right now, there is a lot of discussion about "CS Next" which may be named CS7 but I have not seen any discussion of further fixes for CS6
Only Adobe knows what is planned, and advance notice is rarely given in these forums... other than the public discussion of CS Next
NAB 2013 http://forums.adobe.com/thread/1184484
New Features http://forums.adobe.com/thread/1184788
http://prodesigntools.com/adobe-cs7-next-release-coming-out.html on May 6 ???
-BUT... this may be for the official annoucement, not physical availability

Projects Not Opening with Multicam and Warp Stabilizer - "[..\..\src\TickTime.cpp-207]"

Editing a sequence with multiple nested multicam clips and warp stabilizer, if I close Premiere and reopen it, it says "Premiere Pro has encountered an error. [..\..\src\TickTime.cpp-207]" repeatedly until killed by Task Manager. I have restarted the computer, cleared the media cache and deleted preferences. I can import the sequence into another project and continue editing but if I close PPro I have to create another project and import the sequence again or I get the same error. Help!

Hi Kevin!
That is great news. I had a feeling the issue would be gone in the Next PPro. The issue can be easily duplicated by following these steps in CS6:
1) User warp stabilizer on several clips (like maybe 6 or more or so).
2) Take two clips and nest them and sync them for multicam on the same timeline as the stabilized clips (NOTE: these two clips don't actually have to be sync'd...just grab any two clips, stack them on top of each other, highlight them both and right-click and choose "nest", then right-click again and "enable" multicam.
3) Save project. Close project. Re-open project and you'll get the error.
If you do that in the NEXT version, does the error come up? Also, just while I have you...if you go into the settings of Warp Stabilizer, what is the default "method"? Is it still defaulted to "Subspace Warp" or did they smarten up and realize the option "Position, Scale, Rotation" is actually MUCH more effeciet causing less wobble and less cropping of the video 90% of the time? Just curious.
Coltom Media Productions,
I feel your pain. What also stinks is that the error pops up again when you export (or I should say when you queue) up the project into AME. I originally thought the number of continues equalled the number of warps applied but that's not always the case. Although, the more warp stabilizers applied the more times you'll have to hit continue. It often goes in numbers divisible by four. Why do I know all this crazy, useless info...hours and hours of trying to "solve" the issue. Every project I do, every single week has more than 100 clips that are stabilized and multiple multicam sequences so I often have to hit "continue" on the error 300-400 times or more on EVERY project. Can't wait til the next version!
To see more on this issue you can see the original post on it here (note that the staff has recently (and graciously) led the charge to help isolate and resolve the issue):
http://forums.adobe.com/thread/956692?start=40&tstart=0
And then also, it definitely made my "Top 15 list" here:
http://forums.adobe.com/thread/1179004
Good luck!!!...oh, one more thing...the project will open...you just have to keep hitting continue. Sucks, but again, hopefully it'll be resolved soon.

Premiere Pro error TickTime.cpp-290

Hi, I have a serous problem with Premier Pro. This is the message:
Please, can somebody help me?
Thank you.
[Moved from the general Cloud forum to the specific Program forum... Mod]

look if this matches?
A guide to repair projects that get a "TickTime.cpp-290" error after opening a specific project.

Error ticktime.cpp-290

I'm having the "ticktime.cpp-290" error a lot, recently. I've tried using the repair executable that can be found here, on the forum, but it isn't solving my problem.
What should I do next?
OS: Windows 8.1 - CC 2014.2

You informations are very poor. What version of Premiere,what OS, what OS version, what footage do you use, when the error message appears.
Question over questions. But without these informations nobody can help.
Take a look here: https://forums.adobe.com/thread/1264170?tstart=0

Copy Paste of clips within a sequence closes the programm saying TickTime.cpp-290

Hello
I got the problem after a while when I want to copy and paste a clip or audiofile within a sequence the programm closes by saying Error TickTime.cpp-290.
It also happens when I open certian sequences.
All video/audiofiles are the same format.
I already used pp-repair.exe like in the forum but the problem isnt resolved. Importing the projectfile in a new project it tells me the same error.
Has anyone an idea?
Thanks

Hey,
Thanks for the answer.
Yes unfortunatly all values were correct and I had not to replace any comma by a full stop.
Do you have another idea?
regards

How to fix TickTime.cpp-288?

Premiere Pro CC, win 8 64 bit
Some itme I see this problem but some time when I open the project from auto-save and resave it I cannot open it and I cannot see the name of the error, there`s no end of the text line.
Any bode can help with that?

I have problem w this as well! TickTime.cpp-288
"Premiere Pro has encountered an error", "TickTime.cpp-288"
Then a Crash ...
It started with me not beeing able to open previous projekts.
win 7, 64-bit.
Frustrated.

Where is a link to the Premiere Pro CC 2014.1 (8.1) update? - Can I get help with the ticktime.cpp-290 error?

Ola to precisando do premiere versao 8.1 caravan consegue o link?
Message was edited by: Kevin Monahan
Reason: needed better title

Hi Kevin,
I posted about the same problem (TickTime.cpp-290 error) in another thread, but since you're asking here specific questions to resolve it, I'm answering it here.
Re: Debug Event: [...\ ...\src\TickTime.cpp-290]
What were you doing when this error started to occur?
          Nothing special I remember. The only thing I do recall, is:
          I was working with Premiere Pro (where the main project is), After Effects but rendering some PNG sequence, and Adobe Media Encoder. I sent from AE to AME a project to render. Configured 2 outputs (PNG & MP4). The same way I sent from PP a project to render and one error occured. Unfortunately I didn't write down the error, but it was like a path C://AME_64/something. But the AME queue updated and everything seemed OK. I close AME to be sure that the error wouldn't be the source of future error during rendering, and relaunched it. And at that time I couldn't open it. I got the error "Adobe Media Encoder has encountered an unexpected error and cannot continue". The only way I found to resolve this is to remove the directory /Users/%USERNAME%/My Documents/Adobe/Adobe Media Encoder/8.0/". The problem seems to appear when I save the queue. And since that time, Premiere do the TickTime.cpp-290 error.
          Another thing I noticed, don't know if it was there before, is, the AEP file in AME queue setttings displayed framerate as "25 / 29.97 / 30 / ...", a 2 digits number for the framerate. But suddenly (I thought first it was because of the Premiere Pro file being added to the queue, but no because it appended after without it), it was displayed as "25 000 / 29 970 / 30 000", a 5 digit number.
          After that, the TickTime.cpp-290 appeared. Sometimes when opening project, sometimes and resetting or changing the workspace (because it was messed up), sometimes when closing.
Do you have iCloud installed?
          No.
Is this a Premiere Pro CC 2014.0 or Premiere Pro CC 2014.1 project that was updated to Premiere Pro CC 2014.2? If so:
          It started long time ago a draft in CS6, but since I reopen the project, I saved new versions in Premiere Pro CC 2014.2 (not sure if I have other version like 2014.1 or 2014.0). Is there a way to know which 2014 version are my files? If I look into the XML I only saw Version="28"
Do you have a copy that can be opened in an earlier version?
              An old draft version in CS6. But that version has footage in different framerate and not all be interpreted at the timeline framerate.
Do you get the same error in that earlier version?
               No error here, the file opens properly.
              Additional info: I tried to open the 2014.2 file on another computer (where PP 2014.2 is installed) and same problem (this computer is on Win7 64-bit)
Did you use any unusual footage types in your project?
     I used MOV (Animation), MP4 (H264), and PNG sequence. The framerates of the footages are 24,25,30 and 60fps (but everything has been interpreted in 30fps)
If you remove them, do you still get an error?
              When I had the error, but not when I open the project file, I resave the file removing anything not interpreted in 30fps (because at that time I still had footage interpreted in their original framerate). I was able to work for some time, but now I can't open it anymore despite that.
Was the fps interpretation changed in any of the clips?
     Since the error appeared, and because I saw in another thread that it could be related to footage of different framerate, my timeline is now in 30fps and all the footage have been interpreted in 30fps. Footage are MP4, MOV, PNG sequence in 24, 25, 30 & 60fps.
If so, restore them to their original fps and see if you still get the error.
              Unfortunately, since I can't open the project anymore, I can't test that.
Did you use Warp Stabilizer?
          No.
Do you have any browser plug-ins?
          What do you call browser plug-in in Premiere?
Are there any third party plug-ins used?
          I have Magic Bullet Looks 2, and I'm using it on this project.
If so, remove the effect from those clips and see if it improves the situation.
              Unfortunately, since I can't open the project anymore, I can't test that.
Some additional infos on my computer.
I use Windows 8.1 (64-bit), all Adobe softwares installed have the last update (for video apps, it's 2014.2)
The language settings are configured in French, but Windows and CC apps are in English.
If needed the 2014.2 project file is here:
https://dl.dropboxusercontent.com/u/68413846/showreel19_30fps.prproj
Thanks in advance to help us to resolve this weird bug.
Christophe.

Premiere Pro Debug Event - Premiere Pro has enconuntered an error.[..\..\src\TickTime.cpp-290]

Ho salvato un progetto Premiere Pro CC (2.2014) tre volte successive con i nomi: telecinema1.prproj, telecinema2.prproj e telecinema3.prproj. Tutto ha funzionato regolarmente e per fortuna ho esportato tutti i file e anche alcuni _copiati con Project Manager.
Ad un certo punto però quando ho cercato di riaprire il n.3 mi è uscito il seguente avviso: Premiere Pro Debug Event - Premiere Pro has enconuntered an error.[..\..\src\TickTime.cpp-290] con relativo crash.
Non mi sono preoccupato e ho provato ad aprire il n. 2, ma anche questo e poi anche il n. 1 mi hanno dato lo stesso problema.
Ho riscontrato che si tratta di un errore ricorrente, ma non ho trovato nessuna segnalazione con TickTime.cpp-290.
Cosa faccio? Grazie

How to repair projects that get a "TickTime.cpp-290" error after opening a specific project.

How to repair projects that get a "TickTime.cpp-290" error after opening a specific project.

This is a guide to repair projects that get a "TickTime.cpp-290" error after opening a specific project.
Prerequisites:
Project repair tool (download link below)
WinRAR or any file archiver
Damaged project file
As an example, let's say the name of my damaged project is 'test.prproj'
Steps:
1. Download the project repair tool here: https://www.dropbox.com/s/3fyja0ws7l5gkbt/pp-repair-0.1.35.zip?dl=0
2. Rename your project file extension from 'test.prproj' to 'test.zip' (a warning appears saying the file might become unusable. Do not be concerned about the warning. Click OK and move to the next step.)
3. Extract the contents of 'test.zip' to a location on your computer. (Right click on the file and select ‘Extract files’ > Choose a location > Click OK).
4. Go to the extracted location. Note the file 'test' has no extension.
5. Rename the file, 'test.prproj'.
6. Launch the project repair tool, and then select the file 'test.prproj' (the one that we renamed in the last step).
7. Deselect all the check-boxes in the project repair tool.
8. Click the Repair button.
9. After a few seconds you see a message saying 'Success'.
10. Open the repaired file in Premiere Pro and then reset the workspace. Choose Window > Workspace > Reset Current Workspace.
11. Click the Save button to reduce the project size.
12. Your project is now repaired.
NOTE: If a file containing letters such as ã, å, ê, í, ú don’t repair, rename the file to something that doesn't contain these letters.

Hi Rameez,
first of all thanks a bunch for the tool - it saved our neck this morning on a tight deadline.
One minor note: I did get a message that the (already uncompressed + renamed) file is not uncompressed until I ran the tool as Administrator so you might want to add that to the FAQ entry...
Other than that I'm very much interested in what triggers this bug so we can potentially prevent it.
Background:
Specs: Windows 8.1, German locale (ie comma is decimal symbol), Premiere Pro CC 2014.2 installed in English
My colleague who ran into the TickTime.cpp-290 error remembers having created a new workspace while working on the project. That seems to have triggered the issue as we haven't had any trouble on other projects yet. It also got saved into the project file:
<MZ.Project.WorkspaceName>Bearbeitung</MZ.Project.WorkspaceName>
Any autosaves after he added the workspace were corrupted as well while the ones dating back to earlier still open fine.
I'd like to mention that Premiere did import previous (German language) workspaces - dating back until CS5. Not sure if that comes into play.
On the other hand, the debug log looks like there only is an issue with the decimal symbol:
10:08:06: Input: C:/temp/trouble/uncompressed/final.prproj
10:08:06: Path: C:/temp/trouble/uncompressed Basename: final Extension:prproj
10:08:06: 19852-> from: <PlaybackSpeed>0,069148936170212769</PlaybackSpeed>
10:08:06: 19852-> to: <PlaybackSpeed>0.069148936170212769</PlaybackSpeed>
10:08:06: 23970-> from: <PlaybackSpeed>0,0062741915889604422</PlaybackSpeed>
10:08:06: 23970-> to: <PlaybackSpeed>0.0062741915889604422</PlaybackSpeed>
I really need to make sure that this is no general problem with German locales as we have multiple users on this kind of config and can't afford projects breaking.
Or do we "just" need to watch out to get rid of the old workspaces? I'm a little puzzled to be honest.
Maybe it helps to mention that we are on CC Enterprise
Best regards,
Mike

Error Code: TickTime.cpp-376, -273

Hey,
So I'm currently on a Premiere job and our main project seems to be corrupt. The project was working and saved fine last night but this morning, the main project, the backup project, and the autosaved projects are all giving us the same error. The load-up bar gets to about 85% and then we get the "TickTime.cpp-376" error. I tried opening the editors main sequence in my project and when it times out, it then gives me a "TickTime.cpp-273" error. I've googled both errors but I'm not finding any solutions. Anyone have these problems before?
Specs:
Mac Pro running OSX 10.8.4
Premiere CC 7.0.1
Media is all Prores 4444 4:3
Thanks!
Will

Hi Will,
Have you used interpret footage on any of your clips in the project? This issue has popped up recenelty. The problem is Premiere is overriding the frame rate of a clip. If this is the cuase we have placed a fixed for the crash in our upcoming release.
It sounds like this came out of nowhere but if you can recall the last steps you did that lead to the project getting into this condition that would be helpful.
Would you mind uploading your project file with the offline media so I can take a look?
Thanks,
Peter Garaway
Adobe
Premiere Pro

Debug Event: [...\ ...\src\TickTime.cpp-290]

Hello,
I have meeting a problem for 24 hours on adobe first pro cc on 2014...
Debug Event: [...\ ...\src\TickTime.cpp-290] and adobe announces a grave error then he(it) closes.
I uninstalled everything and quite reinstalled, but the problem persists.
What's to be done to solve this problem which paralyzes all my work?

Hello,
I've got same problem here tonight. I'm working night & day since 1-2 weeks on After Effects & Premiere CC 2014.2 without any problems. Tonight I was queueing some renders in Media Encoder from After Effects & Premiere. When I 'exported to queue' from Premiere, I had an error (don't remember which one unfortunately), but AME was still open and seemed to be OK (also the Premiere render was listed, and I could change the output settings without any problem). To be sure the queue would render without problem I closed AME and try to reopen it... unsuccessfully. And since that time, I can't open it anymore
The error displayed is Adobe Media Encoder has encountered an unexpected error and cannot continue
And at the same (don't know if it's linked but high probability it is), when now I open a project in Premiere (not all the time), the workspace is totally messed up, and if I try to change to another or reset the one selected I got the same error you got, the
Debug Event: [...\ ...\src\TickTime.cpp-290]
and Premiere crashes
Sometimes the error occurs also when I open a project and it crashes with the same error (it doesn't seem "project-related" since sometimes it's OK, sometimes it's not).
I'm running CC 2014.2 versions on Windows 8.1 64-bits.
Nvidia Drivers 344.75 (not the last one, which is the 347.25, but I didn't install or uninstall anything before or after the problems).
I already had the workspace "messed up" problem one time, but it wasn't followed by a crash like now.
PS: Oh, I noticed around that time also a strange behavior from AME. My output framerate was in "30 fps", but after I queued my Premiere file, it was "30 000". I did not understand why the fps format change. Don't know if it's related.
Thank in advance,
Christophe.

How to fix TickTime.cpp-346?

Hey Guys ,
i have a Problem. Yesterday i had making a new Project and i have saved it . Today i would open the Project but i can not open it. It comes a Error
f:\mightysilt_win64\shared\adobe\mediacore\mediafoundation\api\inc\keyframe
and ..\..\src\TickTime.cpp-364
i hope you can help me .
Sorry for my english , i am from Germany

Malwarebytes ANTI-MALWARE totally solved this problem! Took abt 20 minutes to scan my whole computer, then fix and restart. Haven't had any problems after this (tried several projects that weren't OK from before).
Nice!
Hope this helps!
https://www.malwarebytes.org/

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

Error: ticktime.cpp-207

Similar Messages

Maybe you are looking for