OSX Poor Memory Management.
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.
Similar Messages
-
OSX inactive memory management problems
On my 2010 Macbook Air 11" running OSX 10.8 Mountain Lion, I have run into some major issues with memory management. This problem persists across both my Mac machines and multiple generations of OSX. I have a 2007 2.2 Ghz Core 2 Duo Macbook Pro Running Lion (upgraded from Tiger) with 3 gb 667Mhz DDR2 RAM and my 2010 Air 1.4Ghz Core 2 Duo (Upgraded from Snow Leopard to Mountain Lion) with 2gb 1067mhz DDR3 RAM. On both machines, for some time now, during normal usage; especially web browsing using Chrome and Safari (respectively); the inactive RAM on both machines will grow to consume around 30% of all RAM and force time consuming page outs to the mass storage drives on both machines. The Pro has a slower hard drive and the problem is the worst here, the air has a much faster SSD. I have found myself constantly having a window of Activity Monitor up on at least one of my desktops watching my RAM usage, using terminal to purge ram upwards of 10 times an hour to prevent costly page outs, especially on the Pro. I know Apple claims that inactive RAM is essentially free RAM that is temporarily storing recently used information for ease of access later and that it's supposed to be released as free memory when needed, but this obviously is not happening. Right now on my air my swap file is over 650Mb and I've seen it top 2Gb before. The air is exponentially better than the Pro due to the faster SSD, but I do notice substantial UI lag and a massive drop in fluidity as soon as my meager 2Gb is full and I start paging. The Pro is another story entirely, the entire system will essentially become unusable, having to wait several seconds for mouse clicks to even register. That's why I upgraded the stock 2Gb of RAM it comes with to 3Gb hoping that a 150% increase in RAM would help, but it just prolonged the inevitable. I still end up paging out just as bad across both systems if un checked. Even when I keep a close eye on memory usage and purge often, I still end up paging out because I'm not vigilant enough.
I have to limit my browsing to less than 5 tabs and keep my number of open programs less than 2 on both machines. My active and wired memory rarely seem to top 70%, meaning the rest gets taken by inactive, which isn't functioning as Apple claims. Even if my conclusions aobut what is happening under the hood are incorrect, something is going terribly wrong. I can't upgrade the RAM on my Air at all, and the RAM on my Pro is capped at 4Gb. I'm holding on upgrading because I don't think the excess hardware will solve this software memory problem. Whatever is happening is causing a serious drop in performance for me (yes I do know I have underpowered machines), but there has to be something I can do to speed performance. I've read about disabling the dynamic page file entirely, which just seems to crash the system when free memory is gone, and I've read about programs that claim to free memory. Those programs seem to work by taking a high priority in the process heigharchy of the OS and then proceeding to eat up large portions of RAM and releasing them as needed in an attempt to replicate the true intentions of inactive RAM, but I've heard of problems with this method as well. Does anyone have a viable solution? Monitoring my RAM usage myself and ensuring I don't end up paging out is costly, time consuming, annoying, and inefficient since I fail to catch the problem before I page if I get particularly busy. There is no other OS I've ever been acquainted with that has this problem, not any flavor of Linux, not even the dreaded windows. I seriously hope Apple can do something to manage this runaway memory problem. I'd like to be able to open more than 3 windows in Safari. I've had to purge 3 seperate times while writing this on my Air, and I now have 678 inactive memory, 741 inactive, 582 wired, and less than 14Mb free out of 2Gb with a growing swap at 680Mb. Each purge becomes less and less effective and the last one I did freed up only about 100Mb and it got eaten up again by inactive in less than 10 seconds. On my Air, the memory hog is Safari right now at 700Mb between the web content and flash player with only Facebook, youtube, and this Apple Supprt tab open. I have NO other applications running in the fore or background other than Activity Monitor and Terminal. On my Pro the memory hog is always kernel task, I use Chrome and Safari both. While the memory used by the browser does not usually take up the most substantial portion of the total used RAM out of any process, the more tabs I open, the more RAM I use. The browser is usually the second heaviest RAM hog to Kernel Task. So it seems that across the two machines there are two lsightly different manifestations of the same problem with the same results: massive performance drops and extremely annoying and costly page outs no matter the reason. I just want this problem to go away. I've used underpowered windows laptops that can open a dozen tabs in a heavier browser like IE or Firefox while using other programs like Word or Excel and more with no memory lag issues. There's no way in **** I could manage to open that many pages in a browser while using Pages and/or Numbers on either of my machines and expect reliable (swap free performance). This is just kind of sad in my opinion. Does anyone have a way to get my OSX machine running smooth so that I can remove the one thing that windows and Linux fan boys get the right to laugh at my Macs for?Hi Zephryl,
I was actually able to get an initial response from Sun on this a few months ago. However, the Sun Swing team has not followed up on a resolution for this pervasive problem, even though they noticed the same problem when running a test applet I had created for them. Apparently, I.E. is not releasing memory from the heap.
Below is a quote from a Sun rep. on this in an e-mail sent to me on Dec 4, 2002:
"I suspected the leak is in the native code because the # of handles and GDI objects keep increasing but no obvious Java objects are left behind in the Java heap during page switch."
So, until Sun and/or Microsoft work out a solution to this, anyone who uses I.E. 6 and applets for their UI seems to be in a lot of trouble.
As a note, trying to invoke the Garbage Collector does not do anything, but generally a very small amount of memory will be released (like maybe 5-10% of the memory allocated for the applet).
Cheers!
Avi Gray
Global Computer Enterprises -
EMac has poor memory management
I use an eMac and a G5. I would expect the G5 to be much faster than the eMac but here's a funny thing: I find that the G5 also manages memory much better than the eMac! For example, when I run OmniWeb for a long time on my eMac and really put it through its paces, loading up multiple pages and tabs, I find that OmniWeb starts running slower. Not surprising, but the rest of the computer starts running slower too! For example, creating a new folder may take several seconds.
Even stranger: after I quit all of my programs, the sluggishness continues. My eMac does not recover until I completely restart. Maybe OmniWeb has a memory leak or something, but this doesn't happen on the G5! I can put OmniWeb through its paces on the G5 and launch twice as many programs, including Photoshop, with no noticeable slowdown.
Now here's the weirdest thing of all: both computers have exactly the same amount of memory (768 MB) and both have plenty of free hard drive space (over 40 GB). All the memory on my eMac is Apple brand. I have even clean-reinstalled the OS on my eMac, to no avail.
Is it normal that memory management would be so much better on a G5 than an eMac?The improvements in each OS generation in memory management involve swapping tasks in and out of memory more efficiently, not using less memory --- invariablly more memory is actually used (to do more tasks). It would've been clearer had I noted that each OS generation does more with the memory and places more stringent demands on the RAM timing. Memory chips tha were good enough under 10.1 failed when 10.2 came out; ditto with 10.3/10.2 and 10.4/10.3
See what Console and/or Activity Monitor tell you is using CPU cycles. -
ITunes 7 Poor memory management!
Huge iTunes 7 memory problem.
Upon initial launch, it will use around 40-50mb of real RAM.
If I scroll through CoverFlow it will peak at around 1.5 to 1.6gb of real RAM usage! Going back to normal list view will bring it down to 700-800mb..
I have to quit and re-launch iTunes to get back down to less than 100mb.
If I try this on a computer with less than 2gb of ram OR I am running any other program, iTunes will start to skip because it ran out of physical ram.
I have been able to replicate this on multiple machines.
Very poor QC..The coverflow implementation is indeed using a ton of memory. It kind of has to if you think about it. In order to quickly browse through all of your albums, it has to preload all of your album covers, which are of decent resolution. On my MacBook Pro with 2Gb of ram, it flows effortlessly, but on my MacMini (intel) of which I plundered the ram for the MBP (now only 768mb), the coverflow isn't very useful. It quickly runs out of ram, and starts paging in and out. However, it does seem to release it's memory quite quickly, even if I just change the from the coverflow view to the standard view.
Apple should probably be clear about the memory requirements of this new feature, as a lot of people will just think it's a bug with iTunes.
Berndt -
Problems with memory management
Since my adoption of 10.7, I have noticed a problem that is really reminiscent of 10.2 and 10.3 of poor memory management. This is quite distressing as it has taken away from the performance of the operating system and has created many pages of VM files that are just below the engineering standards of Apple. Any suggestions along this line to clear this up would be greatly helpful. I have 3 GB of memory that is over utilized and over taxed.
I have read a bit about the "better" memory management, but that is all in theory. In the real world, Lion eats RAM and i upgraded from 4 to 8 Gb last week, that makes all the difference. If i close all apps now, 5.5 Gb RAM is still used, and i know that has something to do with Lions special workmemory management that is supposed to work to our favour, but it doesnt! Now after upgrading, fairly cheap but nothing for mainstream people, things work the way i suppose they are meant to work, but when Windows 7 and soon 8 are working towards less RAM needed, Apple seems to say one thing and do another. That is, they claim to have a improved (superior, fantastic?) system for RAM, but in reality it eats RAM for breakfast. Now i dont haveto close one app before opening another just to avoid the little spinning ball of colours.
Also Safari can use gigabytes of RAM on its own....not good. -
Use JNI application has memory manager, feasible?
Hi,
This is an attempt to circumvent javas poor memory management capabilities. Since java is unable to allocate memory dynamically (*) I'm thinking of writing a native library capable of allocating memory and then allowing java applications to stow away data in this area. The application would be able to access the memory directly through some java.nio.ByteArray-type implementation.
The java application would be responsible for allocating and deallocating, reading and writing data.
Is this feasible? Has anyone done this already? I guess a JNI is solution would be pretty straightforward?
(...this will be my first experience with JNI)
(*) Xmx option can be used assuming you know beforehand the memory requirements.Hi,
This is feasible since JNative already does this.
See Pointer and MemoryBlockFactory classes to do this.
--Marc (http://jnative.sf.net) -
Poor RAM management in Photoshop CS4 - need help!
I have done numerous hours of research over the years only to give up and come back to this subject later on. I will try again!
I must ask: is there ANY way to get Photoshop CS4 to automatically flush used RAM after closing image files? I'm tired and annoyed of CS4 eating more and more RAM without freeing anything after an image has been closed. An image shouldn't still eat up memory when it isn't even open anymore. It seems to be terrible RAM management of the program itself and how Adobe has forgotten to write that little snippit of code to clear the RAM after an image has been closed.
I know this is not because of:
Cache levels
Setting too large of a saved history state; purging history cache or any kind of cache still never frees RAM
A lack of updates; I have been up to date with CS4 very punctually as they were released
The computer I am on; this poor RAM management has been around since CS2 and it's the same on the last 4 computers I have used
Does CS5 still do this too?Your historically conditioned to believe software apps should swap data a standard way. The way your using the system is probably not the most effective processing for your workflow.
- I have hundreds of TIFFS that take 60-120MB each in processing, and 8gb of RAM. The more total RAM actually usable that I can use the better. How the heck can using less of what is actually available RAM enhance my workflow? Standard are standards for a reason. The ink industry for printing is non-standardized and people waste $3-5 billion+ a year only increasing on unused ink that is still remaining in their cartridges, because there is no standard way of manufacturing ink, filling cartridges, or monitoring how much ink is actually left in a cartridge. I'd love for more standards in more markets. Unless natively stable, all other programs on my computer work flawlessly with said demonized traditional methods and standards, even in high bandwidth applications a hell of a lot more intensive than Photoshop CS4 will EVER be. Currently people keep disregarding the fact that in my situation CS DOESNT FREE THE RAM. CS4 is balloon. Balloon inflate. Never deflate even when emptied. Overflow into other rooms of critical OS space where balloon shouldn't be when it fill the room full. How many analogies must I give? Must I use sign language? Binary?
You don’t have enough experience with these topics. This is actually a
true statement. Most companies with systems large and small have to
think about what it costs to process specific jobs. If one in a thousand
jobs swap, a decision must be made to know how much it would cost to
retrofit a very expensive environment to keep that one job swap from
occurring. Most times it is better to let the swap happen for this
non-mission critical item than pay $50,000 to upgrade all systems.
I said NON EMERGENCY SITUATIONS. Emergencies are once in a while. You're repeating what I said like a parrot, but in different longer sentences with more words telling me I don't get what I'm talkinga bout. You're missing the full picture of what I am actually saying. That 1 in 1000 overflow would be exactly true in my situation with 7GB used, but it's not. Why not? Because the CS4 balloon will not deflate itself or reuse the empty space inside the balloon when it's needed, and the OS isn't given back any of the empty space to work with to know it doesn't need to page anything. In turn CS4 is going to try and scratch too when the OS is telling it that is has no more RAM left when indeed it does, but its hiding it in its own reserve balloon from itself. If a company needed just 700MB more room and either they spend $50k to upgrade to that, or get CS4 to release some space once in awhile, they'd sure as hell bother Adobe or write their own mod to force CS4 to release unused allocated RAM to get it.
Self inflicted only because I want to push the limit of what is actually usable on my machine, not some 'safe zone' with high tolerance. My system is tuned for a fine line of performance and I know what it can hande. I know what it uses and it does not spike usage for random OS operations. It can handle 7GB to 7.2GB of RAM of freely used RAM to one active program if it needs that big of a workspace to work. If CS4 isn't going to reuse the hollow areas in that balloon, then that's not my fault. My OS can handle the fine tuning, and CS4 is what cannot, obviously, since it can see that much RAM but not use the last %10 correctly. -
Oracle 9i Automatic PGA Memory Management
Hello,
my team and me, we are facing difficulties to change the size of the PGA used by our server processes for HASH JOIN, SORT... operators,
here you can see the results of "select * from v$pgastat":
[pgastat dynamic view results|http://pastebin.com/m210314dc]
We have been increasing consecutively our pga_aggregate_target parameter from 1.7 Gb initially to 4Gb then at the end 6Gb, the value of "Global memory bound" and " aggregate pga auto target" on the link above are still equal to 0.
I have been reading threads on the forum and documentation see below, I understand how the global memory manager (CKPT) computest the sql memory target and then the global memory bound, as far as I understand I can only "play" on the pga_aggregate_target value in order to increase the size of our PGAs (I exclude to play with hidden parameters).
- Joze Senegacnik: Advanced Management of working areas in Oracle 9i/10g : http://tonguc.yilmaz.googlepages.com/JozeSenegacnik-PGAMemoryManagementvO.zip
- Dageville Benoit and Zait Mohamed: SQL memory management in oracle 9i
Here different information that could be usefull:
OS: solaris 10 (db running in a non global zone)
Arch: 64-bit sparcv9 kernel modules
Physical memory: 32 Gb (being shared between all non global zones)
Oracle version: 9.2.0.5 32bits
Values of init parameters and hidden parameters that could be relevant:
[init parameters|http://pastebin.com/m40340cf4]
[hidden parameters|http://pastebin.com/m50d74c53]
Maybe useful queries:
over work areas views, I use the following script:
[wa_analysis.sql|http://pastebin.com/d606ebd9b]
and the result of it:
[result of script wa_analysis.sql|http://pastebin.com/m5f49a2e5]Joze Senegacnik wrote:
- either your sessions are using a lot of memory for storing variables like pl/sql arrays which is subtracted from automatic management: PGA_AGGREGATE_TARGET - (aggregated persistent area + a part of the run time area of all server processes)
- you are hitting a bug
- or maybe something elseI am really happy you come to this conclusion too, they are the same we made with my team and we have submitting to Oracle support via metalink SR 3-1216060641, we were asking if we hit the following bug (in note 1) or we leak about pl/sql or java... or else indeed,
note 1: PGA_AGGREGATE_TARGET Assigned Memory Is Left Unconsumed When Set High [ID 844542.1]
Joze Senegacnik wrote:
I would like to know:
1.) what were the values for global memory bound and autotarget immediately (or in short time) after the database restart or when you have increased them Just after the restart of the database and just after the change of P_A_T, we query v$pgastat immediately after and the value of global memory bound and auto target were equal to 0 byte,
2.) If you are able to change value of PGA_AGGREGATE_TARGET (P_A_T) to 10GB what happens with global memory bound and auto traget. They should be positive at least for a short time. As this is a dynamic parameter you can change it for a short time, run queries and set it back.We plan to do this tonight, we have an "heavy" ITIL change management procedures that allow us to make changes approved by change manager and only during night maintenance window on production system, I come back to you tomorrow. But we have been increasing from 1,7Gb to 4Gb to 6Gb, each time I have been querying v$sgastat in the next 2 mins and global memory bound and auto target were equal to 0 byte.
3.) Have you checked on the OS level how much memory are using server processes - do these numbers come along with what Oracle says. Not during problematic activities, meaning active work areas performing HASH-JOIN, SORT... operators,
unfortunately it is a production system, even if he performs poorly, we are not allowed to try or retry the poor queries, but if it comes again I'll do it,
during low activities, here the results paste with the scripts I used:
[pga processes info in oracle|http://pastebin.com/f2e540062]
I spooled the result rows of this previous script in /var/tmp/pga_processes.log then I loop over all processes pid and display pmap output anon info like this:
h5. cat /var/tmp/pga_processes.log | awk -F' ' '{print $5}' | xargs -n 1 -i pmap -x {}| grep -v 'Addres' |egrep 'Kb' 2>&1 > /var/tmp/pga_processes_os.log
then I merge line by line the two files with unix paste command, here the results:
[os and oracle pga informations|http://pastebin.com/f4135c8a6]
4.) How many server processes are running on you system in average/max and are you using just dedicated processes or also shared?in average 250, we are only using dedicated processes,
5.) At time of low activity is the global memory bound still 0 or becomes > 0. I have been querying every 15 min during more than 24 hours low activities, it still stay to 0,
5.) Are you experiencing paging/swapping on OS level?No, here orca figures for details:
[free memory|http://img509.imageshack.us/img509/5897/ohuron1asd2gauge1024xfr.png]
swap
[pagein pageout|http://img121.imageshack.us/img121/6946/ohuron1asd2gaugepginper.png]
[memory usage|http://img19.imageshack.us/img19/2213/ohuron1asd2gaugeppkerne.png]
6.) Please post the result of: select * from X$QESMMSGA ;during low activities, [results X$QESMMSGA|http://pastebin.com/f61df7093]
While you will be answering to my questions I'll try to figure out what we can do to properly diagnose the problem. As you are on 9i it is a little bit harder.I am really kind of your help, as we say in my country, "if you need tow arms one day to carry something, call me."
--Jeremy Baumont -
How I fixed memory management fails on Lion
MAC:
17" i7 2.66GHz Macbook Prom Mid 2010
SYMPTOM:
The Free memory was always dropping and I needed to use FREE MEMORY APPS from Apps Store. The beach ball was frequent. The speed is so slowly from OS X Snow Leopard, even I made a Permissions Fix, it takes a lot to start and shut down. The memory drops on every app I open and the system can't free them after I quit the apps.
WHAT I DO:
I made a backup, formated and installed a free new copy of OS X Lion and SOLVED all the memory drops.
IMPRESSIONS:
I have 8GB of RAM in my and now I see at least FREE 5.5GB RAM CONSTANTLY (navigating web, without use of huge memory hungry background apps). I'm another 17" MBP Mid 2009 owner with 4GB RAM and noted that it was faster. Both with the last version of Lion. Not now after the new copy of Lion my mac is pretty fast again There is no aparent issues about Lion Memory Management as people are discussing.Yes, a brody and thanks for your link. In this Mac I installed an old HP scanner driver
I'm very concearned about people saying don't upgrade to Lion, it's a big liar! You don't need to put your mac to sleep as people said to don't waste time on boot. I imagine boot process is very useful for system reset and evaluate hardware status.
I made a lot of reboots to certificate the speed boost, I imagine the system makes it to diagnose any problems and fix itselves.
I feel the boot and shutdown is becoming fast as I use it since the first boot of reinstaled Lion.
Only one issue (solved) is about installing Epson printer that couldn't print wirelessly.
It was solved just clicking at OSX X UPDATE SOFTWARE and it discovers an needed Epson Driver Update for Lion.
Very happy again with my mac. -
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 ??? -
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 -
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 -
Memory Management Error in Windows 8.1
please check dumpfile in this url related to memory management error in windows 8.1. This error usually occurs when i open window media player....thanks
https://skydrive.live.com/redir?resid=99B960292878F11C%21148These crashes were related to memory management (probably caused by a driver).
Please run these tests to verify your memory and find which driver is causing the problem.
If you are overclocking (pushing the components beyond their design) you should revert to default at least until the crashing is solved. If you don't
know what it is you probably are not overclocking.
1-Memtest. (You can read more about running memtest here)
2-Driver verifier (for complete directions see our wiki here)
Co-Authored by JMH3143
Wanikiya and Dyami--Team Zigzag
Maybe you are looking for
-
Installation of Oracle 11g 32 bit Client on Windows 7 (32 bit) laptop.
Hi, I just got a new Laptop with Windows 7 (32 bit) operating system. Has any one successfully installed Oracle 11g client on in Windows 7 environment and if so what are the steps involved. In the past I have never had any trouble installing an Oracl
-
I have windows 7 on my laptop and i can't get my songs to work.
I have windows 7 on my laptop and the current version of iTunes. For the past two days I cannot play songs from my music or purchased list. I can't even play the sample of a song in the iTunes store. I click on play on it does nothing. What's wrong?
-
Hello everyone. I have a form with a dynamically generated number of fields. Each Client has a variable number of "ItemDetails" assigned to them based upon which Item that individual is registered for. For example: Customer A is registered for a HRID
-
Does Adobe Photoshop Elements 12 offer the following features?
Hello Members, I would like to know if Adobe Photoshop Elements 12 offer the following features: warp tool, kaleidoscope and patterns etc? Thank you.
-
I've uninstalled and reinstalled the program per the Apple support site's instructions, but for some reason iTunes will not open for me. The icon bounces in the dock twice and then stops jumping. No windows/notifications/alerts appear. What should I