IPhone: Memory Management / Tracking Tools
I am new to Mac/iPhone programming but have 20+ years in Windows. I am not familiar with the tools but MS Dev Studio will show memory leaks as the app shuts down. Is there a similar switch to turn on for xcode? I am having trouble with the gestalt of memory management on this platform. For example, I know this is bad code style but is there a leak here?
myLabel.text = [@"Hello, World. " stringByAppendingString: myTextField.text];
Thanks,
Todd
I found section four of this document incredibly useful.
Broadly speaking, if you create an object using "alloc" you need to manually clean up afterwards, otherwise it will be autoreleased and you won't get a memory leak.
XCode comes with Instruments which allows you to track down leaks (among other things).
Cheers,
--> Stephen
Similar Messages
-
Solution manager-third party tracking tools conectivity
Hi All,
How to connect solution manger to third party issue tracking tools to get fake data in solution manager and update the same?
Thanks in advance
vasumathiHi Murali Narayanan
If you wan to achieve monitoring from technical perspective, the way that was introduced by shivjansi might be the option.
If you want to check the entry of specific table in stand alone MSSQL to ensure the business process that use MSSQL
stand alone DB, you can use BPMon remote DB monitoring that enables monitoring of non ABAP/ non SAP that supported
by netweaver like MSSQL, Oracle, DB2.
By using this function, you can monitor the entry of your stand alone SQL server.
For example, stand alone SQL Server has some table that contains some error,
or there is application table and in one row that it indicates error or completeness.
Now if you want to check these error document or incomplete document in the DB,
you can use BPMon remote DB monitor.
By monitoring this, you can ensure whether there is issue in your business or not.
You can find out how to setup from following link.
http://service.sap.com/bpm
->technical detail ->Setup Guide for non-ABAP/non-SAP
P14 (The monitoring object u201CGeneric Table Entry Counter for remote DBu201D (NATABCNX) )
is related description.
(In the document, it also introduce some other way using web service).
Also in same link, you can find out other document like how to setup BPMon.
Also there is some blog about table entry counter. it is for SAP ABAP system.
But the function is more or less same for remote DB.
So you can also check following blog to have more understandable image.
/people/volker.vongloeden/blog/2010/07/16/create-your-own-customer-specific-key-figure-for-business-process-monitoring-within-5-minutes
Best Regards
Keiji -
RE: (forte-users) memory management
Brenda,
When a partition starts, it reserves the MinimumAllocation. Within this
memory space, objects are created and more and more of this memory is
actually used. When objects are no longer referenced, they remain in memory
and the space they occupy remains unusable.
When the amount of free memory drops below a certain point, the garbage
collector kicks in, which will free the space occopied by all objects that
are no longer referenced.
If garbage collecting can't free enough memory to hold the additional data
loaded into memory, then the partition will request another block of memory,
equal to the IncrementAllocation size. The partition will try to stay within
this new boundary by garbage collecting everytime the available part of this
memory drops below a certain point. If the partition can't free enough
memory, it will again request another block of memory.
This process repeats itself until the partition reaches MaximumAllocation.
If that amount of memory still isn't enough, then the partition crashes.
Instrument ActivePages shows the memory reserved by the partition.
AllocatedPages shows the part of that memory actually used.
AvailablePages shows the part ot that memory which is free.
Note that once memory is requested from the operating system, it's never
released again. Within this memory owned by the partition, the part actually
used will always be smaller. But this part will increase steadily, until the
garbage collecter is started and a part of it is freed again.
There are some settings that determine when the garbage collector is
started, but I'm not sure which ones they are.
The garbage collector can be started from TOOL using
"task.Part.OperatingSystem.RecoverMemory()", but I'm not sure if that will
always actually start the garbage collector.
If you track AllocatedPages of a partition, it's always growing, even if the
partition isn't doing anything. I don't know why.
If you add AllocatedPages and AvailablePages, you shoud get the value of
ActivePages, but you won't. You always get a lower number and sometimes even
considerably lower. I don't know why.
Pascal Rottier
Atos Origin Nederland (BAS/West End User Computing)
Tel. +31 (0)10-2661223
Fax. +31 (0)10-2661199
E-mail: Pascal.Rottiernl.origin-it.com
++++++++++++++++++++++++++++
Philip Morris (Afd. MIS)
Tel. +31 (0)164-295149
Fax. +31 (0)164-294444
E-mail: Rottier.Pascalpmintl.ch
-----Original Message-----
From: Brenda Cumming [mailto:brenda_cummingtranscanada.com]
Sent: Tuesday, January 23, 2001 6:40 PM
To: Forte User group
Subject: (forte-users) memory management
I have been reading up on memory management and the
OperatingSystemAgent, and could use some clarification...
When a partition is brought online, is the ActivePages value set to the
MinimumAllocation value, and expanded as required?
And what is the difference between the ExpandAtPercent and
ContractAtPercent functions?
Thanks in advance,
Brenda
For the archives, go to: http://lists.xpedior.com/forte-users and use
the login: forte and the password: archive. To unsubscribe, send in a new
email the word: 'Unsubscribe' to: forte-users-requestlists.xpedior.comThe Forte runtime is millions of lines of compiled C++ code, packaged into
shared libraries (DLL's) which are a number of megabytes in size. The
space is taken by the application binary, plus the loaded DLL's, plus
whatever the current size of garbage collected memory is.
Forte allocates a garbage-collected heap that must be bigger than the size
of the allocated objects. So if you start with an 8MB heap, you will always
have at least 8MB allocated, no matter what objects you actually
instantiate. See "Memory Issues" in the Forte System Management Guide.
-tdc
Tom Childers
iPlanet Integration Server Engineering
At 10:37 PM 6/11/01 +0200, [email protected] wrote:
Hi all,
I was wondering if anyone had any experience in deploying clients on NT
concerning
the memory use of these client apps.
What is the influence of the various compiler options (optimum
performance, memory use etc)?
We seem to see a lot of the memory is taken by the Forte client apps (seen
in the Task Manager
of NT) in respect to the other native Window apps. For example an
executable of approx 4Mb takes up to
15Mb of memory. When I look at the objects retained in memory after
garbage collection, these are about
2Mb. Where do the other Mb's come from? -
Can I use my iphone as a tracking Device??
Hi, all out there.!
I just bought the new iphone 3G
This iphone is great and one of the best ever of all the time,
I'm a menufacturing engineer, I used several devices and many computers
in the past and I haven't seen nothing like it.
This is my toy I was waiting for.!!
I've had downloaded several applications already, which they're amazing.
all you can do with your iphone it's amazing.!!
THERE IS ONLY ONE THING, I'M WONDERING IF I CAN DO IT.
It should be able to do it, It has all the tools, I just I haven't seen it.
I'm thinking like a little application that can be used as
TRACKING DEVICE.!!
Can I use my iphone as a TRACKING DEVICE??
Any body knows out there?
How? or where is this application??
DEVELOPERS OUT THERE.!
Can you develop one if there isn't any??
Please, let me know as soon as you can.
Thanks in advance.Hi, Jim.
Thanks for your info.
the second link works now.
I kept trying the first link but I kept getting the same message,
not be able open page becuase invalid address.
Anyways,
Second QUESTION?
Is that software could be use to track a second iphone?
see, I have two iphones and I want to give one to my crazy son,
to track him what **** he's doing.
I know there are seperate devices that I can do that only., but
since I have two iphones already, I don't see a reason why to spend more
money if with the iphones that laready have I can do the same thing.
Please, let me know if that would work or
if there is something else available for that.
Thanks so much again. -
I will have several questions about memory management,
garbage collection by Flash.
First of all can anyone explain what is the link between the
memory usage of the profiler and the System.totalMemory value.
I use a module to display the totalMemory value evolution
with a timeline chart (get the totalMemory value every 0.5 second
and keeping only last 300 values).
Here what I get : after about 4 hours of time running, the
memory usage peak is about 24 Mbytes, BUT the System.totalMemory is
about 600 Mbytes !!
Before trying to understand why I have this memory
consumption, I would like to understand the difference between what
the profiler is measuring (24 Mbytes) and the memory used by the
Flash Player (600 Mbytes).
ThanksThis is a loaded question but let me try to take a stab at it:
First, let's right away eliminate the 'Minimize Application' issue; the memory that goes way down to 1 meg is the actual Real Memory being used by the Application, by minimizing it, you are putting all the application memory space into the Windows swap file. When you restore the application, then you will see the value grow again back to where it was by taking the swapped out pages back into real memory.
The difference between the memory profiler and the task manager could be drastic in terms of consumption, the memory profiler is tracking only the java objects allocated and freed by your application, the task manager is look at the Windows Process as a whole, which contains a Virtual Machine that needs memory to store loaded classes, internal data and application heap (which are the actual java objects). The application heap will be usually far bigger than the cumulative total number of objects in your application.
A usual way to use the memory profiler is to, by running it on your application, take a snapshot of the memory before an expensive operation, perform the operation, then take a snapshot again and see what is left to make sure no leaks are being created.
In order to find out why your expensive operation is so... expensive, is to increase the granularity of the operation up to a point where you will get to the few sections of code that allocate all that memory.
Hope that helps,
Michel -
Fatal Internal Error: "Memory Manager.cpp", line 547
Hello,
I am using LV 2009 and I am also getting an error as follows:
=======================================================
Fatal Internal Error: "Memory Manager.cpp", line 547
LabVIEW version 9.0.1
You will lose any unsaved work. For assistance in resolving this problem, please relaunch LabVIEW, or contact National Instruments.
=======================================================
I get this error when I start executing steps on TS 4.2.1 as well as when I do "Unload All Modules" in TS. Please find the attched logs. Further, I could not run anything in TS and need to restart the PC to re-run the sequence after everytime this error occurs.
We have transited through LV 8.0, 8.2, 8.5 and now 2009 over past 4 years for our project and this is the first time I could see this error.
Please help.
Thanks.
Attachments:
lvlog2010-06-09-10-06-07.txt 2 KB
lvlog2010-06-09-18-52-36.txt 1 KB
lvlog2010-06-09-19-16-20.txt 2 KBAdding on to Pritam's post:
For the earlier "Fatal Internal Error: "Memory Manager.cpp", line 547" , we found that a couple of our dll's which were developed in LV 8.5.1 had not been recompiled in LV2009. After recompiling each of them in LV2009, and then running the same sequences in TestStand,this error vanished.
But now again we're seeing this error, and that too only on 3 PCs systems out of 5 PCs!
The same installer has been installed on all 5 sytems (after removing the earlier installers and running MSI Blast.exe them).
The error now appears again, only when we try to exit TestExec.exe and another tool built in LabVIEW.
So everything works fine and tasks are performed,etc, but when we close the window or try the exit that program, the "Fatal Internal Error: "Memory Manager.cpp", line 547" pops up.
If we say "OK" to it, the window closes, but the Task is seen still running in the Task Manager and has to be manually terminated (End Task).
Does anyone know what could be going wrong? -
Data Backup 2.1 and Mac Memory Management?
I'm trialing a backup program called Data Backup 2.1. It keeps versions of my programs, which I need, as often I've had corruptions and have not notice this till a few days after the fact. I've been using Retrospect but read a review that praised Data Backup. The thing I've noticed with it is that although it is very fast, like SuperDuper, it seems to affect my free memory dramatically. I've noticed that it will finish and instead of having say 250 megs of Active memory in use I'll have 700 megs of active memory. Inactive will be low whereas normally its high. Free memory during its backup can drop to 20 megs (I have 1.5 gigs). The free memory, once you start to use your computer seems to recover to around 500 - 700 megs. The one thing I have noticed of concern is that while its running I get pageouts, which I never get and my reading about Mac memory management is you want to avoid pageouts and if you get them you need more memory (for what I'm doing 1.5 gigs should be plenty). I've asked the Data Backup people what's going on and they don't think its something to be concerned about but they said it is probably something to do with the way they are caching.
I'm just wondering - do you think this is something to be concerned about. I'd like to switch from Retrospect as although I know it I'm not sure how committed they are to the Mac market any longer and it is way slower in terms of activities but it does manage memory well. However I don't want to get Data Backup if it is affecting RAM inappropriately.
KerrySynchronize! Pro X will maintain versioned archives, perform full, incremental, and bootable backups both to local and to network devices. I have found that SPX is just about as full-featured as Retrospect with certain limitations. It cannot backup across multiple media (CDs, DVDs, tape), no extensive browser windows like Retrospect, no backups without scanning (as SuperDuper does for its "fast" updating backup.
SPX supports schedules, multiple-item backups (can select individual files and/or folders), extensive backup/synchronize customizations, can run as "root", can auto-mount devices (including network drives), and it's a universal binary.
It's also nearly as expensive as Retrospect but in my opinion it's worth it.
If you want a less costly backup solution without all the features of SPX, but with all the features of SuperDuper (and in my opinion better than SD) then try Deja Vu. Also a universal binary, it supports incremental archives, full, incremental, and bootable backups to local or network drives, supports scheduling and runs as a preference pane.
Finally, for the the truly cheap there are PsyncX and RsyncX - both freeware. They are GUI wrappers around the basic backup and synchronizing tools that are part of Unix (ditto, rsync, and psync.)
Download mentioned software from www.versiontracker.com or www.macupdate.com.
Why reward points?(Quoted from Discussions Terms of Use.)
The reward system helps to increase community participation. When a community member gives you (or another member) a reward for providing helpful advice or a solution to their question, your accumulated points will increase your status level within the community.
Members may reward you with 5 points if they deem that your reply is helpful and 10 points if you post a solution to their issue. Likewise, when you mark a reply as Helpful or Solved in your own created topic, you will be awarding the respondent with the same point values. -
IPhoto Memory Management Issue?!
I've been having an issue with trying to import Photos with iPhoto 9.21 for some time now and finally decided to try to figure out what's going on. Config: Mac Pro 1.1, 5 gigs RAM, 250 Gig, 500 Gig x 2 (RAID 1) where iTunes and iPhoto reside, 160 Gig for Time Machine, OSX Lion.
I believe this issue is due to a lack of memory management. Our iPhoto library is approximately 40 gigabytes and will crash when trying to import even small quantities of images/video. I've run disk permissions, deleted plists, etc. I have noticed that iphoto will use all of the available RAM on the computer when it's running.
I figured I'd try rebuilding the library using iPhoto Library Manager and while that was running, I was watching memory usage while the rebuild process was going and over time more memory was getting used. The rebuilt library hit around 27.5 gigs when I ran out of free memory and iPhoto quit.
The next step was to create a new library and try importing photos and videos again. Started with a mix of files from my iphone 4S and then RAW and jpeg files from a Canon (18 megapixel) and they all imported without issue. The same files would crash iphoto in the original library.
Adding another 4 gigs of RAM to the computer to see if that rectifies the problem assuming it doesn't get sucked dry on a 40 gig library! I'll update the post after I get the RAM installed and can try importing into the main library.
JohnFinished rebuilding the library per Fix #1. Tried to import 48 RAW files and it crashed while in process. Again, the RAM Free RAM was gone! Here's the crash report:
Process: iPhoto [706]
Path: /Applications/iPhoto.app/Contents/MacOS/iPhoto
Identifier: com.apple.iPhoto
Version: 9.2.1 (9.2.1)
Build Info: iPhotoProject-628000000000000~1
App Item ID: 408981381
App External ID: 4641130
Code Type: X86 (Native)
Parent Process: launchd [152]
Date/Time: 2012-01-28 15:52:26.203 -0800
OS Version: Mac OS X 10.7.2 (11C74)
Report Version: 9
Interval Since Last Report: 182337 sec
Crashes Since Last Report: 8
Per-App Interval Since Last Report: 21333 sec
Per-App Crashes Since Last Report: 8
Anonymous UUID: F900FBFC-BDD3-4299-ADFF-5CC409100C51
Crashed Thread: 44 Import thread 1
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x00000000001568b2
VM Regions Near 0x1568b2:
shared memory 0000000000002000-0000000000003000 [ 4K] rw-/rw- SM=SHM
-->
MALLOC_SMALL 0000000004458000-0000000004800000 [ 3744K] rw-/rwx SM=PRV
Thread 0:: Dispatch queue: com.apple.main-thread
0 libsystem_kernel.dylib 0x9b7d0c22 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x9b7d01f6 mach_msg + 70
2 com.apple.CoreFoundation 0x9abbf0ea __CFRunLoopServiceMachPort + 170
3 com.apple.CoreFoundation 0x9abc8214 __CFRunLoopRun + 1428
4 com.apple.CoreFoundation 0x9abc78ec CFRunLoopRunSpecific + 332
5 com.apple.CoreFoundation 0x9abc7798 CFRunLoopRunInMode + 120
6 com.apple.HIToolbox 0x9b863a7f RunCurrentEventLoopInMode + 318
7 com.apple.HIToolbox 0x9b86ad9b ReceiveNextEventCommon + 381
8 com.apple.HIToolbox 0x9b86ac0a BlockUntilNextEventMatchingListInMode + 88
9 com.apple.AppKit 0x901bc040 _DPSNextEvent + 678
10 com.apple.AppKit 0x901bb8ab -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 113
11 com.apple.AppKit 0x901b7c22 -[NSApplication run] + 911
12 com.apple.AppKit 0x9044c18a NSApplicationMain + 1054
13 ??? 0x0001159a 0 + 71066
14 ??? 0x00010a29 0 + 68137
Thread 1:: Dispatch queue: com.apple.libdispatch-manager
0 libsystem_kernel.dylib 0x9b7d2b5e __select_nocancel + 10
1 libdispatch.dylib 0x938e6b11 _dispatch_mgr_invoke + 642
2 libdispatch.dylib 0x938e56a7 _dispatch_mgr_thread + 53
Thread 2:
0 libsystem_kernel.dylib 0x9b7d283e __psynch_cvwait + 10
1 libsystem_c.dylib 0x9bc7be78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x9bc7bf7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x9c6fa507 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9c6c092a -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9c6c07fe -[NSConditionLock lockWhenCondition:] + 69
6 ??? 0x01759702 0 + 24483586
7 ??? 0x017586b0 0 + 24479408
8 com.apple.Foundation 0x9c6c7f7d -[NSThread main] + 45
9 com.apple.Foundation 0x9c6c7f2d __NSThread__main__ + 1582
10 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
11 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 3:
0 libsystem_kernel.dylib 0x9b7d0c22 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x9b7d01f6 mach_msg + 70
2 com.apple.CoreFoundation 0x9abbf0ea __CFRunLoopServiceMachPort + 170
3 com.apple.CoreFoundation 0x9abc8214 __CFRunLoopRun + 1428
4 com.apple.CoreFoundation 0x9abc78ec CFRunLoopRunSpecific + 332
5 com.apple.CoreFoundation 0x9abc7798 CFRunLoopRunInMode + 120
6 com.apple.Foundation 0x9c674607 -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 273
7 ??? 0x0175aaed 0 + 24488685
8 com.apple.Foundation 0x9c6c7f7d -[NSThread main] + 45
9 com.apple.Foundation 0x9c6c7f2d __NSThread__main__ + 1582
10 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
11 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 4:
0 libsystem_kernel.dylib 0x9b7d0c22 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x9b7d01f6 mach_msg + 70
2 com.apple.CoreFoundation 0x9abbf0ea __CFRunLoopServiceMachPort + 170
3 com.apple.CoreFoundation 0x9abc8214 __CFRunLoopRun + 1428
4 com.apple.CoreFoundation 0x9abc78ec CFRunLoopRunSpecific + 332
5 com.apple.CoreFoundation 0x9abc7798 CFRunLoopRunInMode + 120
6 com.apple.Foundation 0x9c674607 -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 273
7 ??? 0x0175aaed 0 + 24488685
8 com.apple.Foundation 0x9c6c7f7d -[NSThread main] + 45
9 com.apple.Foundation 0x9c6c7f2d __NSThread__main__ + 1582
10 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
11 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 5:
0 libsystem_kernel.dylib 0x9b7d283e __psynch_cvwait + 10
1 libsystem_c.dylib 0x9bc7be78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x9bc7bf7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x9c6fa507 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9c6c092a -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9c6c07fe -[NSConditionLock lockWhenCondition:] + 69
6 ??? 0x01759702 0 + 24483586
7 ??? 0x017586b0 0 + 24479408
8 com.apple.Foundation 0x9c6c7f7d -[NSThread main] + 45
9 com.apple.Foundation 0x9c6c7f2d __NSThread__main__ + 1582
10 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
11 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 6:
0 libsystem_kernel.dylib 0x9b7d283e __psynch_cvwait + 10
1 libsystem_c.dylib 0x9bc7be78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x9bc7bf7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x9c6fa507 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9c6c092a -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9c6c07fe -[NSConditionLock lockWhenCondition:] + 69
6 ??? 0x01759702 0 + 24483586
7 ??? 0x017586b0 0 + 24479408
8 com.apple.Foundation 0x9c6c7f7d -[NSThread main] + 45
9 com.apple.Foundation 0x9c6c7f2d __NSThread__main__ + 1582
10 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
11 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 7:
0 libsystem_kernel.dylib 0x9b7d283e __psynch_cvwait + 10
1 libsystem_c.dylib 0x9bc7be78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x9bc7bf7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x9c6fa507 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9c6c092a -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9c6c07fe -[NSConditionLock lockWhenCondition:] + 69
6 ??? 0x01759702 0 + 24483586
7 ??? 0x017586b0 0 + 24479408
8 com.apple.Foundation 0x9c6c7f7d -[NSThread main] + 45
9 com.apple.Foundation 0x9c6c7f2d __NSThread__main__ + 1582
10 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
11 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 8:
0 libsystem_kernel.dylib 0x9b7d283e __psynch_cvwait + 10
1 libsystem_c.dylib 0x9bc7be78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x9bc7bf7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x9c6fa507 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9c6c092a -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9c6c07fe -[NSConditionLock lockWhenCondition:] + 69
6 ??? 0x01759702 0 + 24483586
7 ??? 0x017586b0 0 + 24479408
8 com.apple.Foundation 0x9c6c7f7d -[NSThread main] + 45
9 com.apple.Foundation 0x9c6c7f2d __NSThread__main__ + 1582
10 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
11 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 9:
0 libsystem_kernel.dylib 0x9b7d0c22 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x9b7d01f6 mach_msg + 70
2 com.apple.CoreFoundation 0x9abbf0ea __CFRunLoopServiceMachPort + 170
3 com.apple.CoreFoundation 0x9abc8214 __CFRunLoopRun + 1428
4 com.apple.CoreFoundation 0x9abc78ec CFRunLoopRunSpecific + 332
5 com.apple.CoreFoundation 0x9abc7798 CFRunLoopRunInMode + 120
6 com.apple.Foundation 0x9c674607 -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 273
7 ??? 0x0175aaed 0 + 24488685
8 com.apple.Foundation 0x9c6c7f7d -[NSThread main] + 45
9 com.apple.Foundation 0x9c6c7f2d __NSThread__main__ + 1582
10 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
11 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 10:
0 libsystem_kernel.dylib 0x9b7d283e __psynch_cvwait + 10
1 libsystem_c.dylib 0x9bc7be78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x9bc7bf7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x9c6fa507 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9c6c092a -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9c6c07fe -[NSConditionLock lockWhenCondition:] + 69
6 ??? 0x01759702 0 + 24483586
7 ??? 0x017586b0 0 + 24479408
8 com.apple.Foundation 0x9c6c7f7d -[NSThread main] + 45
9 com.apple.Foundation 0x9c6c7f2d __NSThread__main__ + 1582
10 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
11 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 11:
0 libsystem_kernel.dylib 0x9b7d283e __psynch_cvwait + 10
1 libsystem_c.dylib 0x9bc7be78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x9bc7bf7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x9c6fa507 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9c6c092a -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9c6c07fe -[NSConditionLock lockWhenCondition:] + 69
6 ??? 0x01759702 0 + 24483586
7 ??? 0x017586b0 0 + 24479408
8 com.apple.Foundation 0x9c6c7f7d -[NSThread main] + 45
9 com.apple.Foundation 0x9c6c7f2d __NSThread__main__ + 1582
10 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
11 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 12:
0 libsystem_kernel.dylib 0x9b7d283e __psynch_cvwait + 10
1 libsystem_c.dylib 0x9bc7be78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x9bc7bf7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x9c6fa507 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9c6c092a -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9c6c07fe -[NSConditionLock lockWhenCondition:] + 69
6 ??? 0x01759702 0 + 24483586
7 ??? 0x017586b0 0 + 24479408
8 com.apple.Foundation 0x9c6c7f7d -[NSThread main] + 45
9 com.apple.Foundation 0x9c6c7f2d __NSThread__main__ + 1582
10 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
11 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 13:
0 libsystem_kernel.dylib 0x9b7d283e __psynch_cvwait + 10
1 libsystem_c.dylib 0x9bc7be78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x9bc7bf7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x9c6fa507 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9c6c092a -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9c6c07fe -[NSConditionLock lockWhenCondition:] + 69
6 ??? 0x01759702 0 + 24483586
7 ??? 0x017586b0 0 + 24479408
8 com.apple.Foundation 0x9c6c7f7d -[NSThread main] + 45
9 com.apple.Foundation 0x9c6c7f2d __NSThread__main__ + 1582
10 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
11 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 14:
0 libsystem_kernel.dylib 0x9b7d283e __psynch_cvwait + 10
1 libsystem_c.dylib 0x9bc7be78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x9bc7bf7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x9c6fa507 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9c6c092a -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9c6c07fe -[NSConditionLock lockWhenCondition:] + 69
6 ??? 0x01759702 0 + 24483586
7 ??? 0x017586b0 0 + 24479408
8 com.apple.Foundation 0x9c6c7f7d -[NSThread main] + 45
9 com.apple.Foundation 0x9c6c7f2d __NSThread__main__ + 1582
10 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
11 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 15:
0 libsystem_kernel.dylib 0x9b7d283e __psynch_cvwait + 10
1 libsystem_c.dylib 0x9bc7be78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x9bc7bf7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x9c6fa507 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9c6c092a -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9c6c07fe -[NSConditionLock lockWhenCondition:] + 69
6 ??? 0x01759702 0 + 24483586
7 ??? 0x017586b0 0 + 24479408
8 com.apple.Foundation 0x9c6c7f7d -[NSThread main] + 45
9 com.apple.Foundation 0x9c6c7f2d __NSThread__main__ + 1582
10 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
11 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 16:
0 libsystem_kernel.dylib 0x9b7d283e __psynch_cvwait + 10
1 libsystem_c.dylib 0x9bc7be78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x9bc7bf7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x9c6fa507 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9c6c092a -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9c6c07fe -[NSConditionLock lockWhenCondition:] + 69
6 ??? 0x01759702 0 + 24483586
7 ??? 0x017586b0 0 + 24479408
8 com.apple.Foundation 0x9c6c7f7d -[NSThread main] + 45
9 com.apple.Foundation 0x9c6c7f2d __NSThread__main__ + 1582
10 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
11 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 17:
0 libsystem_kernel.dylib 0x9b7d283e __psynch_cvwait + 10
1 libsystem_c.dylib 0x9bc7be78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x9bc7bf7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x9c6fa507 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9c6c092a -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9c6c07fe -[NSConditionLock lockWhenCondition:] + 69
6 ??? 0x01759702 0 + 24483586
7 ??? 0x017586b0 0 + 24479408
8 com.apple.Foundation 0x9c6c7f7d -[NSThread main] + 45
9 com.apple.Foundation 0x9c6c7f2d __NSThread__main__ + 1582
10 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
11 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 18:
0 libsystem_kernel.dylib 0x9b7d283e __psynch_cvwait + 10
1 libsystem_c.dylib 0x9bc7be78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x9bc7bf7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x9c6fa507 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9c6c092a -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9c6c07fe -[NSConditionLock lockWhenCondition:] + 69
6 ??? 0x01759702 0 + 24483586
7 ??? 0x017586b0 0 + 24479408
8 com.apple.Foundation 0x9c6c7f7d -[NSThread main] + 45
9 com.apple.Foundation 0x9c6c7f2d __NSThread__main__ + 1582
10 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
11 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 19:
0 libsystem_kernel.dylib 0x9b7d283e __psynch_cvwait + 10
1 libsystem_c.dylib 0x9bc7be78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x9bc7bf7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x9c6fa507 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9c6c092a -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9c6c07fe -[NSConditionLock lockWhenCondition:] + 69
6 ??? 0x01759702 0 + 24483586
7 ??? 0x017586b0 0 + 24479408
8 com.apple.Foundation 0x9c6c7f7d -[NSThread main] + 45
9 com.apple.Foundation 0x9c6c7f2d __NSThread__main__ + 1582
10 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
11 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 20:
0 libsystem_kernel.dylib 0x9b7d283e __psynch_cvwait + 10
1 libsystem_c.dylib 0x9bc7be78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x9bc7bf7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x9c6fa507 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9c6c092a -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9c6c07fe -[NSConditionLock lockWhenCondition:] + 69
6 ??? 0x01759702 0 + 24483586
7 ??? 0x017586b0 0 + 24479408
8 com.apple.Foundation 0x9c6c7f7d -[NSThread main] + 45
9 com.apple.Foundation 0x9c6c7f2d __NSThread__main__ + 1582
10 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
11 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 21:
0 libsystem_kernel.dylib 0x9b7d283e __psynch_cvwait + 10
1 libsystem_c.dylib 0x9bc7be78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x9bc7bf7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x9c6fa507 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9c6c092a -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9c6c07fe -[NSConditionLock lockWhenCondition:] + 69
6 ??? 0x01759702 0 + 24483586
7 ??? 0x017586b0 0 + 24479408
8 com.apple.Foundation 0x9c6c7f7d -[NSThread main] + 45
9 com.apple.Foundation 0x9c6c7f2d __NSThread__main__ + 1582
10 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
11 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 22:
0 libsystem_kernel.dylib 0x9b7d283e __psynch_cvwait + 10
1 libsystem_c.dylib 0x9bc7be78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x9bc7bf7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x9c6fa507 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9c6c092a -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9c6c07fe -[NSConditionLock lockWhenCondition:] + 69
6 ??? 0x01759702 0 + 24483586
7 ??? 0x017586b0 0 + 24479408
8 com.apple.Foundation 0x9c6c7f7d -[NSThread main] + 45
9 com.apple.Foundation 0x9c6c7f2d __NSThread__main__ + 1582
10 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
11 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 23:
0 libsystem_kernel.dylib 0x9b7d283e __psynch_cvwait + 10
1 libsystem_c.dylib 0x9bc7be78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x9bc7bf7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x9c6fa507 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9c6c092a -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9c6c07fe -[NSConditionLock lockWhenCondition:] + 69
6 ??? 0x01759702 0 + 24483586
7 ??? 0x017586b0 0 + 24479408
8 com.apple.Foundation 0x9c6c7f7d -[NSThread main] + 45
9 com.apple.Foundation 0x9c6c7f2d __NSThread__main__ + 1582
10 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
11 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 24:
0 libsystem_kernel.dylib 0x9b7d0c22 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x9b7d01f6 mach_msg + 70
2 ??? 0x0184bf41 0 + 25476929
3 ??? 0x0184bdc9 0 + 25476553
4 com.apple.Foundation 0x9c6c7f7d -[NSThread main] + 45
5 com.apple.Foundation 0x9c6c7f2d __NSThread__main__ + 1582
6 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
7 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 25:
0 libsystem_kernel.dylib 0x9b7d0c22 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x9b7d01f6 mach_msg + 70
2 ??? 0x0184bf41 0 + 25476929
3 ??? 0x0184bdc9 0 + 25476553
4 com.apple.Foundation 0x9c6c7f7d -[NSThread main] + 45
5 com.apple.Foundation 0x9c6c7f2d __NSThread__main__ + 1582
6 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
7 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 26:
0 libsystem_kernel.dylib 0x9b7d283e __psynch_cvwait + 10
1 libsystem_c.dylib 0x9bc7be78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x9bc7bf7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x9c6fa507 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9c6c092a -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9c6c07fe -[NSConditionLock lockWhenCondition:] + 69
6 ??? 0x01d35ac1 0 + 30628545
7 com.apple.CoreFoundation 0x9ac2f53a -[NSObject performSelector:] + 58
8 ??? 0x01763626 0 + 24524326
9 com.apple.CoreFoundation 0x9ac27091 -[NSObject performSelector:withObject:] + 65
10 ??? 0x0175acb5 0 + 24489141
11 ??? 0x0175a406 0 + 24486918
12 ??? 0x01759f55 0 + 24485717
13 ??? 0x017586c6 0 + 24479430
14 com.apple.Foundation 0x9c6c7f7d -[NSThread main] + 45
15 com.apple.Foundation 0x9c6c7f2d __NSThread__main__ + 1582
16 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
17 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 27:
0 libsystem_kernel.dylib 0x9b7d283e __psynch_cvwait + 10
1 libsystem_c.dylib 0x9bc7be78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x9bc7bf7b pthread_cond_timedwait_relative_np + 47
3 com.apple.CoreServices.CarbonCore 0x944385a3 TSWaitOnConditionTimedRelative + 178
4 com.apple.CoreServices.CarbonCore 0x94438319 TSWaitOnSemaphoreCommon + 490
5 com.apple.CoreServices.CarbonCore 0x9443812a TSWaitOnSemaphoreRelative + 24
6 com.apple.QuickTimeComponents.component 0x91abade6 0x914ce000 + 6213094
7 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
8 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 28:
0 libsystem_kernel.dylib 0x9b7d283e __psynch_cvwait + 10
1 libsystem_c.dylib 0x9bc7be21 _pthread_cond_wait + 827
2 libsystem_c.dylib 0x9bc2c42c pthread_cond_wait$UNIX2003 + 71
3 com.apple.Foundation 0x9c6c9d40 -[NSCondition wait] + 304
4 ??? 0x0005c66a 0 + 378474
5 ??? 0x0005c5c2 0 + 378306
6 com.apple.CoreFoundation 0x9ac29e1d __invoking___ + 29
7 com.apple.CoreFoundation 0x9ac29d59 -[NSInvocation invoke] + 137
8 ??? 0x01d57e61 0 + 30768737
9 ??? 0x01d696c4 0 + 30840516
10 com.apple.CoreFoundation 0x9ac27091 -[NSObject performSelector:withObject:] + 65
11 ??? 0x01763626 0 + 24524326
12 com.apple.CoreFoundation 0x9ac27091 -[NSObject performSelector:withObject:] + 65
13 ??? 0x0175acb5 0 + 24489141
14 ??? 0x0175a406 0 + 24486918
15 ??? 0x01759f55 0 + 24485717
16 ??? 0x017586c6 0 + 24479430
17 com.apple.Foundation 0x9c6c7f7d -[NSThread main] + 45
18 com.apple.Foundation 0x9c6c7f2d __NSThread__main__ + 1582
19 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
20 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 29:
0 libsystem_kernel.dylib 0x9b7d283e __psynch_cvwait + 10
1 libsystem_c.dylib 0x9bc7be78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x9bc7bf7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x9c6fa507 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9c6c092a -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9c6c07fe -[NSConditionLock lockWhenCondition:] + 69
6 ??? 0x01759702 0 + 24483586
7 ??? 0x017586b0 0 + 24479408
8 com.apple.Foundation 0x9c6c7f7d -[NSThread main] + 45
9 com.apple.Foundation 0x9c6c7f2d __NSThread__main__ + 1582
10 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
11 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 30:: com.apple.NSURLConnectionLoader
0 libsystem_kernel.dylib 0x9b7d0c22 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x9b7d01f6 mach_msg + 70
2 com.apple.CoreFoundation 0x9abbf0ea __CFRunLoopServiceMachPort + 170
3 com.apple.CoreFoundation 0x9abc8214 __CFRunLoopRun + 1428
4 com.apple.CoreFoundation 0x9abc78ec CFRunLoopRunSpecific + 332
5 com.apple.CoreFoundation 0x9abc7798 CFRunLoopRunInMode + 120
6 com.apple.Foundation 0x9c6d421c +[NSURLConnection(NSURLConnectionReallyInternal) _resourceLoadLoop:] + 378
7 com.apple.Foundation 0x9c6c7f7d -[NSThread main] + 45
8 com.apple.Foundation 0x9c6c7f2d __NSThread__main__ + 1582
9 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
10 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 31:: com.apple.CFSocket.private
0 libsystem_kernel.dylib 0x9b7d2b42 __select + 10
1 com.apple.CoreFoundation 0x9ac16195 __CFSocketManager + 1557
2 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
3 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 32:
0 libsystem_kernel.dylib 0x9b7d0c22 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x9b7d01f6 mach_msg + 70
2 ??? 0x0184bf41 0 + 25476929
3 ??? 0x0184bdc9 0 + 25476553
4 com.apple.Foundation 0x9c6c7f7d -[NSThread main] + 45
5 com.apple.Foundation 0x9c6c7f2d __NSThread__main__ + 1582
6 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
7 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 33:: JavaScriptCore::BlockFree
0 libsystem_kernel.dylib 0x9b7d283e __psynch_cvwait + 10
1 libsystem_c.dylib 0x9bc7be21 _pthread_cond_wait + 827
2 libsystem_c.dylib 0x9bc2c3e0 pthread_cond_timedwait$UNIX2003 + 70
3 com.apple.JavaScriptCore 0x92ce09dc ***::ThreadCondition::timedWait(***::Mutex&, double) + 156
4 com.apple.JavaScriptCore 0x92ed4f03 JSC::Heap::blockFreeingThreadMain() + 323
5 com.apple.JavaScriptCore 0x92ed4f3f JSC::Heap::blockFreeingThreadStartFunc(void*) + 15
6 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
7 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 34:: jpegdecompress_MPLoop
0 libsystem_kernel.dylib 0x9b7d283e __psynch_cvwait + 10
1 libsystem_c.dylib 0x9bc7be78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x9bc2382a pthread_cond_wait + 48
3 com.apple.QuickTimeComponents.component 0x91bdccc9 0x914ce000 + 7400649
4 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
5 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 35:: jpegdecompress_MPLoop
0 libsystem_kernel.dylib 0x9b7d283e __psynch_cvwait + 10
1 libsystem_c.dylib 0x9bc7be78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x9bc2382a pthread_cond_wait + 48
3 com.apple.QuickTimeComponents.component 0x91bdccc9 0x914ce000 + 7400649
4 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
5 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 36:: jpegdecompress_MPLoop
0 libsystem_kernel.dylib 0x9b7d283e __psynch_cvwait + 10
1 libsystem_c.dylib 0x9bc7be78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x9bc2382a pthread_cond_wait + 48
3 com.apple.QuickTimeComponents.component 0x91bdccc9 0x914ce000 + 7400649
4 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
5 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 37:
0 libsystem_kernel.dylib 0x9b7d302e __workq_kernreturn + 10
1 libsystem_c.dylib 0x9bc79ccf _pthread_wqthread + 773
2 libsystem_c.dylib 0x9bc7b6fe start_wqthread + 30
Thread 38:
0 libsystem_kernel.dylib 0x9b7d2b0a __rename + 10
1 libsystem_kernel.dylib 0x9b7d1c53 rename + 25
2 com.apple.CoreFoundation 0x9ac151bc -[CFXPreferencesPropertyListSourceSynchronizer writePlistToDisk] + 1052
3 com.apple.CoreFoundation 0x9abd9ab3 -[CFXPreferencesPropertyListSourceSynchronizer synchronizeAlreadyFlocked] + 595
4 com.apple.CoreFoundation 0x9abd981e -[CFXPreferencesPropertyListSourceSynchronizer synchronize] + 526
5 com.apple.CoreFoundation 0x9ac1c88a __-[CFXPreferencesPropertyListSource synchronizeInBackgroundWithCompletionBlock:]_block_invoke_1 + 122
6 libdispatch.dylib 0x938e4e11 _dispatch_call_block_and_release + 15
7 libdispatch.dylib 0x938e6797 _dispatch_queue_drain + 224
8 libdispatch.dylib 0x938e663c _dispatch_queue_invoke + 47
9 libdispatch.dylib 0x938e5e44 _dispatch_worker_thread2 + 187
10 libsystem_c.dylib 0x9bc79b24 _pthread_wqthread + 346
11 libsystem_c.dylib 0x9bc7b6fe start_wqthread + 30
Thread 39:: CVDisplayLink
0 libsystem_kernel.dylib 0x9b7d283e __psynch_cvwait + 10
1 libsystem_c.dylib 0x9bc7be78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x9bc7bf7b pthread_cond_timedwait_relative_np + 47
3 com.apple.CoreVideo 0x953f92e8 CVDisplayLink::waitUntil(unsigned long long) + 306
4 com.apple.CoreVideo 0x953f843a CVDisplayLink::runIOThread() + 706
5 com.apple.CoreVideo 0x953f8161 _ZL13startIOThreadPv + 160
6 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
7 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 40:
0 libsystem_kernel.dylib 0x9b7d302e __workq_kernreturn + 10
1 libsystem_c.dylib 0x9bc79ccf _pthread_wqthread + 773
2 libsystem_c.dylib 0x9bc7b6fe start_wqthread + 30
Thread 41:
0 libsystem_kernel.dylib 0x9b7d302e __workq_kernreturn + 10
1 libsystem_c.dylib 0x9bc79ccf _pthread_wqthread + 773
2 libsystem_c.dylib 0x9bc7b6fe start_wqthread + 30
Thread 42:: com.apple.appkit-heartbeat
0 libsystem_kernel.dylib 0x9b7d2bb2 __semwait_signal + 10
1 libsystem_c.dylib 0x9bc2c7b9 nanosleep$UNIX2003 + 187
2 libsystem_c.dylib 0x9bc2c558 usleep$UNIX2003 + 60
3 com.apple.AppKit 0x90403be2 -[NSUIHeartBeat _heartBeatThread:] + 2399
4 com.apple.Foundation 0x9c6c7f7d -[NSThread main] + 45
5 com.apple.Foundation 0x9c6c7f2d __NSThread__main__ + 1582
6 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
7 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 43:: Import thread 0
0 libsystem_kernel.dylib 0x9b7d0c22 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x9b7d01f6 mach_msg + 70
2 com.apple.CoreFoundation 0x9abbf0ea __CFRunLoopServiceMachPort + 170
3 com.apple.CoreFoundation 0x9abc8214 __CFRunLoopRun + 1428
4 com.apple.CoreFoundation 0x9abc78ec CFRunLoopRunSpecific + 332
5 com.apple.CoreFoundation 0x9abc7798 CFRunLoopRunInMode + 120
6 com.apple.AE 0x9367024f AESendMessage + 4116
7 com.apple.ImageCapture 0x93e8c462 ICAAESendMessage + 192
8 com.apple.ImageCapture 0x93e8c112 ICACommand::SendSync() + 62
9 com.apple.ImageCapture 0x93e8c00e ICACommand::ProcessCommand() + 74
10 com.apple.ImageCapture 0x93e8def3 ICADownloadFile + 819
11 ??? 0x0029a2fb 0 + 2728699
12 ??? 0x006831de 0 + 6828510
13 ??? 0x00150aeb 0 + 1379051
14 ??? 0x001508ef 0 + 1378543
15 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
16 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 44 Crashed:: Import thread 1
0 ??? 0x001568b2 0 + 1403058
1 libobjc.A.dylib 0x9369754e _objc_rootRelease + 47
2 ??? 0x0067b2de 0 + 6795998
3 ??? 0x001512a0 0 + 1381024
4 ??? 0x001508ef 0 + 1378543
5 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
6 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 45:: Import thread 2
0 libsystem_kernel.dylib 0x9b7d283e __psynch_cvwait + 10
1 libsystem_c.dylib 0x9bc7be21 _pthread_cond_wait + 827
2 libsystem_c.dylib 0x9bc2c42c pthread_cond_wait$UNIX2003 + 71
3 ??? 0x0068446c 0 + 6833260
4 ??? 0x00683178 0 + 6828408
5 ??? 0x00150aeb 0 + 1379051
6 ??? 0x001508ef 0 + 1378543
7 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
8 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 46:: Import thread 3
0 libsystem_kernel.dylib 0x9b7d283e __psynch_cvwait + 10
1 libsystem_c.dylib 0x9bc7be21 _pthread_cond_wait + 827
2 libsystem_c.dylib 0x9bc2c42c pthread_cond_wait$UNIX2003 + 71
3 ??? 0x0068446c 0 + 6833260
4 ??? 0x00683178 0 + 6828408
5 ??? 0x00150aeb 0 + 1379051
6 ??? 0x001508ef 0 + 1378543
7 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
8 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 47:: Import thread 4
0 libsystem_kernel.dylib 0x9b7d283e __psynch_cvwait + 10
1 libsystem_c.dylib 0x9bc7be21 _pthread_cond_wait + 827
2 libsystem_c.dylib 0x9bc2c42c pthread_cond_wait$UNIX2003 + 71
3 ??? 0x0068446c 0 + 6833260
4 ??? 0x00683178 0 + 6828408
5 ??? 0x00150aeb 0 + 1379051
6 ??? 0x001508ef 0 + 1378543
7 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
8 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 48:: Import thread 5
0 libsystem_kernel.dylib 0x9b7d283e __psynch_cvwait + 10
1 libsystem_c.dylib 0x9bc7be21 _pthread_cond_wait + 827
2 libsystem_c.dylib 0x9bc2c42c pthread_cond_wait$UNIX2003 + 71
3 ??? 0x0068446c 0 + 6833260
4 ??? -
Hi!
As a former windows user and developer I was happy with its memory management ( Windows 7).
Now I decided to change, and give Mac a chance... and the only thing I have to say.. Im felling as using the old versions of windows... My machine has 8GB of ram and using it for about 2 days running 1 VM (2 GB of ram) and internet browsing gives me 15MB of free memory and 2.5GB swap file!! The system is slow as ****... Btw page outs is about 25% of page ins.
What can I do to stop that ?
Do I have to keep my ( pseudo ) Unix system rebooting? Thats a shame!
Thanks!Now I decided to change, and give Mac a chance... and the only thing I have to say.. Im felling as using the old versions of windows... My machine has 8GB of ram and using it for about 2 days running 1 VM (2 GB of ram)
Most virtual machines take the amount of memory you give them away from the Mac for the life of the virtual session. So now you are most likely down to 6GB of RAM.
and internet browsing gives me 15MB of free memory and 2.5GB swap file!! The system is slow as ****...
Since you do not indicate what kind of applications you are running (besides the 1 VM), it is difficult to guess what is consuming your memory. Some applications demand more memory than others, especially graphic/video related apps where there is a lot of data to process.
Also having 15MB of free can be considered a good thing, as the Mac is actually using all that memory you paid for. "Inactive" memory is also available to the OS. Its main difference from "Free" memory is that the operating system knows what is in the inactive memory and if the original owner asks for that memory back, the OS can give it to the original owner without requiring an expensive disk I/O.
Btw page outs is about 25% of page ins.
Since the operating system will page a program into memory, it is very typical that you will have more pageins than pageouts.
You can use tools such as
sar -g 60 100
to monitor your pageout activity once a minute for 100 minutes and see if you can correlate heavy pageout activity with the use of a specific application.
You can also use Applications -> Utilities -> Activity Monitor to monitor your programs. If you think you have found a heavy memory consumer, you can select that app, in Activity Monitor, then click on "Inspect", then "Statistics" and that will show you the paging activity.
You can also use Unix commands such as 'top' and 'ps' (see "man top" and "man ps"), as well as 'vm_stat', 'iostat', etc...
Another thing. A lot of people have reported slowness when it turned out their disk was getting lots of errors. This is unlikely, but it has been know to happen. -
Mountain Lion memory management Issue !!!
Hi,
I have a MacPro Mid-2010 quad-core intel xeon with 10 gb ram.
Im an audio engineer n i use this machine extensively for my work.
I recently updated to mountain lion.
Since updating the memory management has gone from amazing (never ran out of memory even while doing extensive tasks) to crap (running out of memory all the time).
At the moment im adding a lot of tracks to itunes while simultaneously using mp3 scan+repair to fix my mp3 files.
this to me doesnt sound like anything that my MacPro should have difficulty with but its sluggish. i can still type this message easily while the other 2 tasks are on but its just feeling slow.
now when i look at istat this is what i see:
now why would there be so much inactive memory n free mem only like 10 mb with 260 page outs?
i shouldnt be getting page outs with so much inactive memory.
getting page outs means buying more memory but i dont think i need it.
im unclear about mountain lions memory management.
please advise.
Thanks.
Gautam.I'm using version 7.0.15104.778994 and having no trouble under Mountain Lion. I think that it was a July 10th release (coinciding with the GM developer release of ML).
What version do you have?
Clinton -
What is difference between 32 bit and 64 bit sql server memory management
What is difference between 32 bit and 64 bit sql server memory management
Thanks
ShashikalaThis is the basic difference...check if helps:
A 32-bit CPU running 32-bit software (also known as the x86 platform) is so named because it is based on an architecture that can manipulate values that are up to 32 bits in length. This means that a 32-bit memory pointer can store a value between 0 and
4,294,967,295 to reference a memory address. This equates to a maximum addressable space of 4GB on 32-bit platforms
On the other hand 64-bit limit of 18,446,744,073,709,551,616, this number is so large that in memory/storage terminology it equates to 16 exabytes. You don’t come across that term very often, so to help understand the scale, here is the value converted to
more commonly used measurements: 16 exabytes = 16,777,216 petabytes (16 million PB)➤ 17,179,869,184 terabytes (17 billion TB)➤ 17,592,186,044,416 gigabytes (17 trillion GB)➤
As you can see, it is significantly larger than the 4GB virtual address space usable in 32-bit systems; it’s so large in fact that any hardware capable of using it all is sadly restricted to the realm of science fiction. Because of this, processor manufacturers
decided to only implement a 44-bit address bus, which provides a virtual address space on 64-bit systems of 16TB. This was regarded as being more than enough address space for the foreseeable future and logically it’s split into an 8TB range for user mode
and 8TB for kernel mode. Each 64-bit process running on an x64 platform will be able to address up to 8TB of VAS.
Please click the Mark as answer button and vote as helpful if this reply solves your problem -
Questions about db_keep_cache_size and Automatic Shared Memory Management
Hello all,
I'm coming upon a server that I'm needing to pin a table and some objects in, per the recommendations of an application support call.
Looking at the database, which is a 5 node RAC cluster (11gr2), I'm looking to see how things are laid out:
SQL> select name, value, value/1024/1024 value_MB from v$parameter
2 where name in ('db_cache_size','db_keep_cache_size','db_recycle_cache_size','shared_pool_size','sga_max_size');
NAME VALUE VALUE_MB
sga_max_size 1694498816 1616
shared_pool_size 0 0
db_cache_size 0 0
db_keep_cache_size 0 0
db_recycle_cache_siz 0 0
e
Looking at granularity level:
SQL> select granule_size/value from v$sga_dynamic_components, v$parameter where name = 'db_block_size' and component like 'KEEP%';
GRANULE_SIZE/VALUE
2048
Then....I looked, and I thought this instance was set up with Auto Shared Mem Mgmt....but I see that sga_target size is not set:
SQL> show parameter sga
NAME TYPE VALUE
lock_sga boolean FALSE
pre_page_sga boolean FALSE
sga_max_size big integer 1616M
sga_target big integer 0
So, I'm wondering first of all...would it be a good idea to switch to Automatic Shared Memory Management? If so, is this as simple as altering system set sga_target =...? Again, this is on a RAC system, is there a different way to do this than on a single instance?
If that isn't the way to go...let me continue with the table size, etc....
The table I need to pin is:
SQL> select sum (blocks) from all_tables where table_name = 'MYTABLE' and owner = 'MYOWNER';
SUM(BLOCKS)
4858
And block size is:
SQL> show parameter block_size
NAME TYPE VALUE
db_block_size integer 8192
So, the space I'll need in memory for pinning this is:
4858 * 8192 /1024/1024 = 37.95.......which is well below my granularity mark of 2048
So, would this be as easy as setting db_keep_cache_size = 2048 with an alter system call? Do I need to set db_cache_size first? What do I set that to?
Thanks in advance for any suggestions and links to info on this.
cayenne
Edited by: cayenne on Mar 27, 2013 10:14 AM
Edited by: cayenne on Mar 27, 2013 10:15 AMJohnWatson wrote:
This is what you need,alter system set db_keep_cache_size=40M;I do not understand the arithmetic you do here,select granule_size/value from v$sga_dynamic_components, v$parameter where name = 'db_block_size' and component like 'KEEP%';it shows you the number of buffers per granule, which I would not think has any meaning.I'd been looking at some different sites studying this, and what I got from that, was that this granularity gave you the minimum you could set the db_keep_cache_size, that if you tried setting it below this value, it would be bumped up to it, and also, that each bump you gave the keep_cache, would be in increments of the granularity number....?
Thanks,
cayenne -
How to use MS Project in conjunction with a time-tracker tool
In my new job, the company is using a time-tracking tool in a very strict way.
Allow me to explain...
Let's say the project has two phases: Ph1 and Ph2.
Ph1 starts on day 1 and effort is 5 days.
Ph2 starts after Ph1 and effort is 10 days.
There are 3 resources available, R1, R2 and R3, and after a careful estimate of skills and avilability it has been decided the following:
- Ph1 is assigned to R1 from day 1 to day 5, resulting in a duration for Ph1 of 5 days.
- Ph2 is assigned to...
...R2 from day 6 to day 10
...R3 from day 8 to day 12
resulting in a duration of 7 days.
The above is mapped into the time-tracking tool to allow each resource to track time against Ph1 or Ph2 only in the aplanned timeframe. That is: R3 will be able to track
hous aganst Ph2 only from day 8 and only till day 12. That is to avoid that resources track more time that what was originally allocated: if this is necessary, it must be explained why, a new plan must be calculated and more budget must be allocated. When
the ok is given, the tasks in the time-racking tool will be changed accordingly.
If the above situation is clear, my question is: how would you model this in MS Project?
If the WBS in MSP is simply
1. Project X
1.1 Ph1
1.2. Ph2
when allocating R2 and R3 to Ph2, how can I specify that R2 will work only from day 6 to 10 and R3 from day 8 to 12?
At the moment the only clean solution I found is to go into the task usage view and adjust, for each day, the working hours of each resource assigned to the activity.
A second less clean solution is to have a WBS like follows
1. Project X
1.1 Ph1
1.2. Ph2
1.2.1 Ph2.R2
1.2.2 Ph2.R3
that is split Ph2 into two sub-activities, one for each resource.
Thanks fo any help.Thanks a lot to both of you for your suggestions.
Unfortunately the time-tracking tool cannot be changed: it is a new SAP based tool deployed worldwide.
The problem is that each project involves different teams from differnt countries for a fixed "budget" (or a fixed number of man-days). Therefore there is a global PM in London that will define in the time tracking tool
a WBS like this
1. Project X
1.1 Analysis
1.1.1 Analyse impact for team in Rome
1.1.2 Analyse impact for team in Amsterdam
1.1.3 Analyse impact fr tam in Bangkok
1.2 Development
1.2.1 Develop A
1.2.2 Develop B
1.2.3 Develop C
1.3 Customer Acceptance Test
1.3.1 Prepare test environment by team in Amsterdam
1.3.1 Test by final user
1.3.2 Support user testing by team in Rome
then he would assign the development tasks to the rsources that are supposed to work on it and for only the estimatd time. The reason is easy: he want to make sure that a resource tracks time only against the task she is supposed t work on and for only the
estimated number of days, to avoid exceeding the budget. If extra effort is required for a resource on a task, before allocating more time on that task, a long battle will start.
This we cannot change.
The problem now is on our side, the teams in Rome/Amsterdam/Bangkok: we must keep our own plan in MSP. Our tam in rome is divided in 4 sub-teams, one for each module of the core product, each team with a team
leader assiging tasks to resources with Asana. Untill las week, for months, there was not PM in Rome leading the four teams and hand and of course there was no global plan for the tasks in Rome.
My first attempt was to try with a Gantt that would stop at phases level, without going down to task level, that are under responsibility of the 4 team leaders. the reason being that we have something like
25 projects, some with dependecies with each other. I simply wanted to avoid having one huge MSP file with all projects down to task level: by experience, in my previous project (an ERP upgrade for Oracle EBS in FAO) this approach did not work very well.
But this is bringing up he problem I described: if I stop at "1.2 development" in the WBS, than when I assign R1 and R3, to mak sure their effort is planned accordingly to what has been setup in the time-raking
tool, I need to edit work in the task usage resource by resource, activity by activity.
The other option is to insert under 1.2 development another level with all tasks from Asana, each task being assigned to one resource:
1.2 Development
1.2.1 Develop A
1.2.1.1 Develop class x (by R1)
1.2.1.2 develop class y (by R3)
1.2.2 Develop C
1.2.2.1 Develop new pricing interface (by R4)
1.2.2.2 Modify all logos (by R7)
A third option would be to have one dtailed plan for each project down to the Asana task and then one higher level plan summarising all projects, down to phases only. -
Error code kernel data inpage , memory management , 0xc000021a , 0xc00000e9 on windows 8
Hi everyone I am sahasvat.I am using Acer aspire 5755. It's specification are Intel i3 3rd gen processor, 2Gb DDR 3 ram and 500 GB hdd.I am running on windows 8 OS. I opened about 4 tabs on google chrome and suddenly a blue screen with sad face displayed
an error kernel data inpage and it got restarted and after 5 mins I opened google chrome and again blue screen came and displayed an another error memory management and while restarting on bios I pressed f8 and booted to safe mode as normal
mode didn't open.soon after 20 mins I restarted my lap and I received an error 0xc000021a bios and windows booted.i then pressed power button for a min and switched on my pc but it showed a different error 0xc00000e9. I restarted many times
either 0xc000021a or 0xc00000e9 used to come not an fixed error. I don't have my cd as it got scratches on CD. Plzz help me to get out of this problem.
I can't even access my laptop and I am using my windows phone to post this.Hi everyone I am sahasvat.I am using Acer aspire 5755. It's specification are Intel i3 3rd gen processor, 2Gb DDR 3 ram and 500 GB hdd.I am running on windows 8 OS. I opened about 4 tabs on google chrome and suddenly a blue screen with sad face displayed
an error kernel data inpage and it got restarted and after 5 mins I opened google chrome and again blue screen came and displayed an another error memory management and while restarting on bios I pressed f8 and booted to safe mode as normal
mode didn't open.soon after 20 mins I restarted my lap and I received an error 0xc000021a bios and windows booted.i then pressed power button for a min and switched on my pc but it showed a different error 0xc00000e9. I restarted many times
either 0xc000021a or 0xc00000e9 used to come not an fixed error. I don't have my cd as it got scratches on CD. Plzz help me to get out of this problem.
I can't even access my laptop and I am using my windows phone to post this. -
Blue Screen of Death - Memory Management
I have gotten the blue screen of death twice now. The screen went by really fast but I think it said something about memory, like memory management. I copied the problem details:
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 4105
Additional information about the problem:
BCCode: 1a
BCP1: 0000000000041790
BCP2: FFFFFA80022B8DF0
BCP3: 000000000000FFFF
BCP4: 0000000000000000
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1
Files that help describe the problem:
C:\Windows\Minidump\071314-34335-01.dmp
C:\Users\Tiffany Jiang\AppData\Local\Temp\WER-53804-0.sysdata.xml
Both times happened randomly and about 2 weeks apart, and the laptop (Toshiba Satellite; it was bought brand new about only 3 weeks ago) still works fine after it restarts, but I don't want it to keep happening. I also don't know what the problem is. I used my previous Windows 7 laptop (HP pavillion g6) the same way for 3 years and it never blue screened even once. I tried going to the Toshiba support website to see if I need to download any new drivers but the website does not seem to be working on my laptop, everytime I go on it it's just lines of letter and numbers.
Help would be much appreciated, thank you!Satellite C55-A5195
Downloads here.
Bug Check 0x19: BAD_POOL_HEADER
Caused By Driver : vsdatant.sys <- True Vector device driver
You have ZoneAlarm on board? If so, uninstall it and see what happens.
==================================================
Dump File : 071314-34335-01.dmp
Crash Time : 7/15/2014 9:58:18 AM
Bug Check String : MEMORY_MANAGEMENT
Bug Check Code : 0x0000001a
Parameter 1 : 00000000`00041790
Parameter 2 : fffffa80`022b8df0
Parameter 3 : 00000000`0000ffff
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+75bc0
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Test\071314-34335-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
==================================================
==================================================
Dump File : 070514-42837-01.dmp
Crash Time : 7/15/2014 9:58:18 AM
Bug Check String : BAD_POOL_HEADER
Bug Check Code : 0x00000019
Parameter 1 : 00000000`00000020
Parameter 2 : fffffa80`0b390140
Parameter 3 : fffffa80`0b390160
Parameter 4 : 00000000`04020008
Caused By Driver : vsdatant.sys
Caused By Address : vsdatant.sys+47054
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Test\070514-42837-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
==================================================
-Jerry
Maybe you are looking for
-
How to make a title of region as a link to another page?
Hi there, I need to hyperlink a region title, so when I click in the title I will go to another page in the app without login agian, In other words keep the same session. Thanks, abdul Edited by: dtabed on May 12, 2009 1:40 PM
-
Hi Gururs, while end user opening query getting error. But when iam opening same query it is working successfully. He is facing shared memory error. What is the problem?How to slove the problem? Thanks in advance Ram
-
Hello there, I was just wondering where I can get hold of one of those Blackberry that are on the main page of the MyBT ^^^^^^ There it is , it has the BT logo on it and all I can find is it
-
Hi, I remember reading well before Leopard was released that there was a much hyped feature called resolution independence which was supposed to be included. Since then I haven't heard anything regarding this. On monitors at higher resolution such as
-
PLXML: How to parse given url ?
Hi, I'am working with the XML parser for PL/SQL on NT. According to your Parser API documentation it is possible to parse a given url, too: Parses xml stored in the given url/file and returns the built DOM DocumentNow, parsing from file works fine, b