When to use Locale specific data in HWC ?
Working with a HWC application i noticed two other options as in screenshot in the MBO screen (i.e Wrap data in PRE CODE and Locale -specific display ). When is the appropriate scenario to use these options?
I never tried this but you may look at here:
Wrap header in PRE : SyBooks Online
Locale Specific : SyBooks Online
Similar Messages
-
Enforcing integrity using oracle specific data base commands .v. using fron
Full subject : Enforcing integrity using oracle specific data base commands .v. using front end.
It ought to be generally accepted that it is better to enforce integrity directly in the data base using constraints, dependencies, triggers etc rather than leaving it to specific front end programmes.
In my view, the chief advantages - of enforcing integrity directly in the data base - are:
(1) No process can violate the integrity.
(2) Being server centric, these commands run on the server and so can be easily sized in one place.
(3) One time data migration (imports) into the system using Oracle tools or SQL commands would also need to conform to the integrity constraints. Thus an implementor would be assured that the basic data is alright.
I am faced with a situation where we are about to implement a new Oracle based package. During data migration, when we discovered that there are no integrity constraints built into the target data base, the package vendor asserted that it is not necessary to build in integrity into the database. This seems to be an extreme and risky view.
Further, it is argued by the package vendor that putting constraints directly in the data base would significantly increase the needed resources (RAM) on the server. In my view, this increase is trivial and anyway, hardware costs are crashing day by day.
In the absence of integrity checks in the data base, it seems to me that every program would have to extra zero value work to ensure integrity of the end user data. It will still never be complete.
I would like to know the pros and cons of implementing without integrity constraints.
OK.AnanthaP wrote:
Full subject : Enforcing integrity using oracle specific data base commands .v. using front end.
It ought to be generally accepted that it is better to enforce integrity directly in the data base using constraints, dependencies, triggers etc rather than leaving it to specific front end programmes.
In my view, the chief advantages - of enforcing integrity directly in the data base - are:
(1) No process can violate the integrity.
(2) Being server centric, these commands run on the server and so can be easily sized in one place.
(3) One time data migration (imports) into the system using Oracle tools or SQL commands would also need to conform to the integrity constraints. Thus an implementor would be assured that the basic data is alright.
I am faced with a situation where we are about to implement a new Oracle based package. During data migration, when we discovered that there are no integrity constraints built into the target data base, the package vendor asserted that it is not necessary to build in integrity into the database. This seems to be an extreme and risky view.
Further, it is argued by the package vendor that putting constraints directly in the data base would significantly increase the needed resources (RAM) on the server. In my view, this increase is trivial and anyway, hardware costs are crashing day by day.
In the absence of integrity checks in the data base, it seems to me that every program would have to extra zero value work to ensure integrity of the end user data. It will still never be complete.
I would like to know the pros and cons of implementing without integrity constraints.
OK.It's a shame you seem to be so far into the process and committed to this vendor. I once had a vendor tell us his product would run on Oracle but they recommended MS SQL Server because "oracle can't handle more than 5 concurrent sessions." I made sure that vendor didn't make the short list. -
Approach when the used Live cache data area crosses the threshold
Hi,
Could any of you please let me know the detailed approach when the used Live cache data area crosses the threshold in APO system?
The approach I have as of now is :
1) When it is identified that data cache usage is nearly 100%, check for hit rate for OMS data in data cache in LC10 .Because generally hit rate for OMS data in data cache should be atleaset 99.8% and Data Cache usage should be well below 100%.
2) To monitor unsuccessful accesses to data cache choose refresh and compare value now and before unsuccessful accesses result in physical disk I/O and should generally be avoided.
3) The number of OMS data pages (OMS Data) should be much higher than the number of OMS history pages (History/Undo).A ratio of 4:1 is desirable. If OMS history has nearly the same size as OMS data, use Problem AnalysisPerformanceOMS versions to find out if named consistent views (Versions) are open for a long time. Maximum age should be 8hrs.
4)If consumption of OMS heap and data cache is large, one reason may be a long running transaction simulation that accumulates heap memory and prevents the garbage collector from releasing old object images.
5) To display existing transactional simulations in LC10,use Problem AnalysisPerformanceOMS versions and SM04 to find out user of corresponding transaction and may be required to cancel the session after contacting user if the version open for long time..
Please help me by providing additional information on the issue.
Thanks,
Varada Reddy.Hi Mayank, sorry, one basic question - are you using some selection criteria during extraction? If yes, then try extraction without the selection criteria.
If you maintain selection based on, let's say, material, you need to use the right number of zeros as prefix (based on how you have defined the characteristic for material) otherwise no records would be selected.
Is this relevant in your case?
One more option is to try to repair teh datasource. In the planning area, go to extraction tools, select the datasource, and then choose the option of repair datasource.
If you need more info, pls let me know.
- Pawan -
Detailed approach when the used Live cache data area crosses the threshold
Hi,
Could any of you please let me know the detailed approach when the used Live cache data area crosses the threshold in APO system?
The approach I have as of now is :
1) When it is identified that data cache usage is nearly 100%, check for hit rate for OMS data in data cache in LC10 .Because generally hit rate for OMS data in data cache should be atleaset 99.8% and Data Cache usage should be well below 100%.
2) To monitor unsuccessful accesses to data cache choose refresh and compare value now and before unsuccessful accesses result in physical disk I/O and should generally be avoided.
3) The number of OMS data pages (OMS Data) should be much higher than the number of OMS history pages (History/Undo).A ratio of 4:1 is desirable. If OMS history has nearly the same size as OMS data, use Problem AnalysisPerformanceOMS versions to find out if named consistent views (Versions) are open for a long time. Maximum age should be 8hrs.
4)If consumption of OMS heap and data cache is large, one reason may be a long running transaction simulation that accumulates heap memory and prevents the garbage collector from releasing old object images.
5) To display existing transactional simulations in LC10,use Problem AnalysisPerformanceOMS versions and SM04 to find out user of corresponding transaction and may be required to cancel the session after contacting user if the version open for long time..
Please help me by providing additional information on the issue.
Thanks,
Varada Reddy.Hi Mayank, sorry, one basic question - are you using some selection criteria during extraction? If yes, then try extraction without the selection criteria.
If you maintain selection based on, let's say, material, you need to use the right number of zeros as prefix (based on how you have defined the characteristic for material) otherwise no records would be selected.
Is this relevant in your case?
One more option is to try to repair teh datasource. In the planning area, go to extraction tools, select the datasource, and then choose the option of repair datasource.
If you need more info, pls let me know.
- Pawan -
Getting locale specific date and time
Hi,
I am tyring to create a program which will display the current date and time for a specific locale. But I am clueless as to how to proceed.
Please help me.
Thanksexamples:
servers and protocols: http://tf.nist.gov/service/its.htm
a simple java client using the daytime protocol: http://www.cafeaulait.org/course/week12/18.html
(u can use the simpledateformat class to parse the output string to a java date) -
Why do I get a memory leak when I use the Write Data Storage VI in a loop
I have a large application that I am collecting various data points from. For the most part they are simple scalar values that need to be logged on a regular basis. I was attempting to use the new TDM files and the storage VI's I though everything was working until I looked at the taskmanager and noticed that when the logging loop ran my CPU eventually went to 100% and the process memory grew from about 80,000K to 100,000K and eventually locks up the system.
I am using a state machine arch.
State 1 - open file (open create) mode)
State 2 - Write Channel Group Properties
State 3 - Loop writes 24 distinct data points to a TDM files in append mode
State 3 - Repeats [creating new rows of the same 24 data point (wait time about 1 sec)]
State 4 - Close file on exit.
Any help on this problem would be appreciated.The way I see it, it should be this way.
Message Edited by Pana-man on 09-30-2005 08:15 PM
Message Edited by Pana-man on 09-30-2005 08:18 PM
Paul <--Always Learning!!!
sense and simplicity.
Browse my sample VIs?
Attachments:
nextWeek.jpg 43 KB -
Slow сlient roaming when HREAP used (local swithing)
We have standart wireless deployment with 24 APs (1240G model) and wireless controller 4402-25 placed on same site.
Most of clients (WMS RF terminals ) works with one WLAN (WPA2-PSK) and constantly roam over warehouse , and that works great.
But for better survivability(when controller dies) we are trying to configure HREAP on our APs with local swicthed local auth WLAN. And that also work , but client roaming occur much more slowly and RDP connection to WMS APP server sometimes stuck for 2-5 sec.
Disabling "local switching" checkbox for WLAN make roaming almost momental.
Is that normal behavior ? And slow roaming are price for controllerless HREAP design ? And for fast roaming and survivability we must use N+1 wlc?
I'll be
appreciate for any opinions
and comments!Local switching should be okay since the AP will be doing the encryp/decrypt when using PSK. How does the traffic flow? Does everything come back to where the wlc sits or not? What I would try to determine is if it's a certain application having issues, a certain device or just overall all devices roam slow.
Thanks,
Scott Fella
Sent from my iPhone -
Hi ! when to use @Local and when to use @Remote?
Hello,
Say suppose i want to develop a multi tiered web application with presentation on 1 server, business logic on 1 server and database on 1 server, thus 3 servers altogether. But my all beans reside on single server ie 2nd server, so should i mark my beans as @Remote? or @Local? because my presentation is on 1st server and it will call bean on 2nd server. So, different JVM altogether.
Thanks in advance!Why do you have to give any advise that is not related to the question?Why to get side track? If you know the answer and if you have time then answer it else wait and watch, you will learn something from other people's experience. Let others come and answer. But kindly don't teach me philosophy like read books and you will find answer there and this and that. If it was clear to me why do you think i would ask question and waste your as well as my time? I come from .Net and things in JEE are very different.
This is a place to share knowledge and let others grow. I was just trying to self teach me reading tutorials here and there and asked question because it was not clear from the tutorial. Now, i know due to you nobody will come in this thread and answer this question.
Thanks
Edited by: Salman4u on Jan 27, 2010 12:57 AM -
When to use specific data structures
Hi
I'm currently learning Java and have found a wealth of information on data structures (link lists,queues et. al.) but I'm finding not much material on when best to apply specific data structures and the advantages and disadvantages. Could anyone point me to any resources?
Second question as a Java developer do you actually use things like linked lists etc regularly?
Thanks in advanceI suppose that a wealth of information exists because data structures are an integral part of programming. In simpler terms, all that information exists because the answer to question two is yes, absolutley.
The answer to question one is a bit trickier. It's kind of like asking when is best to use a flathead vrs. a phillips screwdriver. The answer seems obvious within a given context, but obscure outside of one.
IMHO: The 'when' becomes clear with experience. Focus on the 'how' and you'll be ready when you are faced with a problem that calls for a particular type of solution.
jch -
Oracle-specific data types vs Connection pool
Hi, using Oracle-specific data types such as
ArrayDescriptor and create it by a connection to an Oracle database from a WebSphere datasource throw a ClassCastException. There is no problem using these Oracle-specific data types when the connection is obtained via the DriverManager. WebSphere cannot fix the problem because these data types are
not part of the JDBC specification.
Some reply from Oracle?
Thank you very much.Thank you but I there is no solution in that thread.
Also, I know that WebLogic from BEA has a way around this issue... No Websphere work around ?
No Oracle fixing ?
Thanks. -
WHEN TO USE SYS_REFCURSOR AND WHEN NOT TO USE REFCURSOR
SYS_REFCURSOR is a Weakly Defined Cursor
DECLARE emp_refcur SYS_REFCURSOR;
when this is so simple
why this
DECLARE TYPE emp_cur_type IS REF CURSOR RETURN emp%ROWTYPE; my_rec emp_cur_type; ?
Can anyone explain in what situations we should prefer among these ..when both can give same result set .> WHEN TO USE SYS_REFCURSOR AND WHEN NOT TO USE REFCURSOR
When the requirements define that one is better suited than the other.
There are no hard and fast rules about when to use a specific tool. There are however basic concepts of what the purpose of the tool is, and what typical problems the tool can address.
Ref cursors in PL/SQL.. usually not the best of ideas. Ref cursors are designed for client-server processing.
1) The client makes a request for data/information.
2) PL applies the back-end server logic and construct a SQL statement for the client.
3) PL passes the SQL to the SQL engine where it is parsed and a SQL cursor created.
4) PL passes a reference handle to SQL cursor back to the client
5) The client can now fetch the rows output from the cursor.
Advantages.
- The client does not need to know SQL, db structures, business logic, etc
- The PL code can be improved, modified, new business logic added, without even touching a single byte of client code
So what are the advantages where the "client" in the above is another PL/SQL program? None really.
A "real" client (an external one like Java, C#, Delphi, etc) can receive the ref cursor handle and dynamically at run-time determine the projection (output) of the cursor.
PL code cannot (unless using the latest 11g features). In PL code, a ref cursor is actually implemented as a DBMS_SQL cursor. A DBMS_SQL cursor is to PL code what ref cursor is to Java/C#/etc.
So whether you define a strongly typed or weakly typed ref cursor in PL/SQL code... typical response is "so what?" as ref cursors are not really intended for PL code. Not that there are exceptions - they do come in handy at times.. but as exceptions to the rule.
So my response is "so what?" - it is more important to *correctly" chose what type of client cursor data type you want to use to interact with the back-end SQL cursor. Once that decision has been made (based on technical sound logic), then one can look at (minor) issues such as weak vs. strong ref cursors. -
in which situation we use LSMW ? and in which BDC?
Hi,
LSMW and BDC are vastly different.
BDC (Batch Data Communication) is a technology used for data transfer. it is meant for transferring data thru SAP transactions itself. when u use BDC for data transfer, the sequence of steps is the same as when u use standard sap transaction screens for data upload. the only difference is that u can use different options for foreground/backgrou nd processing.
LSMW on the other hand is a tool that helps migrate data from a legacy system (non-sap system ) to SAP system. it offers u various options to use either batch input, direct input, BAPIs or idocs. it involves a series of some 17-18 steps to migrate data.
BDC:
Batch Data Communication (BDC) is the process of transferring data from one SAP System to another SAP system or from a non-SAP system to SAP System.
Features :
BDC is an automatic procedure.
This method is used to transfer large amount of data that is available in electronic medium.
BDC can be used primarily when installing the SAP system and when transferring data from a legacy system (external system).
BDC uses normal transaction codes to transfer data.
Types of BDC :
CLASSICAL BATCH INPUT (Session Method)
CALL TRANSACTION
BATCH INPUT METHOD:
This method is also called as CLASSICAL METHOD.
Features:
Asynchronous processing.
Synchronous Processing in database update.
Transfer data for more than one transaction.
Batch input processing log will be generated.
During processing, no transaction is started until the previous transaction has been written to the database.
CALL TRANSACTION METHOD :
This is another method to transfer data from the legacy system.
Features:
Synchronous processing. The system performs a database commit immediately before and after the CALL TRANSACTION USING statement.
Updating the database can be either synchronous or asynchronous. The program specifies the update type.
Transfer data for a single transaction.
Transfers data for a sequence of dialog screens.
No batch input processing log is generated.
LSMW:
The LSM Workbench is an R/3-based tool that supports You when transferring data from non-SAP systems ("Legacy Systems") to R/3 once or periodically.
The tool supports conversion of data of the legacy system in a convenient way. The data can then be imported into the R/3 system via batch input, direct input, BAPIs or IDocs.
Furthermore, the LSM Workbench provides a recording function that allows to generate a "data migration object" in an entry or change transaction.
The main advantages of the LSM Workbench:
Part of R/3 and thus independent of individual platforms
A variety of technical possibilities of data conversion:
Data consistency due to standard import techniques:
Batch input
Direct input
BAPIs (Business Application Programming Interfaces)
IDocs (Intermediate Documents)
The import technique to be used in an individual case depends on the business object.
Generation of the conversion program on the basis of defined rules
Clear interactive process guide
Interface for data in spreadsheet format
Creation of data migration objects on the basis of recorded transactions
Charge-free for SAP customers and SAP partners
Regards,
Satish -
Using Local EJB obect in web container that installed in on the same Web AS
we can use the local ejb object in the application that runs in same JVM.
The Web Container and EJB Container run in the same JVM when Web AS installed as Minimum Cluster Installation(one cluster node).
But, what happened if we install the Web AS as Large Cluster Installation? Can we still use the local ejb objects in the Web Container?
Best regards,
Raja
Message was edited by: Raja NasrallahHi Raja,
Yes you can. When you use local EJB objects there's no remote communication and the web container will find them in the EJB container of the local cluster node. For the application providers this is transparent - they shouldn't care about the configuration of the cluster.
Best regards,
Vladimir
PS: Please consider <a href="https://www.sdn.sap.com/sdn/index.sdn?page=crp_help.htm#lostme">rewarding points</a> for helpful answers. -
When to use AMF and when to use RTMP??
Hello can someone explain the difference??
I am using all the defaults for the configurations files
(remoting and datamanagement) and my app works perfectly on
development mode where everything is on localhost, but when we try
it on pre-production it keeps throwing an error saying that it
couldn't connect to the RTMP channel. The only thing that changes
between these two modes is that on development i access everything
on localhost and on pre-production we point to another server.
I am totally clueless why this is happening, i am bit
confused why data-management uses RTMP and why remoting uses AMF,
so if anyone could explain it to me it would be great.
ThanksThere's no special reason why one uses RTMP vs. AMF. Data
management service can also use AMF and Remoting can also use RTMP.
The only real requiement is that Data management service needs to
be able to receive updates from the FDS/LCDS server. This can be
achieved by using a channel that is capable of receiving pushed
updates from the server (eg. RTMP) or a channel that is capable of
polling for updates on the server (i.e. AMF-polling). Therefore,
when you use AMF with Data management service, you need to have
polling enabled with a polling interval.
In terms of why AMF works but RTMP doesn't is that AMF
channel uses AMF format over the HTTP protocol whereas RTMP channel
uses simple TCP socket (and not HTTP). Therefore in some
environments, RTMP will be blocked by the firewalls but AMF won't
since it's like regular HTTP traffic. In this case, you can use AMF
polling instead or use RTMPT which is new in LCDS 2.5. -
Logic pro 9.1.7 keeps crashing when I use midi
Hi I only got my mac + logic pro a couple of months ago and it crashes when I'm not even doing anything heavy duty, just recording some piano, using a couple of tracks - it especially doesn't like it when I use the score - I get the Spinning Beach Ball of Death and then when I force quit it gives me the below info. Any help would be gratefully recieved I keep losing work! xx (It's fine when I use just audio)
Date/Time: 2012-08-31 01:04:41 +0300
OS Version: 10.7.4 (Build 11E2620)
Architecture: x86_64
Report Version: 9
Command: Logic Pro
Path: /Applications/Logic Pro.app/Contents/MacOS/Logic Pro
Version: 9.1.7 (1700.57)
Build Version: 2
Project Name: Logic
Source Version: 17005700
App Item ID: 459578486
App External ID: 6130764
Parent: launchd [135]
PID: 1872
Event: hang
Duration: 6.78s
Steps: 69 (100ms sampling interval)
Pageins: 0
Pageouts: 0
Process: Logic Pro [1872]
Path: /Applications/Logic Pro.app/Contents/MacOS/Logic Pro
Architecture: i386
UID: 501
Thread 0x2195c
User stack:
69 DummyConnection::DummyConnection() + 193 (in Logic Pro) [0x2b1c5]
69 NSProApplicationMain + 439 (in ProKit) [0xfa542b]
69 -[NSApplication run] + 911 (in AppKit) [0x985d4cb1]
69 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 113 (in AppKit) [0x985d8942]
69 _DPSNextEvent + 2196 (in AppKit) [0x985d96c6]
69 _NSHandleCarbonMenuEvent + 302 (in AppKit) [0x98648dbc]
69 _HandleMenuSelection + 53 (in HIToolbox) [0x9553f95d]
69 _HandleMenuSelection2 + 636 (in HIToolbox) [0x9553fbde]
69 _ZL14MenuSelectCoreP8MenuData5PointdmPP13OpaqueMenuRefPt + 608 (in HIToolbox) [0x956d8a60]
69 _ZL19FinishMenuSelectionP13SelectionDataP10MenuResultS2_ + 129 (in HIToolbox) [0x95547f2d]
69 SendMenuItemSelectedEvent + 275 (in HIToolbox) [0x956e7b61]
69 SendMenuCommandWithContextAndModifiers + 70 (in HIToolbox) [0x9567c31a]
69 _ZL18SendHICommandEventmPK9HICommandmmhPKvP20OpaqueEventTargetRefS5_PP14OpaqueE ventRef + 482 (in HIToolbox) [0x9567c2b0]
69 SendEventToEventTarget + 76 (in HIToolbox) [0x9550b755]
69 _ZL30SendEventToEventTargetInternalP14OpaqueEventRefP20OpaqueEventTargetRefP14H andlerCallRec + 482 (in HIToolbox) [0x954f6970]
69 _ZL23DispatchEventToHandlersP14EventTargetRecP14OpaqueEventRefP14HandlerCallRec + 1602 (in HIToolbox) [0x954f74f3]
69 _InvokeEventHandlerUPP(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*, long (*)(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*)) + 36 (in HIToolbox) [0x9567bdec]
69 NSSLMMenuEventHandler + 452 (in AppKit) [0x9874b446]
69 -[NSCarbonMenuImpl _carbonCommandProcessEvent:handlerCallRef:] + 172 (in AppKit) [0x9891b78c]
69 -[NSMenuItem _internalPerformActionThroughMenuIfPossible] + 106 (in AppKit) [0x98ab522f]
69 -[NSMenu _internalPerformActionForItemAtIndex:] + 45 (in AppKit) [0x98ab0ffe]
69 -[NSMenu performActionForItemAtIndex:] + 65 (in AppKit) [0x98ab0fcb]
69 -[NSMenu _performActionWithHighlightingForItemAtIndex:sendAccessibilityNotification:] + 79 (in AppKit) [0x987d5149]
69 -[NSCarbonMenuImpl performActionWithHighlightingForItemAtIndex:] + 171 (in AppKit) [0x987d5ac0]
69 -[NSMenuItem _corePerformAction] + 536 (in AppKit) [0x987d5e43]
69 std::ostream& TraceOutContainer<CEvs>(std::ostream&, CEvs, char const*, int) + 6011018 (in Logic Pro) [0x5f72fa]
69 -[NSProApplication sendAction:to:from:] + 118 (in ProKit) [0xfa4f9d]
69 -[NSApplication sendAction:to:from:] + 232 (in AppKit) [0x986e286f]
69 -[NSObject performSelector:withObject:] + 65 (in CoreFoundation) [0x947f2d11]
69 std::ostream& TraceOutContainer<CEvs>(std::ostream&, CEvs, char const*, int) + 6017897 (in Logic Pro) [0x5f8dd9]
69 std::ostream& TraceOutContainer<CEvs>(std::ostream&, CEvs, char const*, int) + 6017097 (in Logic Pro) [0x5f8ab9]
69 -[NSDocument saveDocumentAs:] + 65 (in AppKit) [0x989a6bd1]
69 std::ostream& TraceOutContainer<CEvs>(std::ostream&, CEvs, char const*, int) + 6021276 (in Logic Pro) [0x5f9b0c]
69 -[NSDocument runModalSavePanelForSaveOperation:delegate:didSaveSelector:contextInfo:] + 116 (in AppKit) [0x989a7c8e]
69 -[NSDocument performActivityWithSynchronousWaiting:usingBlock:] + 90 (in AppKit) [0x989c1d7e]
69 __-[NSDocument runModalSavePanelForSaveOperation:delegate:didSaveSelector:contextInfo:]_block_ invoke_1 + 223 (in AppKit) [0x989a7d72]
69 -[NSDocument _commitEditingWithDelegate:didSomethingSelector:contextInfo:thenContinue:] + 108 (in AppKit) [0x989b3771]
69 -[NSDocument _commitEditingThenContinue:] + 335 (in AppKit) [0x989b7f35]
69 __-[NSDocument _commitEditingWithDelegate:didSomethingSelector:contextInfo:thenContinue:]_bloc k_invoke_1 + 34 (in AppKit) [0x989b3798]
69 __-[NSDocument runModalSavePanelForSaveOperation:delegate:didSaveSelector:contextInfo:]_block_ invoke_2 + 1037 (in AppKit) [0x989a8200]
69 __-[NSDocument runModalSavePanelForSaveOperation:delegate:didSaveSelector:contextInfo:]_block_ invoke_6 + 380 (in AppKit) [0x989b59ea]
69 -[NSDocument continueActivityUsingBlock:] + 30 (in AppKit) [0x989a306c]
69 __-[NSDocument runModalSavePanelForSaveOperation:delegate:didSaveSelector:contextInfo:]_block_ invoke_10 + 198 (in AppKit) [0x989b5de5]
69 -[NSDocument saveToURL:ofType:forSaveOperation:delegate:didSaveSelector:contextInfo:] + 128 (in AppKit) [0x989a8436]
69 -[NSDocument performActivityWithSynchronousWaiting:usingBlock:] + 90 (in AppKit) [0x989c1d7e]
69 __-[NSDocument saveToURL:ofType:forSaveOperation:delegate:didSaveSelector:contextInfo:]_block_ invoke_1 + 328 (in AppKit) [0x989a8583]
69 -[NSDocument _commitEditingWithDelegate:didSomethingSelector:contextInfo:thenContinue:] + 108 (in AppKit) [0x989b3771]
69 -[NSDocument _commitEditingThenContinue:] + 335 (in AppKit) [0x989b7f35]
69 __-[NSDocument _commitEditingWithDelegate:didSomethingSelector:contextInfo:thenContinue:]_bloc k_invoke_1 + 34 (in AppKit) [0x989b3798]
69 __-[NSDocument saveToURL:ofType:forSaveOperation:delegate:didSaveSelector:contextInfo:]_block_ invoke_5 + 26 (in AppKit) [0x989a32e9]
69 __-[NSDocument saveToURL:ofType:forSaveOperation:delegate:didSaveSelector:contextInfo:]_block_ invoke_2 + 169 (in AppKit) [0x989a8707]
69 -[NSDocument saveToURL:ofType:forSaveOperation:completionHandler:] + 108 (in AppKit) [0x989a9dc4]
69 -[NSDocument performAsynchronousFileAccessUsingBlock:] + 285 (in AppKit) [0x989c1a8f]
69 -[NSDocument _performFileAccessOnMainThread:usingBlock:] + 388 (in AppKit) [0x989c1cf6]
69 -[NSDocument continueFileAccessUsingBlock:] + 252 (in AppKit) [0x989a45da]
69 __-[NSDocument _performFileAccessOnMainThread:usingBlock:]_block_invoke_7 + 53 (in AppKit) [0x989a47d2]
69 __-[NSDocument performAsynchronousFileAccessUsingBlock:]_block_invoke_8 + 25 (in AppKit) [0x989a30f3]
69 __-[NSDocument saveToURL:ofType:forSaveOperation:completionHandler:]_block_invoke_1 + 885 (in AppKit) [0x989aa13e]
69 -[NSDocument _fileCoordinator:coordinateReadingContentsAndWritingItemAtURL:byAccessor:] + 309 (in AppKit) [0x989bda21]
69 -[NSFileCoordinator(NSPrivate) _coordinateReadingItemAtURL:options:writingItemAtURL:options:error:byAccessor:] + 788 (in Foundation) [0x96c0e620]
69 -[NSFileCoordinator(NSPrivate) _invokeAccessor:orDont:thenRelinquishAccessClaimForID:] + 194 (in Foundation) [0x96c0ae2e]
69 __-[NSFileCoordinator(NSPrivate) _coordinateReadingItemAtURL:options:writingItemAtURL:options:error:byAccessor:] _block_invoke_3 + 77 (in Foundation) [0x96c0a43b]
69 __-[NSDocument _fileCoordinator:coordinateReadingContentsAndWritingItemAtURL:byAccessor:]_bloc k_invoke_1 + 50 (in AppKit) [0x989a3320]
69 __-[NSDocument saveToURL:ofType:forSaveOperation:completionHandler:]_block_invoke_7 + 1338 (in AppKit) [0x989ca062]
69 __-[NSDocument saveToURL:ofType:forSaveOperation:completionHandler:]_block_invoke_14 + 322 (in AppKit) [0x989c957c]
69 __-[NSDocument saveToURL:ofType:forSaveOperation:completionHandler:]_block_invoke_15 + 311 (in AppKit) [0x989c96bb]
69 __-[NSDocument saveToURL:ofType:forSaveOperation:completionHandler:]_block_invoke_8 + 366 (in AppKit) [0x989ca292]
69 std::ostream& TraceOutContainer<CEvs>(std::ostream&, CEvs, char const*, int) + 6019103 (in Logic Pro) [0x5f928f]
69 -[NSDocument writeSafelyToURL:ofType:forSaveOperation:error:] + 435 (in AppKit) [0x989bf44c]
69 -[NSDocument _writeSafelyToURL:ofType:forSaveOperation:error:] + 69 (in AppKit) [0x989a6b4a]
69 -[NSDocument _writeSafelyToURL:ofType:forSaveOperation:forceTemporaryDirectory:error:] + 587 (in AppKit) [0x989bf6a2]
69 std::ostream& TraceOutContainer<CEvs>(std::ostream&, CEvs, char const*, int) + 6018036 (in Logic Pro) [0x5f8e64]
69 -[NSDocument writeToURL:ofType:forSaveOperation:originalContentsURL:error:] + 510 (in AppKit) [0x989bf251]
69 -[NSDocument writeToURL:ofType:error:] + 465 (in AppKit) [0x989c04c1]
69 std::ostream& TraceOutContainer<CEvs>(std::ostream&, CEvs, char const*, int) + 6023072 (in Logic Pro) [0x5fa210]
69 std::ostream& TraceOutContainer<CEvs>(std::ostream&, CEvs, char const*, int) + 6020360 (in Logic Pro) [0x5f9778]
69 std::ostream& TraceOutContainer<CEvs>(std::ostream&, CEvs, char const*, int) + 6019723 (in Logic Pro) [0x5f94fb]
69 std::ostream& TraceOutContainer<CEvs>(std::ostream&, CEvs, char const*, int) + 6035245 (in Logic Pro) [0x5fd19d]
69 -[NSBitmapImageRep initWithFocusedViewRect:] + 1712 (in AppKit) [0x988d3037]
69 ??? [0xffffffff]
69 _sigtramp + 43 (in libsystem_c.dylib) [0x93c5259b]
69 std::ostream& TraceOutContainer<CEvs>(std::ostream&, CEvs, char const*, int) + 3839242 (in Logic Pro) [0x3e4f7a]
69 -[NSDocument(NSDeprecated) saveToURL:ofType:forSaveOperation:error:] + 285 (in AppKit) [0x989c5a2e]
69 -[NSDocument _coordinateReadingContentsAndWritingItemAtURL:error:byAccessor:] + 307 (in AppKit) [0x989a8d8a]
69 -[NSFileCoordinator coordinateReadingItemAtURL:options:writingItemAtURL:options:error:byAccessor:] + 125 (in Foundation) [0x96c0a927]
69 -[NSFileCoordinator(NSPrivate) _coordinateReadingItemAtURL:options:writingItemAtURL:options:error:byAccessor:] + 788 (in Foundation) [0x96c0e620]
69 -[NSFileCoordinator(NSPrivate) _invokeAccessor:orDont:thenRelinquishAccessClaimForID:] + 194 (in Foundation) [0x96c0ae2e]
69 __-[NSFileCoordinator(NSPrivate) _coordinateReadingItemAtURL:options:writingItemAtURL:options:error:byAccessor:] _block_invoke_3 + 77 (in Foundation) [0x96c0a43b]
69 __-[NSFileCoordinator coordinateReadingItemAtURL:options:writingItemAtURL:options:error:byAccessor:]_ block_invoke_1 + 197 (in Foundation) [0x96c0a9f1]
69 __-[NSDocument _coordinateReadingContentsAndWritingItemAtURL:error:byAccessor:]_block_invoke_1 + 25 (in AppKit) [0x989a3375]
69 __-[NSDocument(NSDeprecated) saveToURL:ofType:forSaveOperation:error:]_block_invoke_1 + 199 (in AppKit) [0x989c2de1]
69 __-[NSDocument(NSDeprecated) saveToURL:ofType:forSaveOperation:error:]_block_invoke_2 + 304 (in AppKit) [0x989c2f49]
69 std::ostream& TraceOutContainer<CEvs>(std::ostream&, CEvs, char const*, int) + 6019103 (in Logic Pro) [0x5f928f]
69 -[NSDocument writeSafelyToURL:ofType:forSaveOperation:error:] + 435 (in AppKit) [0x989bf44c]
69 -[NSDocument _writeSafelyToURL:ofType:forSaveOperation:error:] + 69 (in AppKit) [0x989a6b4a]
69 -[NSDocument _writeSafelyToURL:ofType:forSaveOperation:forceTemporaryDirectory:error:] + 587 (in AppKit) [0x989bf6a2]
69 std::ostream& TraceOutContainer<CEvs>(std::ostream&, CEvs, char const*, int) + 6018036 (in Logic Pro) [0x5f8e64]
69 -[NSDocument writeToURL:ofType:forSaveOperation:originalContentsURL:error:] + 510 (in AppKit) [0x989bf251]
69 -[NSDocument writeToURL:ofType:error:] + 465 (in AppKit) [0x989c04c1]
69 std::ostream& TraceOutContainer<CEvs>(std::ostream&, CEvs, char const*, int) + 6023072 (in Logic Pro) [0x5fa210]
69 std::ostream& TraceOutContainer<CEvs>(std::ostream&, CEvs, char const*, int) + 6020360 (in Logic Pro) [0x5f9778]
69 std::ostream& TraceOutContainer<CEvs>(std::ostream&, CEvs, char const*, int) + 6019723 (in Logic Pro) [0x5f94fb]
69 std::ostream& TraceOutContainer<CEvs>(std::ostream&, CEvs, char const*, int) + 6035245 (in Logic Pro) [0x5fd19d]
69 -[NSBitmapImageRep initWithFocusedViewRect:] + 195 (in AppKit) [0x988d2a4a]
69 CGPixelAccessLock + 26 (in CoreGraphics) [0x95c2df1e]
69 __psynch_mutexwait + 10 (in libsystem_kernel.dylib) [0x90580876]
Kernel stack:
69 psynch_mtxcontinue + 0 (in mach_kernel) [0xffffff800059e520]
Thread 0x21971 DispatchQueue 1701273966
User stack:
69 _dispatch_mgr_thread + 53 (in libdispatch.dylib) [0x97d7d85f]
69 kevent + 10 (in libsystem_kernel.dylib) [0x9058190a]
Kernel stack:
69 kqueue_scan + 416 (in mach_kernel) [0xffffff800053aec0]
Thread 0x2197c
User stack:
69 thread_start + 34 (in libsystem_c.dylib) [0x93bfe6de]
69 _pthread_start + 335 (in libsystem_c.dylib) [0x93bfaed9]
69 __NSThread__main__ + 1582 (in Foundation) [0x96a55dd5]
69 -[NSThread main] + 45 (in Foundation) [0x96a55e25]
69 +[NSURLConnection(NSURLConnectionReallyInternal) _resourceLoadLoop:] + 378 (in Foundation) [0x96a620c4]
69 CFRunLoopRunInMode + 120 (in CoreFoundation) [0x94793088]
69 CFRunLoopRunSpecific + 332 (in CoreFoundation) [0x947931dc]
69 __CFRunLoopRun + 1428 (in CoreFoundation) [0x94793b04]
69 __CFRunLoopServiceMachPort + 170 (in CoreFoundation) [0x9478a9da]
69 mach_msg_trap + 10 (in libsystem_kernel.dylib) [0x9057ec22]
Kernel stack:
69 ipc_mqueue_receive_continue + 0 (in mach_kernel) [0xffffff8000215930]
Thread 0x21983
User stack:
69 thread_start + 34 (in libsystem_c.dylib) [0x93bfe6de]
69 _pthread_start + 335 (in libsystem_c.dylib) [0x93bfaed9]
69 __select + 10 (in libsystem_kernel.dylib) [0x90580b42]
Kernel stack:
69 wakeup + 992 (in mach_kernel) [0xffffff8000555880]
Thread 0x219b8
User stack:
69 thread_start + 34 (in libsystem_c.dylib) [0x93bfe6de]
69 _pthread_start + 335 (in libsystem_c.dylib) [0x93bfaed9]
69 MDFileIOThread_IsBusy + 3593 (in MAAudioEngine) [0x2b1e899]
69 pthread_cond_wait$UNIX2003 + 71 (in libsystem_c.dylib) [0x93baf42c]
69 __psynch_cvwait + 10 (in libsystem_kernel.dylib) [0x9058083e]
Kernel stack:
69 psynch_cvcontinue + 0 (in mach_kernel) [0xffffff800059e320]
Thread 0x219bb
User stack:
69 thread_start + 34 (in libsystem_c.dylib) [0x93bfe6de]
69 _pthread_start + 335 (in libsystem_c.dylib) [0x93bfaed9]
69 CAPThread::Entry(CAPThread*) + 123 (in CoreMIDI) [0x1364f69]
69 XThread::RunHelper(void*) + 17 (in CoreMIDI) [0x136559f]
69 MIDIProcess::MIDIInPortThread::Run() + 24 (in CoreMIDI) [0x1387912]
69 MIDIProcess::RunMIDIInThread() + 259 (in CoreMIDI) [0x1386f8b]
69 XServerMachPort::ReceiveMessage(int&, void*, int&) + 101 (in CoreMIDI) [0x1363fcb]
69 mach_msg_trap + 10 (in libsystem_kernel.dylib) [0x9057ec22]
Kernel stack:
69 ipc_mqueue_receive_continue + 0 (in mach_kernel) [0xffffff8000215930]
Thread 0x21ef9
User stack:
69 thread_start + 34 (in libsystem_c.dylib) [0x93bfe6de]
69 _pthread_start + 335 (in libsystem_c.dylib) [0x93bfaed9]
69 thread_fun + 29 (in QuartzCore) [0x90989866]
69 CA::Render::Server::server_thread(void*) + 233 (in QuartzCore) [0x90989959]
69 mach_msg_trap + 10 (in libsystem_kernel.dylib) [0x9057ec22]
Kernel stack:
69 ipc_mqueue_receive_continue + 0 (in mach_kernel) [0xffffff8000215930]
Thread 0x31332
User stack:
69 thread_start + 34 (in libsystem_c.dylib) [0x93bfe6de]
69 _pthread_start + 335 (in libsystem_c.dylib) [0x93bfaed9]
69 __NSThread__main__ + 1582 (in Foundation) [0x96a55dd5]
69 -[NSThread main] + 45 (in Foundation) [0x96a55e25]
68 -[NSUIHeartBeat _heartBeatThread:] + 2399 (in AppKit) [0x9881d816]
68 usleep$UNIX2003 + 60 (in libsystem_c.dylib) [0x93baf558]
68 __semwait_signal + 10 (in libsystem_kernel.dylib) [0x90580bb2]
1 _setjmp + 4 (in libsystem_c.dylib) [0x93c0ea1c]
Kernel stack:
66 semaphore_wait_continue + 0 (in mach_kernel) [0xffffff8000234650]
2 hndl_unix_scall + 281 (in mach_kernel) [0xffffff80002daa79]
2 unix_syscall + 472 (in mach_kernel) [0xffffff80005cd898]
2 __semwait_signal_nocancel + 155 (in mach_kernel) [0xffffff8000553fbb]
2 semaphore_timedwait_trap_internal + 135 (in mach_kernel) [0xffffff8000234f27]
2 semaphore_signal_internal + 944 (in mach_kernel) [0xffffff8000234b10]
2 thread_block_reason + 275 (in mach_kernel) [0xffffff800022f413]
2 thread_go + 608 (in mach_kernel) [0xffffff800022e060]
2 processor_idle + 149 (in mach_kernel) [0xffffff800022d375]
2 machine_idle + 289 (in mach_kernel) [0xffffff80002c6461]
1 hndl_allintrs + 290 (in mach_kernel) [0xffffff80002da712]
1 interrupt + 192 (in mach_kernel) [0xffffff80002c48d0]
1 lapic_interrupt + 121 (in mach_kernel) [0xffffff80002c9ab9]
1 cpu_signal_handler + 172 (in mach_kernel) [0xffffff80002cb9ac]
1 sync_iss_to_iks + 118 (in mach_kernel) [0xffffff80002c3c76]
Thread 0x31436
User stack:
54 start_wqthread + 30 (in libsystem_c.dylib) [0x93bfe6fe]
54 __workq_kernreturn + 10 (in libsystem_kernel.dylib) [0x9058102e]
Kernel stack:
54 workqueue_mark_exiting + 1408 (in mach_kernel) [0xffffff80005a4ab0]
Thread 0x319df
User stack:
15 start_wqthread + 30 (in libsystem_c.dylib) [0x93bfe6fe]
15 __workq_kernreturn + 10 (in libsystem_kernel.dylib) [0x9058102e]
Kernel stack:
15 workqueue_mark_exiting + 1408 (in mach_kernel) [0xffffff80005a4ab0]
Binary Images:
0x1000 - 0xbe7ff7 com.apple.logic.pro 9.1.7 (1700.57) <5F56E15A-9720-AE07-31BF-AD616FF0803C> /Applications/Logic Pro.app/Contents/MacOS/Logic Pro
0xf82000 - 0x11aaff7 com.apple.prokit 7.2.2 (1817) <832C3859-AF71-3CC5-83AB-20764115E483> /System/Library/PrivateFrameworks/ProKit.framework/Versions/A/ProKit
0x1354000 - 0x13a0ffb com.apple.audio.midi.CoreMIDI 1.8 (42) <292E006C-CB38-39AD-9AAD-0151D9AF060D> /System/Library/Frameworks/CoreMIDI.framework/Versions/A/CoreMIDI
0x2aeb000 - 0x2b62fe7 com.apple.music.apps.MAAudioEngine 9.1.7 (158.32) <4FD5874A-C993-D1F5-4B8F-F1BC56C4CDB9> /Applications/Logic Pro.app/Contents/Frameworks/MAAudioEngine.framework/Versions/A/MAAudioEngine
0x90568000 - 0x90586ff7 libsystem_kernel.dylib ??? (???) <EE8DD7FD-53FC-3DE0-8622-7CCF062716EC> /usr/lib/system/libsystem_kernel.dylib
0x90987000 - 0x90ae9ffb com.apple.QuartzCore 1.7 (270.5) <6E04A99C-2F52-3E73-991E-340B048E8001> /System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore
0x93b9e000 - 0x93c69fff libsystem_c.dylib ??? (???) <03E608FA-1689-3D85-9A21-31C1922AEC1A> /usr/lib/system/libsystem_c.dylib
0x94758000 - 0x9492ffe7 com.apple.CoreFoundation 6.7.2 (635.21) <4D1D2BAF-1332-32DF-A81B-7E79D4F0A6CB> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
0x954ef000 - 0x95835ff3 com.apple.HIToolbox 1.9 (???) <96AFBCE8-61CC-31A6-8E57-2EC21D7A7851> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.fra mework/Versions/A/HIToolbox
0x95ada000 - 0x96402e2b com.apple.CoreGraphics 1.600.0 (???) <93490E7A-8CA6-3D58-AA13-B6FEB35647B4> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreGraphics.framework/Versions/A/CoreGraphics
0x969f6000 - 0x96d00ff3 com.apple.Foundation 6.7.2 (833.25) <361418ED-589D-36DE-9668-A88B35937524> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
0x97d7c000 - 0x97d8afff libdispatch.dylib ??? (???) <2F918480-12C8-3F22-9B1A-9B2D76F6F4F5> /usr/lib/system/libdispatch.dylib
0x985cf000 - 0x99064ff6 com.apple.AppKit 6.7.3 (1138.47) <D84BC928-E3D3-303C-88E0-942E18AFBDD6> /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit
Process: AirPort Base Station Agent [214]
Path: /System/Library/CoreServices/AirPort Base Station Agent.app/Contents/MacOS/AirPort Base Station Agent
Architecture: x86_64
UID: 501
Thread 0x6a9 DispatchQueue 1
User stack:
69 ??? (in AirPort Base Station Agent) [0x102944654]
69 ??? (in AirPort Base Station Agent) [0x102955353]
69 CFRunLoopRun + 95 (in CoreFoundation) [0x7fff9069d19f]
69 CFRunLoopRunSpecific + 230 (in CoreFoundation) [0x7fff9068d486]
69 __CFRunLoopRun + 1204 (in CoreFoundation) [0x7fff9068dc74]
69 __CFRunLoopServiceMachPort + 188 (in CoreFoundation) [0x7fff9068550c]
69 mach_msg_trap + 10 (in libsystem_kernel.dylib) [0x7fff9471e67a]
Kernel stack:
69 ipc_mqueue_receive_continue + 0 (in mach_kernel) [0xffffff8000215930]
Thread 0x6cd DispatchQueue 2
User stack:
69 _dispatch_mgr_thread + 54 (in libdispatch.dylib) [0x7fff93a7f31a]
69 kevent + 10 (in libsystem_kernel.dylib) [0x7fff947207e6]
Kernel stack:
69 kqueue_scan + 416 (in mach_kernel) [0xffffff800053aec0]
Thread 0x6d4
User stack:
69 thread_start + 13 (in libsystem_c.dylib) [0x7fff8cb19b75]
69 _pthread_start + 335 (in libsystem_c.dylib) [0x7fff8cb168bf]
69 __select + 10 (in libsystem_kernel.dylib) [0x7fff9471fdf2]
Kernel stack:
69 wakeup + 992 (in mach_kernel) [0xffffff8000555880]
Binary Images:
0x102943000 - 0x10295afff com.apple.AirPortBaseStationAgent 1.5.5 (155.7) <21653C11-D069-330A-A54C-5F0071AA70CC> /System/Library/CoreServices/AirPort Base Station Agent.app/Contents/MacOS/AirPort Base Station Agent
0x7fff8cac8000 - 0x7fff8cba5fef libsystem_c.dylib ??? (???) <535C622E-2C14-3DD4-98D0-EA181DF8D582> /usr/lib/system/libsystem_c.dylib
0x7fff90655000 - 0x7fff90829ff7 com.apple.CoreFoundation 6.7.2 (635.21) <62A3402E-A4E7-391F-AD20-1EF20236CE1B> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
0x7fff93a7d000 - 0x7fff93a8bfff libdispatch.dylib ??? (???) <1D5BE322-A9B9-3BCE-8FAC-076FB07CF54A> /usr/lib/system/libdispatch.dylib
0x7fff94709000 - 0x7fff94729fff libsystem_kernel.dylib ??? (???) <185823F1-409E-3AFD-93A9-C214013C17C8> /usr/lib/system/libsystem_kernel.dylib
Process: applepushserviced [53]
Path: /System/Library/PrivateFrameworks/ApplePushService.framework/applepushserviced
Architecture: x86_64
UID: 0
Thread 0x174 DispatchQueue 1
User stack:
69 ??? (in applepushserviced) [0x10fb478d4]
69 ??? (in applepushserviced) [0x10fb479b8]
69 -[NSRunLoop(NSRunLoop) run] + 62 (in Foundation) [0x7fff896a9e67]
69 -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 267 (in Foundation) [0x7fff896a9f7b]
69 CFRunLoopRunSpecific + 230 (in CoreFoundation) [0x7fff9068d486]
69 __CFRunLoopRun + 1204 (in CoreFoundation) [0x7fff9068dc74]
69 __CFRunLoopServiceMachPort + 188 (in CoreFoundation) [0x7fff9068550c]
69 mach_msg_trap + 10 (in libsystem_kernel.dylib) [0x7fff9471e67a]
Kernel stack:
69 ipc_mqueue_receive_continue + 0 (in mach_kernel) [0xffffff8000215930]
Thread 0x1a7 DispatchQueue 2
User stack:
69 _dispatch_mgr_thread + 54 (in libdispatch.dylib) [0x7fff93a7f31a]
69 kevent + 10 (in libsystem_kernel.dylib) [0x7fff947207e6]
Kernel stack:
69 kqueue_scan + 416 (in mach_kernel) [0xffffff800053aec0]
Thread 0x5d6
User stack:
69 thread_start + 13 (in libsystem_c.dylib) [0x7fff8cb19b75]
69 _pthread_start + 335 (in libsystem_c.dylib) [0x7fff8cb168bf]
69 __select + 10 (in libsystem_kernel.dylib) [0x7fff9471fdf2]
Kernel stack:
69 wakeup + 992 (in mach_kernel) [0xffffff8000555880]
Binary Images:
0x10fb46000 - 0x10fbb4ff7 applepushserviced ??? (???) <19819362-4B3D-326C-A00C-AC20DFB36B24> /System/Library/PrivateFrameworks/ApplePushService.framework/applepushserviced
0x7fff8969e000 - 0x7fff899b7fff com.apple.Foundation 6.7.2 (833.25) <F6584E06-7C8F-3422-AF84-3AA58EC67935> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
0x7fff8cac8000 - 0x7fff8cba5fef libsystem_c.dylib ??? (???) <535C622E-2C14-3DD4-98D0-EA181DF8D582> /usr/lib/system/libsystem_c.dylib
0x7fff90655000 - 0x7fff90829ff7 com.apple.CoreFoundation 6.7.2 (635.21) <62A3402E-A4E7-391F-AD20-1EF20236CE1B> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
0x7fff93a7d000 - 0x7fff93a8bfff libdispatch.dylib ??? (???) <1D5BE322-A9B9-3BCE-8FAC-076FB07CF54A> /usr/lib/system/libdispatch.dylib
0x7fff94709000 - 0x7fff94729fff libsystem_kernel.dylib ??? (???) <185823F1-409E-3AFD-93A9-C214013C17C8> /usr/lib/system/libsystem_kernel.dylib
Process: AppleSpell [186]
Path: /System/Library/Services/AppleSpell.service/Contents/MacOS/AppleSpell
Architecture: x86_64
UID: 501
Thread 0x628 DispatchQueue 1
User stack:
69 ??? (in AppleSpell) [0x10aa65a7c]
69 ??? (in AppleSpell) [0x10aa65d2e]
69 -[NSSpellServer run] + 74 (in Foundation) [0x7fff897fac76]
69 CFRunLoopRun + 95 (in CoreFoundation) [0x7fff9069d19f]
69 CFRunLoopRunSpecific + 230 (in CoreFoundation) [0x7fff9068d486]
69 __CFRunLoopRun + 1204 (in CoreFoundation) [0x7fff9068dc74]
69 __CFRunLoopServiceMachPort + 188 (in CoreFoundation) [0x7fff9068550c]
69 mach_msg_trap + 10 (in libsystem_kernel.dylib) [0x7fff9471e67a]
Kernel stack:
69 ipc_mqueue_receive_continue + 0 (in mach_kernel) [0xffffff8000215930]
Thread 0x62d DispatchQueue 2
User stack:
69 _dispatch_mgr_thread + 54 (in libdispatch.dylib) [0x7fff93a7f31a]
69 kevent + 10 (in libsystem_kernel.dylib) [0x7fff947207e6]
Kernel stack:
69 kqueue_scan + 416 (in mach_kernel) [0xffffff800053aec0]
Thread 0x319e3
User stack:
3 start_wqthread + 13 (in libsystem_c.dylib) [0x7fff8cb19b85]
3 __workq_kernreturn + 10 (in libsystem_kernel.dylib) [0x7fff94720192]
Kernel stack:
3 workqueue_mark_exiting + 1408 (in mach_kernel) [0xffffff80005a4ab0]
Binary Images:
0x10aa64000 - 0x10ab20ff7 com.apple.AppleSpell 1.7.1 (131.1) <37673EBC-DCDD-3B27-B4CB-A7BEF05E0039> /System/Library/Services/AppleSpell.service/Contents/MacOS/AppleSpell
0x7fff8969e000 - 0x7fff899b7fff com.apple.Foundation 6.7.2 (833.25) <F6584E06-7C8F-3422-AF84-3AA58EC67935> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
0x7fff8cac8000 - 0x7fff8cba5fef libsystem_c.dylib ??? (???) <535C622E-2C14-3DD4-98D0-EA181DF8D582> /usr/lib/system/libsystem_c.dylib
0x7fff90655000 - 0x7fff90829ff7 com.apple.CoreFoundation 6.7.2 (635.21) <62A3402E-A4E7-391F-AD20-1EF20236CE1B> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
0x7fff93a7d000 - 0x7fff93a8bfff libdispatch.dylib ??? (???) <1D5BE322-A9B9-3BCE-8FAC-076FB07CF54A> /usr/lib/system/libdispatch.dylib
0x7fff94709000 - 0x7fff94729fff libsystem_kernel.dylib ??? (???) <185823F1-409E-3AFD-93A9-C214013C17C8> /usr/lib/system/libsystem_kernel.dylib
Process: autofsd [51]
Path: /usr/libexec/autofsd
Architecture: x86_64
UID: 0
Thread 0x184 DispatchQueue 2
User stack:
69 _dispatch_mgr_thread + 54 (in libdispatch.dylib) [0x7fff93a7f31a]
69 kevent + 10 (in libsystem_kernel.dylib) [0x7fff947207e6]
Kernel stack:
69 kqueue_scan + 416 (in mach_kernel) [0xffffff800053aec0]
Thread 0x1c8 DispatchQueue 6
User stack:
69 _dispatch_sig_thread + 45 (in libdispatch.dylib) [0x7fff93a81b20]
69 __sigsuspend_nocancel + 10 (in libsystem_kernel.dylib) [0x7fff94720022]
Kernel stack:
69 wakeup + 992 (in mach_kernel) [0xffffff8000555880]
Binary Images:
0x101c6d000 - 0x101c6efff autofsd ??? (???) <A02D5E70-1BB1-30ED-A699-375CB0CCE901> /usr/libexec/autofsd
0x7fff93a7d000 - 0x7fff93a8bfff libdispatch.dylib ??? (???) <1D5BE322-A9B9-3BCE-8FAC-076FB07CF54A> /usr/lib/system/libdispatch.dylib
0x7fff94709000 - 0x7fff94729fff libsystem_kernel.dylib ??? (???) <185823F1-409E-3AFD-93A9-C214013C17C8> /usr/lib/system/libsystem_kernel.dylib
Process: automountd [2351]
Path: /usr/libexec/automountd
Architecture: x86_64
UID: 0
Thread 0x312df DispatchQueue 1
User stack:
69 ??? (in automountd) [0x1068d4680]
69 ??? (in automountd) [0x1068d6570]
69 __semwait_signal + 10 (in libsystem_kernel.dylib) [0x7fff9471fe42]
Kernel stack:
69 semaphore_wait_continue + 0 (in mach_kernel) [0xffffff8000234650]
Thread 0x312e9 DispatchQueue 2
User stack:
69 _dispatch_mgr_thread + 54 (in libdispatch.dylib) [0x7fff93a7f31a]
69 kevent + 10 (in libsystem_kernel.dylib) [0x7fff947207e6]
Kernel stack:
69 kqueue_scan + 416 (in mach_kernel) [0xffffff800053aec0]
Thread 0x312e1
User stack:
69 thread_start + 13 (in libsystem_c.dylib) [0x7fff8cb19b75]
69 _pthread_start + 335 (in libsystem_c.dylib) [0x7fff8cb168bf]
69 ??? (in automountd) [0x1068d6682]
69 __sigwait + 10 (in libsystem_kernel.dylib) [0x7fff94720036]
Kernel stack:
69 hndl_unix_scall64 + 19 (in mach_kernel) [0xffffff80002daea3]
69 unix_syscall64 + 507 (in mach_kernel) [0xffffff80005cdecb]
69 __sigwait_nocancel + 333 (in mach_kernel) [0xffffff800055381d]
69 msleep + 119 (in mach_kernel) [0xffffff8000555c07]
69 wakeup + 267 (in mach_kernel) [0xffffff80005555ab]
69 lck_mtx_sleep + 74 (in mach_kernel) [0xffffff8000227efa]
69 thread_block_reason + 299 (in mach_kernel) [0xffffff800022f42b]
69 thread_continue + 1661 (in mach_kernel) [0xffffff800022f1ad]
69 machine_switch_context + 361 (in mach_kernel) [0xffffff80002c2939]
Thread 0x312e2
User stack:
69 thread_start + 13 (in libsystem_c.dylib) [0x7fff8cb19b75]
69 _pthread_start + 335 (in libsystem_c.dylib) [0x7fff8cb168bf]
69 ??? (in automountd) [0x1068d678d]
69 __psynch_cvwait + 10 (in libsystem_kernel.dylib) [0x7fff9471fbca]
Kernel stack:
69 psynch_cvcontinue + 0 (in mach_kernel) [0xffffff800059e320]
Thread 0x312e3
User stack:
69 thread_start + 13 (in libsystem_c.dylib) [0x7fff8cb19b75]
69 _pthread_start + 335 (in libsystem_c.dylib) [0x7fff8cb168bf]
69 ??? (in automountd) [0x1068de85c]
69 __psynch_cvwait + 10 (in libsystem_kernel.dylib) [0x7fff9471fbca]
Kernel stack:
69 psynch_cvcontinue + 0 (in mach_kernel) [0xffffff800059e320]
Thread 0x312e4
User stack:
69 thread_start + 13 (in libsystem_c.dylib) [0x7fff8cb19b75]
69 _pthread_start + 335 (in libsystem_c.dylib) [0x7fff8cb168bf]
69 ??? (in automountd) [0x1068d6839]
FBIent wrote:
it is but it still spikes...all my logic files are on the external drive and still i get a spike. usually when im playing back a track. (hitting play...then it spikes)
I just looked at a small project with 8 audio tracks 44.1kHz at 24 bits.
When I start the project my disk meter pegs to the red, the reason is.... Logic is not only reading the file for playback it's reading ahead and filling the audio buffers which have been greatly increased in later version of Logic.
Possibilities...
-As AD2 pointed out, check your disk format, some external disks come PC formatted.
-Your recording format 44.1, 48, 88.2 or 96kHz 16 or 24 bit?
-Are any samples used on other tracks being pulled off a drive?
Disk acces spikes are not that big a deal..
Maybe you are looking for
-
How to delete a prerecodered file from mediant 1000
Hi! I want previously to excuse, my English is not perfect, And sorry if i write to wrong part of forum. Following the advices from this theme I have installed a prerecodered file in our Mediant 1000 http://social.microsoft.com/Forums/en-US/communica
-
How can I import passwords and usernames from Google Chrome into FireFox using Mac OSX?
All of my passwords are in the Google Chrome browser, but I want to use Firefox as adblock plus is better for firefox. How can I import my firefox passwords & usernames in OSX easily?
-
Can I distribute an MP4 video through an enterprise app store?
This would be as a standalone MP4 file, not as part of an app. Which non-app content types can be deployed in-house within an iOS enterprise app store (i.e. PDF files)? Thank you, - TomR2
-
Hi , I need help . I need to communicate from applet to java script in the same page . the only thing i came across is netscape.javascript.JSObject which gives access to DOM object . but this thing does not work with MAc system . i am using power MAc
-
HR TEM - replace Attendee in the background
Hi Experts, We are on SAP 4.7. We have a requirement to automate the Replace Attendee process(T code PV03) in TEM. I need to ask, if there is any standard function module or BAPI like we have for Booking (BAPI_BOOK_ATTENDANCE) and for pre booking (B