Continuous Measurement and Logging LV2014
Hello,
I am examining the CML template which can be found in LabView 2014. It is very nice, I learn a lot just by playing with this template. However, due to the very minimal documentation (practically zero), some things are not clear why are there implemented?
1., In the UI Message Loop, the Case structure has a "Confirm Quit" case. As I see, this case never can get triggered, since the stop button is disabled during DAQ, why is it there? I guess for to give an example, if someone wants to enable the option shutting down the app during DAQ, without stopping the DAQ?
2., Since it is not explained in the documentation, could someone explain the behaviour of the enum type def in the UI Message Loop? I think I understand that, before stopping the DAQ, we have to be sure about first the DAQ is stopped. Second, all the data is logged, so the logging loop can be also stopped, and finally we can go to Idle state and "update status" message can be broadcasted. Am I right? Somehow it is still a bit "fuzzy" for me...
thanks for help!
Regards,
Solved!
Go to Solution.
crossrulz wrote:
I don't even put Stop buttons on my programs. Almost always, somebody who was not familiar with programming LabVIEW would use the 'X' to close the window. So when I discovered the Panel Close? event, I was overjoyed.
yep, actually the problem is not that the user uses the X or a "stop" button, but that, we let the user to be able to quit the application without first stopping the DAQ. Would not be just easier to fire a pop-up dialog, telling the user, "hey, first stop the DAQ before you quit!" ? So some state-check could be avoided in the UI Msg loop`s case structure...
2.: May I ask a CML related additional question? If I wish to extend the template with another DAQ loop, which has a different rate, or a loop which controls for example a flow controller, how would you do it nicely? Of course we create additional queues (notifiers too if we need graph plotting), etc. but how do you implement the state machine for this new loop? I think we need a separate enum typdef in the UI msg loop, since we need total decoupling between the DAQ and DAQ2 loops? Is that correct, or is there another way to do it? Maybe more compact if we create a cluster typedef, and we put the enumtypdef1 and enumtypdef2 in it, and we unbundle by name them only in the corresponding cases?
Similar Messages
-
Hi!
I have serious problems playing the video Developer Walkthrough of the Continuous Measurement and Logging Sample Project.
As the video pauses every few seconds for buffering. I am not able to watch it. Just wanted to check if you can playback the video:
http://zone.ni.com/wv/app/doc/p/id/wv-3401
This happens on any browser (chrome, ie, firefox). I am using Win XP and the latest Adobe Flash Player. About 2 weeks ago NI Germany confirmed the problem and promised to contact NI USA as they are responsible for these videos. So far nothing happened. In the meantime I received an e-mail that the problem could not be confirmed although they had confirmed it before...
Thank you for any feedback.
Regards,
AnguelHello ctVolFan,
As indicated in the "support" section of the SPOT, you should get in touch with self-paced-training(at)ni(dot)com. I don't believe that team monitors these forums directly.
Regards,
Tom L. -
Developer walkthrough fails on Continuous MEasurment and Logging
I am having problems watching these two videos:
Developer Walkthrough of the Continuous Measurement and Logging Sample Project
http://www.ni.com/video/2741/en/
Developer Walkthrough of the Continuous Measurement and Logging Sample Project
Queued Message Handler Template Documentation
http://www.ni.com/video/2728/en/
It gets stuck at the start saying Slide 1/1: Buffering.
I have downloaded the latest Adobe flash. A guy from NI support rang in response to my question to them and said that it worked on Chrome for him. I tried that and they don't work for me.
Can anyone help?OK, one update from my side:
On my machine (Win7, 64bit) it is working when running Firefox 29.
Using IE9, the link to the video seems to lead back to its page, no popup, nothing.
Point is, that my IE (since IE8) is obviously not 100% compatibel with Adobe Flash player. For instance, i have issues to play videos from YouTube on the machine using IE (error messages like Flash not installed or simply a blank screen instead of the video) but not for all videos there. With Firefox, i can view all videos from YouTube except the ones which are prohibited from YouTube due to national restrictions ("This video is forbidden in your country" or something like that).
So all in all, it seems to me that the issues you all observe are issues between the browsers and Flash, invalid settings for popup-blockers and specific "error handling" of specific browsers (which create the "loop-link-behavior").
Norbert
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it. -
How best to modify Continuous Measurement and Logging project
Hi,
I'm looking to log and aquire continuous data from some devices, and it looks like the Continuous Measurement and Logging project template is a great place to start... but I need to log/acquire from upwards of 20+ devices...
What's the best way to go about making this template more scalable?
ThanksYes the CM&L project template is a good framework to hang your code on .
(You find it with "Create Project" in 2012 and later versions)
The developer walk through is useful for the first time getting into the project.
With 20 devices I have to ask what kind of throughput are you talking about here?
Jeff -
Continuous Measurement and Logging Template - May hang-up due to lost Exit
The template Continuous Measurement and Logging in LabVIEW 2012SP1 has a flaw in the both the Acquisition and Logging loops.
The Stop message handler discards all messages in the message queue. The note says:
"Stop - Flush the queue of any pending "Log" messages. Close the TDMS file reference." See picture below.
This concept breaks if the Exit message is posted while the Stop message is being processed. The Critical time gap for this to happen is small because Exit is posted to the front of the queue. But it depends on the processing in the Stop handler case. Small or large - it can happen.
The symptom is that the application hangs in an infinite wait on the message queue - all controls are with no effect as the rest of the loops are terminated. Only Break will terminate the application. Pause button does not work either. (see this forum entry)
This problem may only appear after the application has become more complex and the timing has changed - the fresly made template works and does not reveal the issue.
The cure: First I thought of previewing the queue elements before discarding them selectively, one by one in the Stop loop, but that wont work either, because the Exit may arrive precicely in the time laps between preview and dequeue - remember Exits are posted to the front of the queue.
I think the best option is to replace the flush of the queue in the Stop message handlers with a Selectively dequeue of messages one by one and check each if Exit is found - if so, re-insert it into the front of the queue. All other messages are discared. This look like this, having the interesting parts visible...
Below is what the Stop message loop looks like with the problem highlighted.
Given that I am not mistaken, I think it is better that NI updates the templates to prevent this problem.
Solved!
Go to Solution.Here's what the idle state case within the stop message case looks like:
We don't hang the CPU handling a constant stream of no-op messages because we only enqueue "Log" messages when we are in the valid logging state (the Idle state here is again a passthrough).
The worst case scenario is that there are number of Log requests already in the queue when the system stops. Upon recieving the Stop message the state transitions to idle and the remaining Log messages become no-ops due to the state.
I will look into the feasibility of posting some updated VIs.
~Simon -
LabView 2012 Continuous Measurement and Logging (DAQmx) Project
I've been working with this example to try to build a DAQmx and Serial acquisition message handling loops, as well as another message handling loop with two analog outputs for control. This control would also be based off of information from the DAQmx acquistion loop. Is this example appropriate to do this with? I've added two additional message handling loops (Serial and the AO control loop). I worried that this example might not be the best to follow.
Attachments:
Main.vi 108 KBI'm not sure what example you are talking about but it seems like you are wanting something like the document below.
http://www.ni.com/white-paper/14119/en
Carl W.
Applications Engineering
National Instruments -
Continuously measure and write waveform using tdms
Hello everyone,
I am doing my thesis using Labview 2010(since it is only version avaliable in University currently ). I need to read and record data from microphone(currently using simulate signal since i need to make program work first) then save and analise it(didn't reach that point yet). I tried to use event structure so i can record and then read tdms file. But unfortunatly it records only small piece, then i inserted while loop so it will record continuosly but program doesnt respond after i push record and i can only close it manualy from toolbar. Please could anyone help me or suggest something since i am not very good at Labview and any feedback is welcome. Here is what i have done till now. I tried to search forums for some similar solution but could not find anything usefull(some had much newer version so i could not open). Thank you.
Solved!
Go to Solution.
Attachments:
test2.vi 45 KBHi and welcome to the forums,
The reason you cannot stop the recording of the waveform or exit the application is because you have the event case configured to "lock panel until the case for this event completes" (in edit events). This means that LabVIEW will not respond to user interaction until that event structure completes but because you rely on being able to press the while loop stop button to finish the event structure means you have a deadlock and have to abort the VI.
The architecture of your application is not ideal - I would strong advise against having anything that takes a long time to execute inside your event structure for the very reason above (obviously you can untick lock panel as a quick solution). I would suggest having a look at the producer/consumer design pattern (events) (new... > from template > frameworks) as this would be more appropriate for your application. You can handle your button presses in the top event structure and have a state machine in the bottom loop for starting, running and stopping your data acquisition.
The idea is that you only do very little inside the event structure so it frees up the front panel but the messages (e.g. start/stop acquiring data, exit application) are handled by another loop.
I don't know if it ships in LabVIEW 2010, but in 2012/2013 there are sample projects that include a "continuous measurement and logging" project which might be suited to your application. There are also examples for state machines and queued message handlers.
Certified LabVIEW Architect, Certified TestStand Developer
NI Days (and A&DF): 2010, 2011, 2013, 2014
NI Week: 2012, 2014
Knowledgeable in all things Giant Tetris and WebSockets -
How to measure and log frequency with fieldpoint CTR
Hi,
I am developing a data acquistion and control system for an engine dynamometer using the fieldpoint modules and Labview. One of the most important signals is the engine speed, measured in RPM. The RPM signal is a 0-12V pulse where one pulse equals one revolution of the engine. As well as being an important piece of data for later analysis, engine RPM will also be in the input into a PID controller, so the signal must be both accurate and have a high measurement frequency.
Currently I am using the FP-CTR500 modules to measure the frequency of the signal. I am already aware of the included frequency measurement VI example, as well as the one posted before for low frequency measurements, and I have gotten both to work with my setup. I would be using the low frequency VI becuase the max frequency measurement would be in the 200Hz range.
The first problem I am having is with the structure of the VI and how the data is output. The case structure in the VI activates when the counter is read and resets the counter, then switches to the next case. I would like the RPM number to output out of the case structure into a write_to_file VI and PID controller input. The problem is that when the case switches, the counter is reset to 0, which will be recorded in the written file.
This is some example output data (RPM):
1232
0
2321
0
2400
0
2521
0
The data is being written correctly, but of course I can't have 0 readings when the case structure changes. This would be especially problematic when input into a controller VI.
The next problem I am having is with sampling rate. If I were to use the low frequency measurement VI, the sampling rate of RPM would be variable based upon the the speed of the signal. Or, the original frequency measurement VI has an adjustable sampling rate. Of course, in my system there are a number of other signals that need to be recorded at the same time. I have found that as I am collecting data, the "write to file frequency" is entirely dependent on the read frequency of the frequency measurement. Therefore, if I had set the read frequency VI to read at 1 Hz, data will be recorded only every 2Hz. Ideally I would like an overall measurement frequency of all channels (mix of analog and digital) to read between 20-50Hz, but if I am limited by the frequency measurement.
Any ideas on how to solve this problem, either through Fieldpoint or Labview?
I can post my VI if this help.
Thanks,
HuangThanks for your reply.
I should probably describe my current setup before I go into anymore details with the problem. As for my specific setup, I am using an FP-1000 connected with an AIO600, AI110, CTR500, and TC120 all running through the RS232 line to a desktop running labview 8. The actual counter module is reading a tachometer signal output from a separate engine controller. THe output is a 0-12V ON 50% duty cycle signal. As for data logging, i am simply using a "write to measurement file" Express VI. I have a while structure which holds all of the express VIs which access the fieldpoint IO, and these are all routed to the "write to" VI.
As for the specifics of the data logging problem, as I said, when I set the count frequency of the "Fieldpoint Frequency Measurement" VI to 1Hz, (which means the VI calls the case structure at 2Hz), the "write to measurment file" VI is called at the same rate (2Hz). Which means that the overall logging rate of the VI is only 2Hz. Is there someway to decouple this?
I was able to solve the problem of calling the frequency variable from the case structure by using a local variable which is called outside the case structure.
And now I have been having a lot of problems with reading the actual frequency from my engine controller. THe actual signal will only range from 0 to around 200Hz. I noticed, by comparing the actual signal to what was being read in my labview program, that after around 80Hz the signal increases by around 1.5times more than the actual signal. ie. Actual signal = 100hz, Read Signal = 150Hz. After trying to figure out what was the problem, I decided to change the Noise Filter settings to 200Hz. It actually worked for all the frequency ranges up to around 150Hz but after that the filter attenuates the signal to the point where the actual signal is 160Hz, but is being read at 100Hz. My question is if there is a way to change the actual filter setting outside of the 2 given setpoints (200hz and 40khz) or if you have any other suggestions on how to fix this problem? I was thinking of creating a noise filter input in MAX so that i could play with the values in Labview, but am i only limited to those two filters?
Thanks again for your help,
Huang -
WLAN Detail Measurement and logging
Hello,
at an event with +150 WLAN clients should I create a report for WLAN usage over the event time..Network environment:
- WLC 5508 (7.2), AIR LAP1242G, access switches: 2960SCriteria for the report:
- How many wireless clients were generally in time connected / associated?
- How long each client was connected or active?
- What has caused traffic each client and all?
- When was which client on which AP is associated?
- How many clients were on the individual APs in each account?Dignity for Netflow (Prime as Collector) sufficient or do I need more?With which board means and how I can for example also in the controller LOG to see when which client was associated with which AP (to find no setting)?What tools can I help it still inserting. Ideas?
I already thank you for your feedback and professional helpBest regards
AlexanderHello,
sorry, bau at the moment i've found this dokument about Client Reporting with Prime:
http://www.cisco.com/en/US/docs/net_mgmt/prime/infrastructure/2.0/user/guide/reps.html#wp1059688
If someone still one more thing?
Many Thanks
Alexander -
I am looking at using the Continuous Measurement and Logging sample project as a starting point for my project. The template shows the use of a single data source at a single rate. In my case I have multiple data sources that will arrive at different rates and need to come together and be logged to the same file with the fastest arrival dictating the log entry and the slower data would be their last values. It is a slow data collecton process ranging from 1 second to around 10 second sample rate. More of a monitoring application with logging than a data aquisition application. Since the waveform data type is base-t plus delta-t and my data arrives at varying rates, my first task would be to remove the use of it and define a typedef for my data. I would use a single logging message loop, but what approach can anyone recommend for the aquisition? I imagine separate aquisition message loop vis for each data source but what about placement? Placing them all at the top level vs placing them within a the existing aquisition message loop vi? Any other thoughts or recommendation are appreciated. Thanks in advance!
if you want to sample one channel at 10/s and an other one at 1/second.... How is your file going to look like? Does this mean that for the slower channel you just want to keep the same value for the other 9 values?
The sampling speeds that you are talking about are really slow. It would certainly not hurt your hardware to sample eacht channel with the same speed. And it you really just need one sample every 10 second, you can always decimate you array of values.
For instance :
channel 1 : 1 point per second (sample ratio) => 10 points in 10 seconds
Channel 2 : 1 point per 10 seconds => 10 points per 10 seconds (same sample speed) => decimate array (keep 1+/10 values) => 1 point per 10 seconds
This is going to be the easy way, or you want to start with parallel loops running, but that's "not that simple" anymore
Kind regards,
- Bjorn -
Have fun using LabVIEW... and if you like my answer, please pay me back in Kudo's
LabVIEW 5.1 - LabVIEW 2012 -
My Macbook Pro keeps crashing and logging out frequently, continuously
My Macbook Pro early 2011, memory 4GB 1333 MHz DDR3, 2GHz intel Core i7, Mountain LIon 10.8.2
It keeps crashing and pushing me to "log-in" window. At first, it only happened mostly when I was using Google Chrome but then I removed Chrome and used Safari, it still happened and the times are more frequently.
I backed everything all up and reinstalled Mountain Lion and everything again. At the moment my Macbook Pro was upgraded the memory to 8GB of Corsair and it still crashed and loged me out. The Apple guy asked me to remove the 8GB memory and replace with the original one from Apple. I did and ir run smoothly for like 3 days and it happened AGAIN and since then it keeps crashing and logging out and hanging some softwares..
And today is the limit, my macbook Pro has kept crashing CONTINOUSLY and I had to restart and shut down like 5 times.
It is real annoying and affect to my works.
I just updated the latest from Apple (the java) today and I was wishing it would stop crashing but still.
The Crash Reports are most of WindowServer but today it is more: hidd and SecurityAgent and some softwares are hang like Skype, Adobe, iTune and VLC.
Please HELP.this is Chrome
Process: Google Chrome [11176]
Path: /Applications/Google Chrome.app/Contents/MacOS/Google Chrome
Identifier: com.google.Chrome
Version: 22.0.1229.92 (1229.92)
Code Type: X86 (Native)
Parent Process: launchd [133]
User ID: 501
Date/Time: 2012-10-19 00:46:02.691 +0700
OS Version: Mac OS X 10.8.2 (12C60)
Report Version: 10
Crashed Thread: 0 CrBrowserMain Dispatch queue: com.apple.main-thread
Exception Type: EXC_ARITHMETIC (SIGFPE)
Exception Codes: 0x0000000000000005, 0x00000000000080a8
Thread 0 Crashed:: CrBrowserMain Dispatch queue: com.apple.main-thread
0 com.apple.CoreFoundation 0x90cb3677 -[__NSArrayM insertObject:atIndex:] + 375
1 com.apple.CoreFoundation 0x90cb34f0 -[__NSArrayM addObject:] + 64
2 com.apple.CoreFoundation 0x90c7ae3b CFArrayAppendValue + 91
3 com.apple.CoreFoundation 0x90ca410b __CFRunLoopRun + 1643
4 com.apple.CoreFoundation 0x90ca363a CFRunLoopRunSpecific + 378
5 com.apple.CoreFoundation 0x90ca34ab CFRunLoopRunInMode + 123
6 com.apple.HIToolbox 0x95f2715a RunCurrentEventLoopInMode + 242
7 com.apple.HIToolbox 0x95f26ec9 ReceiveNextEventCommon + 374
8 com.apple.HIToolbox 0x95f26d44 BlockUntilNextEventMatchingListInMode + 88
9 com.apple.AppKit 0x93430a3a _DPSNextEvent + 724
10 com.apple.AppKit 0x9343026c -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 119
11 com.apple.AppKit 0x934266cc -[NSApplication run] + 855
12 com.google.Chrome.framework 0x00f49981 ChromeMain + 15008881
13 com.google.Chrome.framework 0x00f494bc ChromeMain + 15007660
14 com.google.Chrome.framework 0x00f75080 ChromeMain + 15186800
15 com.google.Chrome.framework 0x00f879c1 ChromeMain + 15262897
16 com.google.Chrome.framework 0x00f74dfa ChromeMain + 15186154
17 com.google.Chrome.framework 0x00930c59 ChromeMain + 8615753
18 com.google.Chrome.framework 0x00d2f01c ChromeMain + 12802828
19 com.google.Chrome.framework 0x00d2e71a ChromeMain + 12800522
20 com.google.Chrome.framework 0x00d2d486 ChromeMain + 12795766
21 com.google.Chrome.framework 0x00d2a947 ChromeMain + 12784695
22 com.google.Chrome.framework 0x00d2bdb1 ChromeMain + 12789921
23 com.google.Chrome.framework 0x003785fd ChromeMain + 2617581
24 com.google.Chrome.framework 0x003775c3 ChromeMain + 2613427
25 com.google.Chrome.framework 0x0036e79c ChromeMain + 2577036
26 com.google.Chrome.framework 0x00373bde ChromeMain + 2598606
27 com.google.Chrome.framework 0x0036dbad ChromeMain + 2573981
28 com.google.Chrome.framework 0x00eea36b ChromeMain + 14618203
29 com.google.Chrome.framework 0x00ee9610 ChromeMain + 14614784
30 com.google.Chrome.framework 0x000f9539 ChromeMain + 41
31 com.google.Chrome 0x000f3f78 main + 24
32 com.google.Chrome 0x000f3f55 0xf3000 + 3925
Thread 1:: Dispatch queue: com.apple.libdispatch-manager
0 libsystem_kernel.dylib 0x9404b9ae kevent + 10
1 libdispatch.dylib 0x94f1fc71 _dispatch_mgr_invoke + 993
2 libdispatch.dylib 0x94f1f7a9 _dispatch_mgr_thread + 53
Thread 2:
0 libsystem_kernel.dylib 0x9404b0ee __workq_kernreturn + 10
1 libsystem_c.dylib 0x9168304c _pthread_workq_return + 45
2 libsystem_c.dylib 0x91682e19 _pthread_wqthread + 448
3 libsystem_c.dylib 0x9166acca start_wqthread + 30
Thread 3:
0 libsystem_kernel.dylib 0x940487d2 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x94047cb0 mach_msg + 68
2 com.google.Chrome.framework 0x00f43430 ChromeMain + 14982944
3 libsystem_c.dylib 0x91680557 _pthread_start + 344
4 libsystem_c.dylib 0x9166acee thread_start + 34
Thread 4:: NetworkConfigWatcher
0 libsystem_kernel.dylib 0x940487d2 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x94047cb0 mach_msg + 68
2 com.apple.CoreFoundation 0x90c9e599 __CFRunLoopServiceMachPort + 185
3 com.apple.CoreFoundation 0x90ca3f7f __CFRunLoopRun + 1247
4 com.apple.CoreFoundation 0x90ca363a CFRunLoopRunSpecific + 378
5 com.apple.CoreFoundation 0x90ca34ab CFRunLoopRunInMode + 123
6 com.apple.Foundation 0x94b1a946 -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 278
7 com.google.Chrome.framework 0x00f497ef ChromeMain + 15008479
8 com.google.Chrome.framework 0x00f494bc ChromeMain + 15007660
9 com.google.Chrome.framework 0x00f75080 ChromeMain + 15186800
10 com.google.Chrome.framework 0x00f879c1 ChromeMain + 15262897
11 com.google.Chrome.framework 0x00f74dfa ChromeMain + 15186154
12 com.google.Chrome.framework 0x00f9b6a1 ChromeMain + 15344017
13 com.google.Chrome.framework 0x00f9b72b ChromeMain + 15344155
14 com.google.Chrome.framework 0x00f98419 ChromeMain + 15331081
15 libsystem_c.dylib 0x91680557 _pthread_start + 344
16 libsystem_c.dylib 0x9166acee thread_start + 34
Thread 5:: DnsWatcher
0 libsystem_kernel.dylib 0x9404b9ae kevent + 10
1 com.google.Chrome.framework 0x00faae6c ChromeMain + 15407452
2 com.google.Chrome.framework 0x00fa8b8c ChromeMain + 15398524
3 com.google.Chrome.framework 0x00f48a5f ChromeMain + 15005007
4 com.google.Chrome.framework 0x00f75080 ChromeMain + 15186800
5 com.google.Chrome.framework 0x00f879c1 ChromeMain + 15262897
6 com.google.Chrome.framework 0x00f74dfa ChromeMain + 15186154
7 com.google.Chrome.framework 0x00f9b6a1 ChromeMain + 15344017
8 com.google.Chrome.framework 0x00f9b72b ChromeMain + 15344155
9 com.google.Chrome.framework 0x00f98419 ChromeMain + 15331081
10 libsystem_c.dylib 0x91680557 _pthread_start + 344
11 libsystem_c.dylib 0x9166acee thread_start + 34
Thread 6:: AudioThread
0 libsystem_kernel.dylib 0x9404a8e2 __psynch_cvwait + 10
1 libsystem_c.dylib 0x91685220 _pthread_cond_wait + 833
2 libsystem_c.dylib 0x9170b0a1 pthread_cond_wait$UNIX2003 + 71
3 com.google.Chrome.framework 0x00f92638 ChromeMain + 15307048
4 com.google.Chrome.framework 0x00f92aeb ChromeMain + 15308251
5 com.google.Chrome.framework 0x00f929e6 ChromeMain + 15307990
6 com.google.Chrome.framework 0x00f7818c ChromeMain + 15199356
7 com.google.Chrome.framework 0x00f75080 ChromeMain + 15186800
8 com.google.Chrome.framework 0x00f879c1 ChromeMain + 15262897
9 com.google.Chrome.framework 0x00f74dfa ChromeMain + 15186154
10 com.google.Chrome.framework 0x00f9b6a1 ChromeMain + 15344017
11 com.google.Chrome.framework 0x00f9b72b ChromeMain + 15344155
12 com.google.Chrome.framework 0x00f98419 ChromeMain + 15331081
13 libsystem_c.dylib 0x91680557 _pthread_start + 344
14 libsystem_c.dylib 0x9166acee thread_start + 34
Thread 7:: CrShutdownDetector
0 libsystem_kernel.dylib 0x9404bdba __read + 10
1 com.google.Chrome.framework 0x00384196 ChromeMain + 2665606
2 com.google.Chrome.framework 0x00f98419 ChromeMain + 15331081
3 libsystem_c.dylib 0x91680557 _pthread_start + 344
4 libsystem_c.dylib 0x9166acee thread_start + 34
Thread 8:: Chrome_DBThread
0 libsystem_kernel.dylib 0x9404a8e2 __psynch_cvwait + 10
1 libsystem_c.dylib 0x91685220 _pthread_cond_wait + 833
2 libsystem_c.dylib 0x9170b0ec pthread_cond_timedwait$UNIX2003 + 70
3 com.google.Chrome.framework 0x00f92717 ChromeMain + 15307271
4 com.google.Chrome.framework 0x00f92b20 ChromeMain + 15308304
5 com.google.Chrome.framework 0x00f781c6 ChromeMain + 15199414
6 com.google.Chrome.framework 0x00f75080 ChromeMain + 15186800
7 com.google.Chrome.framework 0x00f879c1 ChromeMain + 15262897
8 com.google.Chrome.framework 0x00f74dfa ChromeMain + 15186154
9 com.google.Chrome.framework 0x00f9b6a1 ChromeMain + 15344017
10 com.google.Chrome.framework 0x00379c4f ChromeMain + 2623295
11 com.google.Chrome.framework 0x00f9b72b ChromeMain + 15344155
12 com.google.Chrome.framework 0x00f98419 ChromeMain + 15331081
13 libsystem_c.dylib 0x91680557 _pthread_start + 344
14 libsystem_c.dylib 0x9166acee thread_start + 34
Thread 9:: Chrome_WebKitThread
0 libsystem_kernel.dylib 0x9404a8e2 __psynch_cvwait + 10
1 libsystem_c.dylib 0x91685220 _pthread_cond_wait + 833
2 libsystem_c.dylib 0x9170b0a1 pthread_cond_wait$UNIX2003 + 71
3 com.google.Chrome.framework 0x00f92638 ChromeMain + 15307048
4 com.google.Chrome.framework 0x00f92aeb ChromeMain + 15308251
5 com.google.Chrome.framework 0x00f929e6 ChromeMain + 15307990
6 com.google.Chrome.framework 0x00f7818c ChromeMain + 15199356
7 com.google.Chrome.framework 0x00f75080 ChromeMain + 15186800
8 com.google.Chrome.framework 0x00f879c1 ChromeMain + 15262897
9 com.google.Chrome.framework 0x00f74dfa ChromeMain + 15186154
10 com.google.Chrome.framework 0x00f9b6a1 ChromeMain + 15344017
11 com.google.Chrome.framework 0x00379c7f ChromeMain + 2623343
12 com.google.Chrome.framework 0x00f9b72b ChromeMain + 15344155
13 com.google.Chrome.framework 0x00f98419 ChromeMain + 15331081
14 libsystem_c.dylib 0x91680557 _pthread_start + 344
15 libsystem_c.dylib 0x9166acee thread_start + 34
Thread 10:: Chrome_FileThread
0 libsystem_kernel.dylib 0x9404b9ae kevent + 10
1 com.google.Chrome.framework 0x00faae6c ChromeMain + 15407452
2 com.google.Chrome.framework 0x00fa8b8c ChromeMain + 15398524
3 com.google.Chrome.framework 0x00f48b23 ChromeMain + 15005203
4 com.google.Chrome.framework 0x00f75080 ChromeMain + 15186800
5 com.google.Chrome.framework 0x00f879c1 ChromeMain + 15262897
6 com.google.Chrome.framework 0x00f74dfa ChromeMain + 15186154
7 com.google.Chrome.framework 0x00f9b6a1 ChromeMain + 15344017
8 com.google.Chrome.framework 0x00379caf ChromeMain + 2623391
9 com.google.Chrome.framework 0x00f9b72b ChromeMain + 15344155
10 com.google.Chrome.framework 0x00f98419 ChromeMain + 15331081
11 libsystem_c.dylib 0x91680557 _pthread_start + 344
12 libsystem_c.dylib 0x9166acee thread_start + 34
Thread 11:: Chrome_FileUserBlockingThread
0 libsystem_kernel.dylib 0x9404a8e2 __psynch_cvwait + 10
1 libsystem_c.dylib 0x91685220 _pthread_cond_wait + 833
2 libsystem_c.dylib 0x9170b0a1 pthread_cond_wait$UNIX2003 + 71
3 com.google.Chrome.framework 0x00f92638 ChromeMain + 15307048
4 com.google.Chrome.framework 0x00f92aeb ChromeMain + 15308251
5 com.google.Chrome.framework 0x00f929e6 ChromeMain + 15307990
6 com.google.Chrome.framework 0x00f7818c ChromeMain + 15199356
7 com.google.Chrome.framework 0x00f75080 ChromeMain + 15186800
8 com.google.Chrome.framework 0x00f879c1 ChromeMain + 15262897
9 com.google.Chrome.framework 0x00f74dfa ChromeMain + 15186154
10 com.google.Chrome.framework 0x00f9b6a1 ChromeMain + 15344017
11 com.google.Chrome.framework 0x00379cdf ChromeMain + 2623439
12 com.google.Chrome.framework 0x00f9b72b ChromeMain + 15344155
13 com.google.Chrome.framework 0x00f98419 ChromeMain + 15331081
14 libsystem_c.dylib 0x91680557 _pthread_start + 344
15 libsystem_c.dylib 0x9166acee thread_start + 34
Thread 12:: Chrome_ProcessLauncherThread
0 libsystem_kernel.dylib 0x9404a8e2 __psynch_cvwait + 10
1 libsystem_c.dylib 0x91685220 _pthread_cond_wait + 833
2 libsystem_c.dylib 0x9170b0a1 pthread_cond_wait$UNIX2003 + 71
3 com.google.Chrome.framework 0x00f92638 ChromeMain + 15307048
4 com.google.Chrome.framework 0x00f92aeb ChromeMain + 15308251
5 com.google.Chrome.framework 0x00f929e6 ChromeMain + 15307990
6 com.google.Chrome.framework 0x00f7818c ChromeMain + 15199356
7 com.google.Chrome.framework 0x00f75080 ChromeMain + 15186800
8 com.google.Chrome.framework 0x00f879c1 ChromeMain + 15262897
9 com.google.Chrome.framework 0x00f74dfa ChromeMain + 15186154
10 com.google.Chrome.framework 0x00f9b6a1 ChromeMain + 15344017
11 com.google.Chrome.framework 0x00379d0f ChromeMain + 2623487
12 com.google.Chrome.framework 0x00f9b72b ChromeMain + 15344155
13 com.google.Chrome.framework 0x00f98419 ChromeMain + 15331081
14 libsystem_c.dylib 0x91680557 _pthread_start + 344
15 libsystem_c.dylib 0x9166acee thread_start + 34
Thread 13:: Chrome_CacheThread
0 libsystem_kernel.dylib 0x9404b9ae kevent + 10
1 com.google.Chrome.framework 0x00faae6c ChromeMain + 15407452
2 com.google.Chrome.framework 0x00fa8b8c ChromeMain + 15398524
3 com.google.Chrome.framework 0x00f48b23 ChromeMain + 15005203
4 com.google.Chrome.framework 0x00f75080 ChromeMain + 15186800
5 com.google.Chrome.framework 0x00f879c1 ChromeMain + 15262897
6 com.google.Chrome.framework 0x00f74dfa ChromeMain + 15186154
7 com.google.Chrome.framework 0x00f9b6a1 ChromeMain + 15344017
8 com.google.Chrome.framework 0x00379d3f ChromeMain + 2623535
9 com.google.Chrome.framework 0x00f9b72b ChromeMain + 15344155
10 com.google.Chrome.framework 0x00f98419 ChromeMain + 15331081
11 libsystem_c.dylib 0x91680557 _pthread_start + 344
12 libsystem_c.dylib 0x9166acee thread_start + 34
Thread 14:: Chrome_IOThread
0 libsystem_kernel.dylib 0x9404b9ae kevent + 10
1 com.google.Chrome.framework 0x00faae6c ChromeMain + 15407452
2 com.google.Chrome.framework 0x00fa8b8c ChromeMain + 15398524
3 com.google.Chrome.framework 0x00f48b23 ChromeMain + 15005203
4 com.google.Chrome.framework 0x00f75080 ChromeMain + 15186800
5 com.google.Chrome.framework 0x00f879c1 ChromeMain + 15262897
6 com.google.Chrome.framework 0x00f74dfa ChromeMain + 15186154
7 com.google.Chrome.framework 0x00f9b6a1 ChromeMain + 15344017
8 com.google.Chrome.framework 0x00379d6f ChromeMain + 2623583
9 com.google.Chrome.framework 0x00f9b72b ChromeMain + 15344155
10 com.google.Chrome.framework 0x00f98419 ChromeMain + 15331081
11 libsystem_c.dylib 0x91680557 _pthread_start + 344
12 libsystem_c.dylib 0x9166acee thread_start + 34
Thread 15:: WorkerPool/-1339895808
0 libsystem_kernel.dylib 0x9404a8e2 __psynch_cvwait + 10
1 libsystem_c.dylib 0x91685220 _pthread_cond_wait + 833
2 libsystem_c.dylib 0x9170b0ec pthread_cond_timedwait$UNIX2003 + 70
3 com.google.Chrome.framework 0x00f92717 ChromeMain + 15307271
4 com.google.Chrome.framework 0x00f9c70d ChromeMain + 15348221
5 com.google.Chrome.framework 0x00f9cba1 ChromeMain + 15349393
6 com.google.Chrome.framework 0x00f98419 ChromeMain + 15331081
7 libsystem_c.dylib 0x91680557 _pthread_start + 344
8 libsystem_c.dylib 0x9166acee thread_start + 34
Thread 16:: WorkerPool/-1339756544
0 libsystem_kernel.dylib 0x9404a8e2 __psynch_cvwait + 10
1 libsystem_c.dylib 0x91685220 _pthread_cond_wait + 833
2 libsystem_c.dylib 0x9170b0ec pthread_cond_timedwait$UNIX2003 + 70
3 com.google.Chrome.framework 0x00f92717 ChromeMain + 15307271
4 com.google.Chrome.framework 0x00f9c70d ChromeMain + 15348221
5 com.google.Chrome.framework 0x00f9cba1 ChromeMain + 15349393
6 com.google.Chrome.framework 0x00f98419 ChromeMain + 15331081
7 libsystem_c.dylib 0x91680557 _pthread_start + 344
8 libsystem_c.dylib 0x9166acee thread_start + 34
Thread 17:: WorkerPool/-1339617280
0 libsystem_kernel.dylib 0x9404a8e2 __psynch_cvwait + 10
1 libsystem_c.dylib 0x91685220 _pthread_cond_wait + 833
2 libsystem_c.dylib 0x9170b0ec pthread_cond_timedwait$UNIX2003 + 70
3 com.google.Chrome.framework 0x00f92717 ChromeMain + 15307271
4 com.google.Chrome.framework 0x00f9c70d ChromeMain + 15348221
5 com.google.Chrome.framework 0x00f9cba1 ChromeMain + 15349393
6 com.google.Chrome.framework 0x00f98419 ChromeMain + 15331081
7 libsystem_c.dylib 0x91680557 _pthread_start + 344
8 libsystem_c.dylib 0x9166acee thread_start + 34
Thread 18:: NetworkConfigWatcher
0 libsystem_kernel.dylib 0x940487d2 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x94047cb0 mach_msg + 68
2 com.apple.CoreFoundation 0x90c9e599 __CFRunLoopServiceMachPort + 185
3 com.apple.CoreFoundation 0x90ca3f7f __CFRunLoopRun + 1247
4 com.apple.CoreFoundation 0x90ca363a CFRunLoopRunSpecific + 378
5 com.apple.CoreFoundation 0x90ca34ab CFRunLoopRunInMode + 123
6 com.apple.Foundation 0x94b1a946 -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 278
7 com.google.Chrome.framework 0x00f497ef ChromeMain + 15008479
8 com.google.Chrome.framework 0x00f494bc ChromeMain + 15007660
9 com.google.Chrome.framework 0x00f75080 ChromeMain + 15186800
10 com.google.Chrome.framework 0x00f879c1 ChromeMain + 15262897
11 com.google.Chrome.framework 0x00f74dfa ChromeMain + 15186154
12 com.google.Chrome.framework 0x00f9b6a1 ChromeMain + 15344017
13 com.google.Chrome.framework 0x00f9b72b ChromeMain + 15344155
14 com.google.Chrome.framework 0x00f98419 ChromeMain + 15331081
15 libsystem_c.dylib 0x91680557 _pthread_start + 344
16 libsystem_c.dylib 0x9166acee thread_start + 34
Thread 19:: BrowserWatchdog
0 libsystem_kernel.dylib 0x9404a8e2 __psynch_cvwait + 10
1 libsystem_c.dylib 0x91685220 _pthread_cond_wait + 833
2 libsystem_c.dylib 0x9170b0ec pthread_cond_timedwait$UNIX2003 + 70
3 com.google.Chrome.framework 0x00f92717 ChromeMain + 15307271
4 com.google.Chrome.framework 0x00f92b20 ChromeMain + 15308304
5 com.google.Chrome.framework 0x00f781c6 ChromeMain + 15199414
6 com.google.Chrome.framework 0x00f75080 ChromeMain + 15186800
7 com.google.Chrome.framework 0x00f879c1 ChromeMain + 15262897
8 com.google.Chrome.framework 0x00f74dfa ChromeMain + 15186154
9 com.google.Chrome.framework 0x00f9b6a1 ChromeMain + 15344017
10 com.google.Chrome.framework 0x00f9b72b ChromeMain + 15344155
11 com.google.Chrome.framework 0x00f98419 ChromeMain + 15331081
12 libsystem_c.dylib 0x91680557 _pthread_start + 344
13 libsystem_c.dylib 0x9166acee thread_start + 34
Thread 20:: Chrome_SafeBrowsingThread
0 libsystem_kernel.dylib 0x9404a8e2 __psynch_cvwait + 10
1 libsystem_c.dylib 0x91685220 _pthread_cond_wait + 833
2 libsystem_c.dylib 0x9170b0a1 pthread_cond_wait$UNIX2003 + 71
3 com.google.Chrome.framework 0x00f92638 ChromeMain + 15307048
4 com.google.Chrome.framework 0x00f92aeb ChromeMain + 15308251
5 com.google.Chrome.framework 0x00f929e6 ChromeMain + 15307990
6 com.google.Chrome.framework 0x00f7818c ChromeMain + 15199356
7 com.google.Chrome.framework 0x00f75080 ChromeMain + 15186800
8 com.google.Chrome.framework 0x00f879c1 ChromeMain + 15262897
9 com.google.Chrome.framework 0x00f74dfa ChromeMain + 15186154
10 com.google.Chrome.framework 0x00f9b6a1 ChromeMain + 15344017
11 com.google.Chrome.framework 0x00f9b72b ChromeMain + 15344155
12 com.google.Chrome.framework 0x00f98419 ChromeMain + 15331081
13 libsystem_c.dylib 0x91680557 _pthread_start + 344
14 libsystem_c.dylib 0x9166acee thread_start + 34
Thread 21:: NetworkConfigWatcher
0 libsystem_kernel.dylib 0x940487d2 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x94047cb0 mach_msg + 68
2 com.apple.CoreFoundation 0x90c9e599 __CFRunLoopServiceMachPort + 185
3 com.apple.CoreFoundation 0x90ca3f7f __CFRunLoopRun + 1247
4 com.apple.CoreFoundation 0x90ca363a CFRunLoopRunSpecific + 378
5 com.apple.CoreFoundation 0x90ca34ab CFRunLoopRunInMode + 123
6 com.apple.Foundation 0x94b1a946 -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 278
7 com.google.Chrome.framework 0x00f497ef ChromeMain + 15008479
8 com.google.Chrome.framework 0x00f494bc ChromeMain + 15007660
9 com.google.Chrome.framework 0x00f75080 ChromeMain + 15186800
10 com.google.Chrome.framework 0x00f879c1 ChromeMain + 15262897
11 com.google.Chrome.framework 0x00f74dfa ChromeMain + 15186154
12 com.google.Chrome.framework 0x00f9b6a1 ChromeMain + 15344017
13 com.google.Chrome.framework 0x00f9b72b ChromeMain + 15344155
14 com.google.Chrome.framework 0x00f98419 ChromeMain + 15331081
15 libsystem_c.dylib 0x91680557 _pthread_start + 344
16 libsystem_c.dylib 0x9166acee thread_start + 34
Thread 22:: BrowserBlockingWorker1/-1213034496
0 libsystem_kernel.dylib 0x9404a8e2 __psynch_cvwait + 10
1 libsystem_c.dylib 0x91685220 _pthread_cond_wait + 833
2 libsystem_c.dylib 0x9170b0a1 pthread_cond_wait$UNIX2003 + 71
3 com.google.Chrome.framework 0x00f92638 ChromeMain + 15307048
4 com.google.Chrome.framework 0x00f9925f ChromeMain + 15334735
5 com.google.Chrome.framework 0x00f9897d ChromeMain + 15332461
6 com.google.Chrome.framework 0x00f9aeed ChromeMain + 15342045
7 com.google.Chrome.framework 0x00f98419 ChromeMain + 15331081
8 libsystem_c.dylib 0x91680557 _pthread_start + 344
9 libsystem_c.dylib 0x9166acee thread_start + 34
Thread 23:: Chrome_HistoryThread
0 libsystem_kernel.dylib 0x9404a8e2 __psynch_cvwait + 10
1 libsystem_c.dylib 0x91685220 _pthread_cond_wait + 833
2 libsystem_c.dylib 0x9170b0ec pthread_cond_timedwait$UNIX2003 + 70
3 com.google.Chrome.framework 0x00f92717 ChromeMain + 15307271
4 com.google.Chrome.framework 0x00f92b20 ChromeMain + 15308304
5 com.google.Chrome.framework 0x00f781c6 ChromeMain + 15199414
6 com.google.Chrome.framework 0x00f75080 ChromeMain + 15186800
7 com.google.Chrome.framework 0x00f879c1 ChromeMain + 15262897
8 com.google.Chrome.framework 0x00f74dfa ChromeMain + 15186154
9 com.google.Chrome.framework 0x00f9b6a1 ChromeMain + 15344017
10 com.google.Chrome.framework 0x00f9b72b ChromeMain + 15344155
11 com.google.Chrome.framework 0x00f98419 ChromeMain + 15331081
12 libsystem_c.dylib 0x91680557 _pthread_start + 344
13 libsystem_c.dylib 0x9166acee thread_start + 34
Thread 24:: Chrome_SyncThread
0 libsystem_kernel.dylib 0x9404a8e2 __psynch_cvwait + 10
1 libsystem_c.dylib 0x91685220 _pthread_cond_wait + 833
2 libsystem_c.dylib 0x9170b0ec pthread_cond_timedwait$UNIX2003 + 70
3 com.google.Chrome.framework 0x00f92717 ChromeMain + 15307271
4 com.google.Chrome.framework 0x00f92b20 ChromeMain + 15308304
5 com.google.Chrome.framework 0x00f781c6 ChromeMain + 15199414
6 com.google.Chrome.framework 0x00f75080 ChromeMain + 15186800
7 com.google.Chrome.framework 0x00f879c1 ChromeMain + 15262897
8 com.google.Chrome.framework 0x00f74dfa ChromeMain + 15186154
9 com.google.Chrome.framework 0x00f9b6a1 ChromeMain + 15344017
10 com.google.Chrome.framework 0x00f9b72b ChromeMain + 15344155
11 com.google.Chrome.framework 0x00f98419 ChromeMain + 15331081
12 libsystem_c.dylib 0x91680557 _pthread_start + 344
13 libsystem_c.dylib 0x9166acee thread_start + 34
Thread 25:: Chrome_PasswordStore_Thread
0 libsystem_kernel.dylib 0x9404a8e2 __psynch_cvwait + 10
1 libsystem_c.dylib 0x91685220 _pthread_cond_wait + 833
2 libsystem_c.dylib 0x9170b0a1 pthread_cond_wait$UNIX2003 + 71
3 com.google.Chrome.framework 0x00f92638 ChromeMain + 15307048
4 com.google.Chrome.framework 0x00f92aeb ChromeMain + 15308251
5 com.google.Chrome.framework 0x00f929e6 ChromeMain + 15307990
6 com.google.Chrome.framework 0x00f7818c ChromeMain + 15199356
7 com.google.Chrome.framework 0x00f75080 ChromeMain + 15186800
8 com.google.Chrome.framework 0x00f879c1 ChromeMain + 15262897
9 com.google.Chrome.framework 0x00f74dfa ChromeMain + 15186154
10 com.google.Chrome.framework 0x00f9b6a1 ChromeMain + 15344017
11 com.google.Chrome.framework 0x00f9b72b ChromeMain + 15344155
12 com.google.Chrome.framework 0x00f98419 ChromeMain + 15331081
13 libsystem_c.dylib 0x91680557 _pthread_start + 344
14 libsystem_c.dylib 0x9166acee thread_start + 34
Thread 26:
0 libsystem_kernel.dylib 0x940487d2 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x94047cb0 mach_msg + 68
2 com.google.Chrome.framework 0x00f732cf ChromeMain + 15179199
3 com.google.Chrome.framework 0x004563c2 ChromeMain + 3526322
4 com.google.Chrome.framework 0x00f98419 ChromeMain + 15331081
5 libsystem_c.dylib 0x91680557 _pthread_start + 344
6 libsystem_c.dylib 0x9166acee thread_start + 34
Thread 27:
0 libsystem_kernel.dylib 0x9404b0ee __workq_kernreturn + 10
1 libsystem_c.dylib 0x9168304c _pthread_workq_return + 45
2 libsystem_c.dylib 0x91682e19 _pthread_wqthread + 448
3 libsystem_c.dylib 0x9166acca start_wqthread + 30
Thread 28:
0 libsystem_kernel.dylib 0x9404b0ee __workq_kernreturn + 10
1 libsystem_c.dylib 0x9168304c _pthread_workq_return + 45
2 libsystem_c.dylib 0x91682e19 _pthread_wqthread + 448
3 libsystem_c.dylib 0x9166acca start_wqthread + 30
Thread 29:
0 libsystem_kernel.dylib 0x9404b0ee __workq_kernreturn + 10
1 libsystem_c.dylib 0x9168304c _pthread_workq_return + 45
2 libsystem_c.dylib 0x91682e19 _pthread_wqthread + 448
3 libsystem_c.dylib 0x9166acca start_wqthread + 30
Thread 30:
0 libsystem_kernel.dylib 0x9404b0ee __workq_kernreturn + 10
1 libsystem_c.dylib 0x9168304c _pthread_workq_return + 45
2 libsystem_c.dylib 0x91682e19 _pthread_wqthread + 448
3 libsystem_c.dylib 0x9166acca start_wqthread + 30
Thread 31:
0 libsystem_kernel.dylib 0x9404b0ee __workq_kernreturn + 10
1 libsystem_c.dylib 0x9168304c _pthread_workq_return + 45
2 libsystem_c.dylib 0x91682e19 _pthread_wqthread + 448
3 libsystem_c.dylib 0x9166acca start_wqthread + 30
Thread 32:
0 libsystem_kernel.dylib 0x9404b0ee __workq_kernreturn + 10
1 libsystem_c.dylib 0x9168304c _pthread_workq_return + 45
2 libsystem_c.dylib 0x91682e19 _pthread_wqthread + 448
3 libsystem_c.dylib 0x9166acca start_wqthread + 30
Thread 33:
0 libsystem_kernel.dylib 0x9404b0ee __workq_kernreturn + 10
1 libsystem_c.dylib 0x9168304c _pthread_workq_return + 45
2 libsystem_c.dylib 0x91682e19 _pthread_wqthread + 448
3 libsystem_c.dylib 0x9166acca start_wqthread + 30
Thread 0 crashed with X86 Thread State (32-bit):
eax: 0x00000000 ebx: 0x00000000 ecx: 0x00000001 edx: 0x00000000
edi: 0x7e334790 esi: 0x90cb350e ebp: 0xbff0b408 esp: 0xbff0b3c0
ss: 0x00000023 efl: 0x00010297 eip: 0x90cb3677 cs: 0x0000001b
ds: 0x00000023 es: 0x00000023 fs: 0x00000000 gs: 0x0000000f
cr2: 0xd06c6000
Logical CPU: 0
Binary Images:
0xf3000 - 0xf3ff7 +com.google.Chrome (22.0.1229.92 - 1229.92) <4D32963C-C84D-3408-7F61-474C6140989E> /Applications/Google Chrome.app/Contents/MacOS/Google Chrome
0xf7000 - 0x39b3fcb +com.google.Chrome.framework (22.0.1229.92 - 1229.92) <785A62BD-1F08-1E54-0E83-382D5626175B> /Applications/Google Chrome.app/Contents/Versions/22.0.1229.92/Google Chrome Framework.framework/Google Chrome Framework
0x50d1000 - 0x50deff3 com.apple.Librarian (1.1 - 1) <88A55A5E-40FF-3234-8394-2317120B79AB> /System/Library/PrivateFrameworks/Librarian.framework/Versions/A/Librarian
0x52bb000 - 0x52caff7 +com.google.Keystone.Registration (1.1.0 - 1.1.0.3659) <2379CBDF-65AB-246D-D5F4-3A450D457F42> /Applications/Google Chrome.app/Contents/Versions/22.0.1229.92/Google Chrome Framework.framework/Frameworks/KeystoneRegistration.framework/KeystoneRegistrat ion
0xae23000 - 0xae2bffc libcldcpuengine.dylib (2.1.19) <E5429AB3-FE28-3C0C-8942-686BB4191A9E> /System/Library/Frameworks/OpenCL.framework/Libraries/libcldcpuengine.dylib
0xae32000 - 0xae34fff libCoreFSCache.dylib (24.4) <A089ED2E-0156-3937-BE32-5BED76DF4066> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCoreFSCache .dylib
0xae3b000 - 0xae3bff7 +cl_kernels (???) <6B51C2B5-73C1-4B39-8035-CAB9D8B2F6C8> cl_kernels
0xae52000 - 0xaee4ff7 unorm8_bgra.dylib (2.1.19) <A2C66114-F581-3D86-9BC9-9994156640AF> /System/Library/Frameworks/OpenCL.framework/Libraries/ImageFormats/unorm8_bgra. dylib
0xaf06000 - 0xaf07ffd +cl_kernels (???) <5EB19A55-B553-4083-BFB1-18B80E1CED57> cl_kernels
0x8fef2000 - 0x8ff24e57 dyld (210.2.3) <23516BE4-29BE-350C-91C9-F36E7999F0F1> /usr/lib/dyld
0x90007000 - 0x90036ff7 com.apple.securityinterface (6.0 - 55024.4) <7C5E28DC-F8BE-3238-883F-E1646A2AF895> /System/Library/Frameworks/SecurityInterface.framework/Versions/A/SecurityInter face
0x90037000 - 0x90085ff3 com.apple.SystemConfiguration (1.12.2 - 1.12.2) <7BA6C58B-0357-356F-BB69-17ACB5E35988> /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfi guration
0x90090000 - 0x9009afff com.apple.speech.recognition.framework (4.1.5 - 4.1.5) <B855E8B4-2EE3-3BFF-8547-98A0F084F9AF> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SpeechRecogni tion.framework/Versions/A/SpeechRecognition
0x9009b000 - 0x90133fff com.apple.CoreServices.OSServices (557.4 - 557.4) <C724AB29-A596-3E1E-9FF1-A4E509AD843A> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServi ces.framework/Versions/A/OSServices
0x90134000 - 0x9013efff libsystem_notify.dylib (98.5) <7EEE9475-18F8-3099-B0ED-23A3E528ABE0> /usr/lib/system/libsystem_notify.dylib
0x9016e000 - 0x9021dff7 com.apple.CoreText (260.0 - 275.16) <873ADCD9-D361-3753-A220-CDD289196AD8> /System/Library/Frameworks/CoreText.framework/Versions/A/CoreText
0x9024f000 - 0x9035cff3 com.apple.ImageIO.framework (3.2.0 - 845) <BF959BCB-C30A-3680-B7C2-91B327B2B63B> /System/Library/Frameworks/ImageIO.framework/Versions/A/ImageIO
0x9035d000 - 0x9035effd com.apple.TrustEvaluationAgent (2.0 - 23) <E42347C0-2D3C-36A4-9200-757FFA61B388> /System/Library/PrivateFrameworks/TrustEvaluationAgent.framework/Versions/A/Tru stEvaluationAgent
0x9035f000 - 0x903a8ff7 com.apple.framework.CoreWLAN (3.0.1 - 301.11) <ABA6A926-34C2-3C09-AD9F-A87A8A35536A> /System/Library/Frameworks/CoreWLAN.framework/Versions/A/CoreWLAN
0x90c26000 - 0x90c6bff7 com.apple.NavigationServices (3.7 - 200) <F6531764-6E43-3AF3-ACDD-8A5551EF016A> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/NavigationSer vices.framework/Versions/A/NavigationServices
0x90c6c000 - 0x90e54ff3 com.apple.CoreFoundation (6.8 - 744.12) <E939CEA0-493C-3233-9983-5070981BB350> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
0x90e55000 - 0x90efffff com.apple.LaunchServices (539.7 - 539.7) <AF33EBD3-BC0B-30B5-B7DA-5CCCF12D7EDD> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchS ervices.framework/Versions/A/LaunchServices
0x90f00000 - 0x91018ff7 com.apple.coreavchd (5.6.0 - 5600.4.16) <F024C78B-4FAA-38F1-A182-AD0A0A596CBE> /System/Library/PrivateFrameworks/CoreAVCHD.framework/Versions/A/CoreAVCHD
0x91019000 - 0x91081fe7 libvDSP.dylib (380.6) <55780308-4DCA-3B10-9703-EAFC3E13A3FA> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/libvDSP.dylib
0x91082000 - 0x9110afff com.apple.PDFKit (2.7.2 - 2.7.2) <7AE7BAE9-4C21-3BFB-919E-5C6EEBBDFF75> /System/Library/Frameworks/Quartz.framework/Versions/A/Frameworks/PDFKit.framew ork/Versions/A/PDFKit
0x9110b000 - 0x91128fff libCRFSuite.dylib (33) <C9D72D0C-871A-39A2-8AFB-682D11AE7D0D> /usr/lib/libCRFSuite.dylib
0x91129000 - 0x911c0ff7 com.apple.ink.framework (10.8.2 - 150) <D90FF7BC-6B90-39F1-AC52-670269947C58> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Ink.framework /Versions/A/Ink
0x911c1000 - 0x911c3fff com.apple.securityhi (4.0 - 55002) <62E3AE75-61CB-341E-B2A0-CFC985A2BF7F> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SecurityHI.fr amework/Versions/A/SecurityHI
0x911c4000 - 0x91256ffb libvMisc.dylib (380.6) <6DA3A03F-20BE-300D-A664-B50A7B4E4B1A> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/libvMisc.dylib
0x91257000 - 0x9160fffa libLAPACK.dylib (1073.4) <9A6E5EAD-F2F2-3D5C-B655-2B536DB477F2> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/libLAPACK.dylib
0x91610000 - 0x91667ff7 com.apple.ScalableUserInterface (1.0 - 1) <2B5E454B-BC49-3E85-B54D-1950397C448C> /System/Library/Frameworks/QuartzCore.framework/Versions/A/Frameworks/ScalableU serInterface.framework/Versions/A/ScalableUserInterface
0x9166a000 - 0x91727feb libsystem_c.dylib (825.25) <B1F6916A-F558-38B5-A18C-D9733625FDC9> /usr/lib/system/libsystem_c.dylib
0x91728000 - 0x91a2dff7 com.apple.CoreServices.CarbonCore (1037.3 - 1037.3) <4571EDDC-704A-3FB1-B9A6-59870AA6165F> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonC ore.framework/Versions/A/CarbonCore
0x91a2e000 - 0x91a2efff libSystem.B.dylib (169.3) <81C58EAB-0E76-3EAB-BDFD-C5A6FE95536F> /usr/lib/libSystem.B.dylib
0x92776000 - 0x92892ff7 com.apple.desktopservices (1.7.2 - 1.7.2) <8E74D101-8398-34F1-A463-B4950680A597> /System/Library/PrivateFrameworks/DesktopServicesPriv.framework/Versions/A/Desk topServicesPriv
0x92893000 - 0x928a1fff com.apple.opengl (1.8.6 - 1.8.6) <1AD1AE7B-B57B-35B5-B571-32A34F0DA737> /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL
0x928a2000 - 0x928c7ff7 com.apple.CoreVideo (1.8 - 99.3) <5B872AC0-E82D-3475-A3F9-FD95F380560D> /System/Library/Frameworks/CoreVideo.framework/Versions/A/CoreVideo
0x928c8000 - 0x928ffffa com.apple.LDAPFramework (2.4.28 - 194.5) <8368FAE7-2B89-3A7D-B6EE-7184B522CB66> /System/Library/Frameworks/LDAP.framework/Versions/A/LDAP
0x92900000 - 0x92942ff7 libauto.dylib (185.1) <B2B5B639-6778-352A-828D-FD8B64A3E8B3> /usr/lib/libauto.dylib
0x92943000 - 0x92970ffe libsystem_m.dylib (3022.6) <9975D9C3-3B71-38E3-AA21-C5C5F9D9C431> /usr/lib/system/libsystem_m.dylib
0x92971000 - 0x92990ff3 com.apple.Ubiquity (1.2 - 243.10) <D2C9F356-1681-31D2-B292-5227E2DDEB0B> /System/Library/PrivateFrameworks/Ubiquity.framework/Versions/A/Ubiquity
0x92991000 - 0x92accff7 libBLAS.dylib (1073.4) <FF74A147-05E1-37C4-BC10-7DEB57FE5326> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/libBLAS.dylib
0x92acd000 - 0x92acdfff com.apple.vecLib (3.8 - vecLib 3.8) <83160DD1-5614-3E34-80EB-97041016EF1F> /System/Library/Frameworks/vecLib.framework/Versions/A/vecLib
0x92ace000 - 0x92c8affd libicucore.A.dylib (491.11.1) <B19E450A-BAF1-3967-9C95-7F77DC0B4639> /usr/lib/libicucore.A.dylib
0x92c8b000 - 0x92cadfff libc++abi.dylib (24.4) <06479DA4-BC23-34B6-BAFC-A885814261D0> /usr/lib/libc++abi.dylib
0x92cae000 - 0x92d0bfff com.apple.audio.CoreAudio (4.1.0 - 4.1.0) <9549B81F-4425-34EE-802B-F462068DC0C5> /System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio
0x92d4c000 - 0x92fc8ff7 com.apple.QuickTime (7.7.1 - 2599.13) <FE609160-E1EF-341D-9B6A-205D3E03A4D2> /System/Library/Frameworks/QuickTime.framework/Versions/A/QuickTime
0x92fc9000 - 0x92ff5ff7 libsystem_info.dylib (406.17) <AA5611DB-A944-3072-B6BE-ACAB08689547> /usr/lib/system/libsystem_info.dylib
0x92ff8000 - 0x93048ff7 com.apple.CoreMediaIO (301.0 - 4147) <F13FA9D4-BD1D-3297-BDD5-5858B231D738> /System/Library/Frameworks/CoreMediaIO.framework/Versions/A/CoreMediaIO
0x93049000 - 0x9304afff libDiagnosticMessagesClient.dylib (8) <39B3D25A-148A-3936-B800-0D393A00E64F> /usr/lib/libDiagnosticMessagesClient.dylib
0x9304b000 - 0x9306ffff libJPEG.dylib (845) <547FA9A5-0BBB-3E39-BACA-F3E2DAE57DB0> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libJPEG.dylib
0x93070000 - 0x930beffb libFontRegistry.dylib (100) <3B8350C2-4D8F-38C4-A22E-2F855D7E83D1> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ATS.framework/Versions/A/Resources/libFontRegistry.dylib
0x930bf000 - 0x93127ff7 com.apple.framework.IOKit (2.0 - 755.18.10) <9A80E97E-544F-3A45-916D-6DB7ED217E33> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
0x931fc000 - 0x931ffff7 libcompiler_rt.dylib (30) <CE5DBDB4-0124-3E2B-9105-989DF98DD108> /usr/lib/system/libcompiler_rt.dylib
0x93200000 - 0x93217fff com.apple.GenerationalStorage (1.1 - 132.2) <93694E0D-35D3-3633-976E-F354CBD92F54> /System/Library/PrivateFrameworks/GenerationalStorage.framework/Versions/A/Gene rationalStorage
0x93218000 - 0x9327cff3 libstdc++.6.dylib (56) <F8FA490A-8F3C-3645-ABF5-78926CE9C62C> /usr/lib/libstdc++.6.dylib
0x9327d000 - 0x932beff7 libcups.2.dylib (327) <F46F8703-FEAE-3442-87CB-45C8BF98BEE5> /usr/lib/libcups.2.dylib
0x932cd000 - 0x93e89ffb com.apple.AppKit (6.8 - 1187.34) <06EDB1D1-3B8A-3699-8E3A-D8F50A27AB7C> /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit
0x93e8a000 - 0x93e8eff7 libmacho.dylib (829) <5280A013-4F74-3F74-BE0C-7F612C49F1DC> /usr/lib/system/libmacho.dylib
0x93e8f000 - 0x93ee6ff3 com.apple.HIServices (1.20 - 417) <561A770B-8523-3D09-A763-11F872779A4C> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ HIServices.framework/Versions/A/HIServices
0x93ee7000 - 0x93ef0ff3 com.apple.DisplayServicesFW (2.6.1 - 353) <50D0BBF0-F911-380F-B470-E59B5E48E520> /System/Library/PrivateFrameworks/DisplayServices.framework/Versions/A/DisplayS ervices
0x93f17000 - 0x93f20ffe com.apple.aps.framework (3.0 - 3.0) <09D5F4F3-03FD-3077-A51D-B368F18ED1D4> /System/Library/PrivateFrameworks/ApplePushService.framework/Versions/A/ApplePu shService
0x93f21000 - 0x93f2efff libGL.dylib (8.6.1) <C7A3917A-C444-33CC-8599-BB9CD8C12BC4> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGL.dylib
0x93f2f000 - 0x93f33fff com.apple.CommonPanels (1.2.5 - 94) <6B3E7E53-7708-3DA2-8C50-59C2B4735DE1> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/CommonPanels. framework/Versions/A/CommonPanels
0x93f34000 - 0x93f8dfff com.apple.QuickLookFramework (4.0 - 555.4) <96911441-FDD4-3B68-9E0C-51BA11A97C2E> /System/Library/Frameworks/QuickLook.framework/Versions/A/QuickLook
0x93fe6000 - 0x93feaffe libcache.dylib (57) <834FDCA7-FE3B-33CC-A12A-E11E202477EC> /usr/lib/system/libcache.dylib
0x93ff0000 - 0x93ff8fff com.apple.CommerceCore (1.0 - 26) <AF0D1990-8CBF-3AB4-99DF-8B7AE14FB0D5> /System/Library/PrivateFrameworks/CommerceKit.framework/Versions/A/Frameworks/C ommerceCore.framework/Versions/A/CommerceCore
0x93ff9000 - 0x93ff9fff libsystem_blocks.dylib (59) <3A743C5D-CFA5-37D8-80A8-B6795A9DB04F> /usr/lib/system/libsystem_blocks.dylib
0x93ffa000 - 0x94035fe7 libGLImage.dylib (8.6.1) <A3442557-18D5-332E-8859-423D5A20EBBE> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLImage.dyl ib
0x94036000 - 0x94050ffc libsystem_kernel.dylib (2050.18.24) <C17D49D0-7961-3B67-B443-C788C6E5AA76> /usr/lib/system/libsystem_kernel.dylib
0x94051000 - 0x9405cffb com.apple.DirectoryService.Framework (10.8 - 151.10) <234F4A14-60ED-300B-93B2-D5052878558F> /System/Library/Frameworks/DirectoryService.framework/Versions/A/DirectoryServi ce
0x9405d000 - 0x94060fff com.apple.help (1.3.2 - 42) <AD7EB1F0-A068-3A2C-9D59-38E59CEC0D96> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Help.framewor k/Versions/A/Help
0x94061000 - 0x9406ffff libxar.1.dylib (105) <343E4A3B-1D04-34A3-94C2-8C7C9A8F736B> /usr/lib/libxar.1.dylib
0x94070000 - 0x940b5ff5 com.apple.opencl (2.1.20 - 2.1.20) <41C4AE6E-67B6-33E2-A9B6-BF6F01580B16> /System/Library/Frameworks/OpenCL.framework/Versions/A/OpenCL
0x940b6000 - 0x940e3ffb com.apple.CoreServicesInternal (154.2 - 154.2) <DCCF604B-1DB8-3F09-8122-545E2E7F466D> /System/Library/PrivateFrameworks/CoreServicesInternal.framework/Versions/A/Cor eServicesInternal
0x940e4000 - 0x9410eff9 com.apple.framework.Apple80211 (8.0.1 - 801.17) <8A8BBBFD-496B-35A6-A26E-ADF8D672D908> /System/Library/PrivateFrameworks/Apple80211.framework/Versions/A/Apple80211
0x9415b000 - 0x94169ff7 libz.1.dylib (43) <245F1B61-2276-3BBB-9891-99934116D833> /usr/lib/libz.1.dylib
0x9416a000 - 0x941c3ff7 com.apple.ImageCaptureCore (5.0.1 - 5.0.1) <541529F7-063E-370B-9EB2-DF5BE39073E6> /System/Library/Frameworks/ImageCaptureCore.framework/Versions/A/ImageCaptureCo re
0x941c4000 - 0x94606fff com.apple.CoreGraphics (1.600.0 - 324.6) <66556166-F9A7-3EEC-A562-46061C7A79E4> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreGraphics.framework/Versions/A/CoreGraphics
0x94607000 - 0x94613ff8 libbz2.1.0.dylib (29) <7031A4C0-784A-3EAA-93DF-EA1F26CC9264> /usr/lib/libbz2.1.0.dylib
0x94614000 - 0x9461dffd com.apple.audio.SoundManager (4.0 - 4.0) <ABC5FE40-B222-36EB-9905-5C8C4BFD8C87> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/CarbonSound.f ramework/Versions/A/CarbonSound
0x9461e000 - 0x94a1afeb com.apple.VideoToolbox (1.0 - 926.62) <B09EEF06-CB3C-3EAA-8B0E-22A1801F3CAE> /System/Library/Frameworks/VideoToolbox.framework/Versions/A/VideoToolbox
0x94a1b000 - 0x94a1cfff liblangid.dylib (116) <E13CC8C5-5034-320A-A210-41A2BDE4F846> /usr/lib/liblangid.dylib
0x94a1d000 - 0x94a1dfff com.apple.CoreServices (57 - 57) <956C6C6D-A5DD-314F-9C57-4A61D41F30CE> /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices
0x94a1e000 - 0x94a22fff com.apple.OpenDirectory (10.8 - 151.10) <A1858D81-086F-3BF5-87E3-9B70409FFDF6> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/OpenDirectory
0x94a23000 - 0x94a72ff6 libTIFF.dylib (845) <989A2EB9-3A49-3157-8E9C-B16E6005BC64> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libTIFF.dylib
0x94a73000 - 0x94a76ff9 libCGXType.A.dylib (324.6) <3004616B-51F6-3B9D-8B85-DCCA3DF9BC10> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreGraphics.framework/Versions/A/Resources/libCGXType.A.dylib
0x94a77000 - 0x94d94ff3 com.apple.Foundation (6.8 - 945.11) <03B242AC-519C-3683-AA52-E73536B3D55F> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
0x94d95000 - 0x94dbaffb com.apple.framework.familycontrols (4.1 - 410) <5A8504E7-D95D-3101-8E20-38EADE8DEAE1> /System/Library/PrivateFrameworks/FamilyControls.framework/Versions/A/FamilyCon trols
0x94dbb000 - 0x94e30ff7 com.apple.ApplicationServices.ATS (332 - 341.1) <95206704-F9C9-33C4-AF25-FE9890E160B2> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ATS.framework/Versions/A/ATS
0x94e31000 - 0x94e71fff com.apple.MediaKit (13 - 659) <37B8C1E3-B67D-3FE6-8A14-7FFD9F31C556> /System/Library/PrivateFrameworks/MediaKit.framework/Versions/A/MediaKit
0x94e72000 - 0x94e73fff libdnsinfo.dylib (453.18) <41C7B8E2-2A81-31DE-BD8B-F0C29E169D4F> /usr/lib/system/libdnsinfo.dylib
0x94f1b000 - 0x94f2dff7 libdispatch.dylib (228.23) <86EF7D45-2D97-3465-A449-95038AE5DABA> /usr/lib/system/libdispatch.dylib
0x94f2e000 - 0x94f6dff7 com.apple.bom (12.0 - 192) <0637E52C-D151-37B3-904F-8656B2FD44DD> /System/Library/PrivateFrameworks/Bom.framework/Versions/A/Bom
0x94f6e000 - 0x94f6ffff libquarantine.dylib (52) <D526310F-DC77-37EA-8F5F-83928EFA3262> /usr/lib/system/libquarantine.dylib
0x94f70000 - 0x94fa6ffb com.apple.DebugSymbols (98 - 98) <9A9ADA0A-E487-3C8F-9998-286EE04C235A> /System/Library/PrivateFrameworks/DebugSymbols.framework/Versions/A/DebugSymbol s
0x94fa7000 - 0x950a5ff7 libFontParser.dylib (84.5) <B3006327-7B2D-3966-A56A-BD85F1D71641> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ATS.framework/Versions/A/Resources/libFontParser.dylib
0x950a6000 - 0x950bbfff com.apple.speech.synthesis.framework (4.1.12 - 4.1.12) <DE68CEB5-4959-3652-83B8-D2B00D3B932D> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ SpeechSynthesis.framework/Versions/A/SpeechSynthesis
0x950bc000 - 0x950befff libCVMSPluginSupport.dylib (8.6.1) <8A174BD9-992E-351D-8F9A-DF6991723ABE> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCVMSPluginS upport.dylib
0x950bf000 - 0x950c2ff7 com.apple.TCC (1.0 - 1) <437D76CD-6437-3B55-BE2C-A53508858256> /System/Library/PrivateFrameworks/TCC.framework/Versions/A/TCC
0x950c3000 - 0x9513fff3 com.apple.Metadata (10.7.0 - 707.3) <6B6A6216-23D0-34CE-8099-BEE9BA42501E> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadat a.framework/Versions/A/Metadata
0x95140000 - 0x9514cff7 com.apple.NetAuth (4.0 - 4.0) <4983C4B8-9D95-3C4D-897E-07743326487E> /System/Library/PrivateFrameworks/NetAuth.framework/Versions/A/NetAuth
0x9514d000 - 0x9529affb com.apple.CFNetwork (596.2.3 - 596.2.3) <1221EF86-659B-3136-AB57-0CC6B130CDA2> /System/Library/Frameworks/CFNetwork.framework/Versions/A/CFNetwork
0x9529b000 - 0x956b8fff FaceCoreLight (2.4.1) <571DE3F8-CA8A-3E71-9AF4-F06FFE721CE6> /System/Library/PrivateFrameworks/FaceCoreLight.framework/Versions/A/FaceCoreLi ght
0x956b9000 - 0x95952ff3 com.apple.AddressBook.framework (7.1 - 1167) <AF7B18F2-D0FF-33AA-9CE9-4106B1CDAE1D> /System/Library/Frameworks/AddressBook.framework/Versions/A/AddressBook
0x95959000 - 0x9595affd libunc.dylib (25) <58599CBF-E262-3CEA-AFE1-35560E0177DC> /usr/lib/system/libunc.dylib
0x9595b000 - 0x95b72fff com.apple.CoreData (106.1 - 407.7) <17FD06D6-AD7C-345A-8FA4-1F0FBFF4DAE1> /System/Library/Frameworks/CoreData.framework/Versions/A/CoreData
0x95b73000 - 0x95b79fff com.apple.print.framework.Print (8.0 - 258) <12AEAD24-69 -
Changing from finite to continuous samples and vice versa?
Hello,
I have a problem which I'm trying to overcome: I have a measurement system consisting of an analog output and reading two analog inputs. I would like to run it continiously to monitor the current values (without saving the previous data), however, when I click something like a record button, I'd like to start a recording of a predefined period (like a finite samples measurement) and then restarting the monitoring without saving again.
Currently my measurement program is based on the examples "Continuous AO" and AI vis, and are made with continuous sample mode and while loops. How can I insert a record button?
I tried putting event handlers in the measurement loop, however it suspended the loop from running.
I attach a screenshot of my current measurement loop. (With the shift register I tried to read data, however I cannot get it out of the loop, until the loop is stopped)
Thank you in advance
Engage! using LV2012
Attachments:
question.png 81 KBI have tried adopting something similar, however it doesn't work the way it should. (Or at least the way I think it should) Could you please help me ironing it out? I've seen some vis on the internet with queue-controlled (but only one-way) and tried adopting them.
The MainProgram vi is the app, with some settings (now limited to a signal file selection and channel settings). Then the data acquisition can be started by clicking the Start Acq button.
And here come my problems: first sometimes the queue starts, sometimes it doesn't (or at least it doesn't start the data acquisition). And the main point: I set the sample rate, yet it is acquired at a much-much slower rate (my signal has a period time of 4 seconds, yet it needs at least 20 seconds to get near finishing). And the strangest: sometimes, mostly after some time (about 1-2 min) it hangs and does nothing with the daq (yet labview seems responsive, just my program hangs somewhere).
So now only the controlled acquisition is in the problem and first I don't care about forwarding the data for analysis and saving. (That seems to be the smaller problem).
What am I doing wrong? Thanks for your help.
I attach all the files. (MainProgram is the app itself, MY.SIGNAL is the signal file I want to output.) I use a USB-6211 device. (at work a physical one, at home a simulated one).
Engage! using LV2012
Attachments:
queued_daq.zip 366 KB -
Hi can anybody help or advise me? I've recently bought the i-phone 4s, I've set up my apple I.D and password but everytime I try and log in it says "this apple I.D has not yet been used on the i-tunes store" I click "review" follow the instructions and agree to the terms and condition's, enter my bank details but it declines every time? I've tried both my accounts and its declined both, this stops me from logging in so I can't download anything for free or buy anything, my sister had the option of skipping the bank details part when she created her apple I.D and just enters her's when buying something, why do I not have that option?? And why is it declining my bank details...please HELP!!!!!
The details I'm entering are correct, I choose visa as my card type, enter my card number, enter my expiry date and my last 3 digts on the reverse of the card, enter my address and zip code plus my home telephone number, click continue and it says "the payment method you have selected has been declined, please enter another payment method". I've lost count how many times I've tried, I've typed my details in slowly making sure I put them in properlly and it still declines it, I've even tried makeing a new apple I.D and when I get to the bank details part it declines it again so I am forced to press cancel and all details are not saved so its just like I'm hitting a brick wall, its ******* me off!!! I can't even download any of the free app's because to do so you must log in but when I do it says "this apple I.D has not yet been used in the i-tunes store" review my details and can't get past the bank details part. So doesn't log me in, I'm honestly out of ideas
-
Hello,
I am currently working with two instruments; an Agilent E3646A and an NI 6212 BNC. My objective is to have the 6212 to be continuously taking measurements according to predefined parameters while the E3646A's parameters can be continuously updated. This simple instrument combination is intended to help me learn the necessarry achitecture; continuous measurement, dynamic output control, and more instruments will be added in the future.
I've previously posted on a similar, but more complicated, setup (http://forums.ni.com/t5/Instrument-Control-GPIB-Serial/Split-second-lag-when-controlling-two-instrum... and was advised to try the Producer Consumer Architecture. I've found relevant literature on the site (http://www.ni.com/white-paper/3023/en/, https://decibel.ni.com/content/docs/DOC-2431), searched the forums and constructed my own VI. While my first attempt at a Producer Consumer Architecture has resolved some of the issues I was having when I first posted on the subject, however, new issues have arisen with regard to reading and stopping the VI.
I am currently able to run the VI and update the device parameters. Previously, I would get a freeze while the instrument was being updated and could not toggle parameters until it was done. This has been resolved although the read only updates when a parameter has been updated although it is outside of the event structure. Furthermore the Stop button does not work in any context. I've also gotten occasional errors regarding the Deqeue Element but the bulk of the trouble is Error -200279 "Attempted to read samples that are no longer available" at DAQmx Read. I realize that there is a problem in my Producer Loop but haven't been able to figure out how to resolve it.
This is my first attempt at a Producer Consumer Architecture and already I can see that it is a powerful tool. I read as much as I could and looked at the relevant examples but expected to have some issues in the beginning. Would really appreciate any advice so I can take full advantage of the architecture.
Hope to hear from you,
Yusif Nurizade
Solved!
Go to Solution.
Attachments:
DCe3646A_DAQ6212_Prod_Con_4_13a_2014.vi 89 KBJon,
Thank you for the response and the suggestions.
I created the Local Variable for the Stop Button and moved the original into its own Event Case. It is now able to stop VI execution although I get Warning -1073676294 which I understand to be the buffer issue. The warning says that this was incurred on VISA Open for the E3646A's Initialize VI which is outside both loops, however, which I don't understand.
I tried increasing buffer size by decreasing the Number of Samples as per suggestions I found on NI forum threads. I've brought it down as low as 1 but the graph still only updates when an Event occurs and I keep getting the same buffer error. You suggested that the problem could be that they are in the same loop; does this mean that the DAQmx read should be outside both Producer and Consumer Loops or moved into the Consumer Loop? I found a couple of links ( http://forums.ni.com/t5/LabVIEW/Producer-Consumer-Design-Pattern-DAQmx-Event-Structure/td-p/2744450 , http://forums.ni.com/t5/LabVIEW/Producer-Consumer-Architecture/td-p/494883 -first response) on dealing with an Event Structure that my own VI is based. Alternatively, I found another link ( http://forums.ni.com/t5/LabVIEW/Producer-Consumer-Design-Pattern-DAQmx-Event-Structure/td-p/2744450 - first response) on a DAQmx Read with an Event Structure that places the graph in the Consumer Loop.
The core of my purpose in setting up this Producer Consumer Architecture is so that I could read continuously while the instrument parameters are updated dynamically so it's very important that I understand how this works. I am particularly struggling with how the Event Structure is controlling the While Loop's Execution.
Hope to hear form you,
Yusif Nurizade
Attachments:
DCe3646A_DAQ6212_Prod_Con_4_14a_2014_Edit_I.vi 90 KB -
I just download and install itunes 10.5 and it worked good the first days but since yesterday it crashed up, and everytime i start it it crashes again and logged me out each time. it can´t acces my itunes account. I´m using snow leopard the last version. What can i do to solve this problem and and continue using my itunes normally?
Try doing it in a WIndows Safe mode - Restart computer and hit F8 key right after your see BIOS check and choose "Safe mode with networking"
Do the SFC /SCANNOW again.
If that does not work, whilst in safe mode, download Free Malwarebyte software from CNET's Download.com. Install, update virus definition then perform a full scan. Remove if it did find some viruses or trojans. Restart computer.
Back to regular windows, do the SFC /SCANNOW again.
If that doesnot work, check to see if your Hard drive has errors or bad sectors
GO START BUTTON /COMPUTER, right mouse click OS (C:) and choose "Properties"
Choose "Tools" tab and under error checking, click "Check Now".
Make sure "Scan for and attempt recovery of bad sectors" is checked and click start.
Restart windows will perform the above task to fix errors This may take hours depends on how big is your Hard Drive
Good Luck!!.
Maybe you are looking for
-
Sync; Windows Updater; iTunes no longer works
I connected my iPhone 4 to the USB port, synced it and then left the phone connected and iTunes running when I went to bed. When I woke up, the welcome screen was on and, after login, I received the message that Windows updater had performed some upd
-
Activated overlays color won't show in menus
I am using DVDSP4, I have 5 menus, the first is a video background, the others are jpegs. In the main (video) menu, i have three buttons with simple underlines as the overlays. When they are in selected mode...they are white...then if you activate on
-
Mac hangs for any ipfwd command with uid.
Hi, I need to resolve problem with ipfw firewall. When I add any new route which filter based on uid, I lost all connectivity and my Mac hangs. It only can be restored by power cycle. This is example of command I use: sudo ipfw add 100 allow ip from
-
Wireless controller ap1130 h-reap
We are about to pull these things out. TAC cannot find the problem. Customer had ap350s and runs fine over their wan. Tried to put h-reap with local switching and it has been nothing but a nightmare. clients disconnect from ap yet controller shows th
-
Database started but cannot select objects..
Hi All, I've come across a situation where i restored and recovered the db to another box and after opening the database i can desc the v$ and dba_ objects but when i do a select tablespace_name from dba_tablespaces or any other alter statements the