Hp530 cpu 100% all the time
Hi, i am trying to upgrade my cpu as it is stuck at 100% most of the time under very light browsing...no gaming or streaming movies etc. i have fiddled enough with processess and services, cleaned the fan applied thermal grease and still same issue. Will T7200 be ok for my configuration as follows??? or any other cpu is recommended
thank u
HP 530 Intel celeron 1.73ghz
CPU-Z TXT Report
Processors
Number of processors 1
Number of threads 1
APICs
Processor 0
-- Core -256
-- Thread -256 -1
Timers
ACPI timer 3.580 MHz
HPET timer 14.318 MHz
Perf timer 1.689 MHz
Sys timer 1.000 KHz
Processors Information
Processor 1 ID = -1
Number of cores 1 (max 1)
Number of threads 1 (max 1)
Name Intel Celeron M
Codename Conroe-L
Specification Intel(R) Celeron(R) M CPU 530 @ 1.73GHz
Package (platform ID) Socket 479 mPGA (0x1)
CPUID 6.6.1
Extended CPUID 6.16
Core Stepping A1
Technology 65 nm
Core Speed 1728.7 MHz
Multiplier x Bus Speed 13.0 x 133.0 MHz
Rated Bus speed 531.9 MHz
Instructions sets MMX, SSE, SSE2, SSE3, SSSE3, EM64T
L1 Data cache 32 KBytes, 8-way set associative, 64-byte line size
L1 Instruction cache 32 KBytes, 8-way set associative, 64-byte line size
L2 cache 1024 KBytes, 4-way set associative, 64-byte line size
FID/VID Control no
Chipset
Northbridge Intel i945GME rev. 03
Southbridge Intel 82801GHM (ICH7-M/U) rev. A1
Memory Type DDR2
Memory Size 2 GBytes
Channels Dual
Memory Frequency 266.0 MHz (1:2)
CAS# latency (CL) 4.0
RAS# to CAS# delay (tRCD) 4
RAS# Precharge (tRP) 4
Cycle Time (tRAS) 12
Bank Cycle Time (tRC) 16
MCHBAR I/O Base address 0x0FED94000
MCHBAR I/O Size 4096
MCHBAR registers
This has been answered. Yes, you can use a T7200
Similar Messages
-
(CS4) Photoshop 32Bit + Bridge + Win7 = CPU 100% all the time
This is something that occurred to me many times now:
I need to use the 32Bit-Version of Photoshop because of all the Plugins I use and some of them run ONLY on one of them at a time, like PixelBender ( W H Y ? ? ? )
So: Whenever I have Photoshop 32bits running (because it would default to 64bits where my plugins are not available) and open Bridge afterwards to open a file in PS, Photoshop stays at 100% CPU (on one of the cores) all the time without any reason. I also checked if there were selections active (yes, selections sometimes pretty much need a LOT of CPU power, whyever!)
Otherwise, when I first start Bridge and THEN Photoshop 32Bits, the CPU usage is okay. Something seems using up much CPU power in some kind of endless loop / dead lock or something?!
It's quite annoying, because I don't use Bridge that often. Sometimes I want to start Bridge "on demand". And if I have opened Photoshop already I would have to close down everything just to be able to start Bridge again without losing a full CPU core.
So if anyone has the same issues like me: Just reverse the opening order: First open Bridge, THEN open Photoshop and everything should be fine.I don't have an answer to your question about the infinite loop, but I can answer this:
function(){return A.apply(null,[this].concat($A(arguments)))}
Ninarama wrote:
I need to use the 32Bit-Version of Photoshop because of all the Plugins I use and some of them run ONLY on one of them at a time, like PixelBender
( W H Y ? ? ? )
A plugin is a special kind of callable function library (Dynamic Link Library, or DLL in Windows speak). A 32 bit DLL cannot be used by a 64 bit version of Photoshop. In order to use the completely different instruction set the processor provides for 64 bit operation, the plugin code must be compiled specifically for 64 bit operation.
All plugins developed before the time of Photoshop CS4 were originally developed as 32 bit applications, because Photoshop was only 32 bit. Even today, 32 bit users outnumber 64 bit users by a large margin.
Microsoft makes it almost trivially easy to compile 32 bit source code as a 64 bit application, BUT... If the programmer hasn't been careful in his use of data types - specifically those that will be a different size (e.g., a pointer will be increased from 32 bits to 64 bits), then doing so - even if the software compiles successfully - might yield a non-functional plugin.
Sadly, many programmers are not careful with their use of data types. This is 30+ years of software engineering talking.
With good design and good coding practices, the code will be good and the programmer will be able to compile a 64 bit plugin quickly. Even bad code can be cleaned up in time, so that it can be made to work in 64 bit form.
But there's even more that must be done...
Most serious software uses an installer.
Installing software on a 64 bit system requires big changes to the installation package, or maybe even a whole new installer. There is, for example, the added complexity that you, the user, might want the proper variant of the plugin installed into each of your 32 bit and 64 bit Photoshop installations. And possibly multiples (e.g., CS4, CS5). Creating a good installer package is somewhat akin to designing a rocket booster. Except that the latter is generally agreed to be easier.
And all this is just on the Windows side! It must be repeated for the Mac, assuming the plugin is marketed into that segment as well.
So... If your favorite plugin doesn't run under Photoshop x64, and the author doesn't have an upgrade available that does, maybe they are struggling to make it work, maybe they decided the x64 user market isn't big enough for their attention right now, or maybe they're just working on something else.
Probably more than you wanted to know, eh?
-Noel -
Don't understand why OEM is reporting that Database Time Spent Waiting (%): Wait Class Other is nearly 100% all the time. Database 10.1.0.4 just installed on Linux(RHEL4AS) and nobody use it for now except OEM and me for admin purpose.
Any clue for that problem ?
Regards
NicolasSeems like you are not the first to see this kind of behaviour.
I've found another similar thread on metalink. I can't say the answer is terribly helpful, but thought you might be interested anyway:
From: Jose Ramón Tourón 14-Sep-07 08:34
Subject: Database Time Spent Waiting (%) at 100 in event class Commit
RDBMS Version: Oracle 10g r2
Operating System and Version: Suse Enterprise Linux 10
Error Number (if applicable):
Product (i.e. SQL*Loader, Import, etc.): database core
Product Version: 10gR2
Database Time Spent Waiting (%) at 100 in event class Commit
Hi everyone, yesterday we create a new database instance with dbca, the creation process was ok, and the two instances are running ok, database stops and starts without any problem, and listeners are ok. In the enterprise manager of this new instance we found this message:
Database Time Spent Waiting (%) at 100 in event class Commit, this event happend every 1 or 2 minutes sometimes at 100, the next 40%, the next 98, ... and so on.
Do you know what's happend in this instance?
Thanks in advance to everyone
Santiago Pérez
From: Oracle, Helmut Pfau 14-Sep-07 12:52
Subject: Re : Database Time Spent Waiting (%) at 100 in event class Commit
From Oracle Database Reference Manual:
Commit
This wait class only comprises one wait event - wait for redo log write confirmation after a commit (that is, 'log file sync')
So you can't write fast enough into your log files.
Did you check the frequency of log switches?
From: Metalink TCS User Group TCS Uruguay 14-Sep-07 15:52
Subject: Re : Database Time Spent Waiting (%) at 100 in event class Commit
Hi José! Please don't get anxious because of this: Wait time must be SOMEWHERE, there's a saying "An OLTP DB is only as fast as its redo logs", but if you are not having any performance problem you don't need to do anything special.
You say you've just created the DB. Now make it DO something: put it to the test by simulating production conditions as closely as you can, and after some hours ask the users whether there is some problem. If there is, take a look at the wait statistics... you'll probably see many other top events before this one!
Bruno abate_at_adinet.com.uy -
MBP Running at 98% CPU Usage All the Time
I'm not sure exactly when this first started, but now whenever I'm in Mac OS X a process called "Socket" running under "root" is constantly using ~98% of my dual-core CPU (out of a possible 200%). This prevents my computer from sleeping and it's obviously using a lot more energy all the time. I can shut the process down and the computer will relax for a while, but it's only a matter of time before it starts again. Any ideas on the matter? The help is greatly appreciated.
The process name is "socket". Is the user cupsd? Check for a print job stuck in the queue.
CUPS stands for Common UNIX Printing System; the cupsd process is the main print engine for OS X.
Run Applications > Utilities > Disk Utility, select your HDD and click Repair Permissions.
You might also try trashing your printing preference files (user/library/preferences folder, .plist files with names that start with com.apple.print).
Hope this helps...
Ps: There's a nice printing repair utility (shareware) out there:
http://www.fixamacsoftware.com/software/pt6/index.php -
Why Lightroom keeps using 30% CPU power all the time?
Hello all,
I am relatively new to LIghtRoom.
I started working on a new set of photos (400 app.). I opened it as new directory.
Since then, all the time I work on theses pictures Lightroom keeps using app. 30% of CPU time.
The over all time I spent on these photos is estimated to be more then 30 hours (yes, I am slow and open each in Photoshop while Lightroom is still opened). So I guess Lightroom finished all the rendering it wished to do.
My question is why and what it keeps calculating and is there a way to stop it?
System configuration:
Single core Intel Pentium 4 CPU, 3.6 GHz (Hyper Threading allowed)
2 GB RAM
NVidia 6600 based graphics card (256 MB)
Both LightRoom 2.3 and PhotoShop CS4 are opened
Please help - the system is slow anyway. It can realy use those extra CPU power.
Utzlyutzly wrote:
But I get a warning that changes I made to pictures in LR might not be
visible in other applications. Dose this mean that when I send the picture
to PhotoShop, or open the raw file later with bridge, all the editing inside
LR will not show?
The warning badge can be switched off from within View Options panel (Library module View menu) by unchecking the option labelled Unsaved Metadata.
With regard to your question as to whether Lr edits will show in Photoshop and Bridge/ACR - you'll be fine with Photoshop. However, for Lr edits to be visible in Bridge/ACR you will now have to manually save the metadata to each file (i.e. select file(s) then hit Cmd/Ctrl+S to save metadata to file). -
Very slow Pages, CPU at 100% all the time
Hey there,
I have some trouble with my Pages 2.0.1 on my PowerMac G3 with Sonnet G4-800. Every time the text window is in foreground and you want to write something, the CPU is at 100% ant the mouse is moving in discrete steps. Then, when I'm typing in, Pages is 3-4 words behind me. It is getting worse if I want to scroll in a document.
All other Apps on this machine are as fast as they should be, incl. Keynote.
I have no trouble at all with Pages on my PowerBook 1,5GHz.
Has anybody some work around?
TNXTry the following things, which all have been known to cause slowdowns.
1. Do you have any PostScript Fonts installed? Some people have reported problems with some PostScript Fonts.
2. Do you have any missing fonts? When you open the document, does Pages complain that it cannot find one or several fonts?
3. Do you have corrupt fonts? Open FontBook, select all fonts and then File > Validate Fonts.
4. Corrupt pictures, songs and movies in your home folder's Movies, Music and Pictures folders can slow down the product through the Media Browser. AVI films in the Movie folder can slow things down, as QT usually cannot play them.
5. Go to View > Hide > Layout. For some reason the layout slows things down.
6. Don't view Thumbnails.
7. Use the Text Fit option "follow contour" instead of "follow a square" in the bottom section of the wrap inspector. (Or was it the other way round? Anyone?)
8. If an object is set to wrap, and a wrapped side squeezes out any possibility of text wrapping along that side - such as extending a text box to the margin, the extreme slowdown will occur. So don't.
9. Use as few objects as possible Fixed on Page. Instead use Moves with Text.
10. Reduce the resolution of your screen. -
I had a Aperture Library before and it converted to a Photos Library with 160GB including many of the original RAW formats. I got the library on an external USB3 SSD disk which is usually quite fast.
Now this conversion process is already finished, but when Photos is opened it constanly has a CPU usage above 100%, typically something between 150 and 300% CPU usage.
I also see the app is constantly reading and writing data. Has anyone an idea what it's doing? Couldn't be iCould sync as this is not activated for me.
And overall the app is pretty slow and not performing very wellI'm actually finding it pretty usable, but I have the exact same issue on my 2011 MacBook Pro (2.0Ghz). It's been running between 200%-600% CPU for the best part of two (business) days now and my library is smaller than yours (~ 17k images, ~100Gb).
I'm getting close to the point of giving up. Without any signs of progress it's difficult to tell whether it's doing anything useful (where's Apertures Activity pane when you need it?).
Saw this in the logs:
10/04/2015 14:35:48.000 kernel[0]: process Photos[11712] thread 1386246 caught burning CPU! It used more than 50% CPU (Actual recent usage: 51%) over 180 seconds. thread lifetime cpu usage 154.283601 seconds, (114.205363 user, 40.078238 system) ledger info: balance: 90002042567 credit: 149514492269 debit: 59512449702 limit: 90000000000 (50%) period: 180000000000 time since last refill (ns): 174309468334
And:
10/04/2015 15:38:16.000 kernel[0]: process Photos[12094] thread 1580420 caught burning CPU!; EXC_RESOURCE supressed due to audio playback
And:
10/04/2015 14:35:50.851 spindump[10646]: Saved cpu_resource.diag report for Photos version 1.0 (209.52.0) to /Library/Logs/DiagnosticReports/Photos_2015-04-10-143550_Stephens-MacBook.cpu_r esource.diag
(This file suggests that it's doing face detection.)
These don't look good on the surface... but who knows?! -
IUService hogs CPU 50% all the time
For some reason that I have not been able to trace, since yesterday every time I boot my T60 (running XP Pro SP3) the process IUservice is taking 50% or more of CPU capacity. (As I understand it, IUservice is part of the Lenovo Rescue and Recovery facility.) This happens pretty much as soon as I log on, and obviously this slows down everything else big time.
I can of course end the process, but I don't really want to have to do this every time I reboot the machine, and I'd rather not interfere with things that should be there.
Is there a way in which I can make this process behave again?
Thanks!
Koen
T60 1951-FDG 14.1" DVDRW XP Pro
T60 2007-43G 14.1" DVCD/CDRW XP ProPlease read this thread and use the Search function before posting another one of these threads. The Forum is full of threads on this topic. Here is the one of them:
http://discussions.apple.com/thread.jspa?threadID=1322338&tstart=0 -
I downloaded adobe flash player 11.4 r402, my cpu overheats all the time now.
I am running winodows vista with firefox 17.0.1 and I downloaded adobe flash player 11.4 r402. Whenever flash is used on a page or I use realplayer my cpu starts to overheat. this player is constantly using too much of my cpu and I have to end process the player. is there a fix for this or an update? I have tried to downgrade my flash player but the older versions cannot play youtube and realplayer vids.
I just downloaded version 11.7.700.202 now and tried a Youtube vid and that version is using 44 - 55 % of my cpu for the vid. I never had this issue before updating to 11.4 and i have been having it ever since.
-
GT60 0NC, no GPU and fan at 100% all the time
Hello.
Recently after many tries to solve nvlddmkm.sys problems I've got final crash. After which my OS could not see my GPU and fan was spinning at full speed. It was after underclocking shader clock from 1240MHz to 1200MHz and opening a game. The screen froze and at the bottom of the it, there was black belt through the screen with RGB colours dots in random locations. Now after full reinstall of the OS from win7 64bit to win8.1 64bit, this all still persist.
Any ideas would be good, as I could not see nor find any solution to this.
My current config is:
-MSI laptop GT60 0NC
-NVIDIA GPU GeForce GTX 670M
-Intel Core i7-3630QM
-Windows 8.1 Pro N 64bitSo to settle the fan down I would have to disable dGPU. Not just unplug it but disable it. And to do this I would probably need unlocked BIOS. Correct me if I am wrong, if not I would appreciate any leads how to do this.
And if my dGPU is broken I can at least try the oven. And question about further actions, can i access mini PCI-e in MSI GT60 0NC in any way? To try connecting external GPU via EXP GDC Beast Laptop External Independent Video Card Dock. I do have GTX 460 from my old PC so I am just wondering. -
25% cpu usage from sysmond process all the time
Hi,
I have a MacBook Pro Retina running Mountain Lion and my battery is running out very soon (under 2 hours) and the MacBook is getting very warm. I found the process sysmond running with at least 25% cpu usage all the time. I can't kill that beast and it justs ***** my battery. A reboot doesn't help. How can I fix that?
Regards,
PhilipOpen Activity Monitor, Select 'sysmond', click on it and then click on the red octagon on the top of the widow. The process should stop.
Ciao.
There may be other reasons for the short battery run time.
Message was edited by: OGELTHORPE -
Why does iTunes use 100% CPU all the time, hogging my Macbook Air?
Decided to post this here instead of the iTunes forum, since it might be related to hardware too.
New owner of a 2011 13" Macbook Air, core i5 based.
My problem started about 1 week ago, after it had run out of power completely one day. At the first boot after that it was incredibly sluggish, totally unusable. After waiting for 5 minutes and still being unresponsive, I turned it off and then back on. Then it booted fine. HOWEVER, ever since that time I noticed the following behavior:
- iTunes stays at 100% + CPU all the time, mostly between 100-120%. Even if it's not playing. Even when I deleted the entire library and left it empty.
- iStats reports CPU idle between 50-65%. However, CPU temperature is still about 55 degrees C (which, I think, is far less than what it should have been with 50% idle cpu). I can confirm the low temperature by touching the chasis.
- the cursor freezes and jumps every few seconds, making the mac kind of unusable with iTunes open.
This has been going on for 2 weeks now. The problem goes away every now and then (iTunes sometimes goes back to regular CPU usage of 3-5%), but most of the time it's there.
Help!
P.S.
Mac OX X 10.7.2
iTunes 10.5.2Cee Pee You, is a OS modification. Apple recommends that you un-install these prior to a OS update because Apple makes changes to the OS all the time which breaks programs like these.
I avoid Unsanity LLC products like the plague. Notice the company is a Limited Liability Corporation (LLC), which makes it difficult to sue the company in case of a defective or malicious product. So the risk using their products is all yours. Their APE framework modules have been used for malicious purposes because anyone can write a module that uses the APE framework.
I also avoid installing anything that requires a administrative password unless I completely trust the source, like Apple mostly. That admin password is the key to the security of our machines, not to be given out lightly or carelessly.
You'll have to contact Unsanity's [email protected] because what I'm reading online is it's very difficult to remove as it doesn't "exist".
http://forums.macosxhints.com/archive/index.php/t-3616.html -
RV180 - CPU ALL the Time 100% Firmware 1.0.4.14
Hi all
i just get a new RV180 and after upgrade to last ver 1.0.4.14 the CPU is 100% non stop
i try to stop all Firewall and not working all the time i get "page is loading .... "
i will try to downgrade to 1.0.3.10 but i must say this is not cisco finest product ...
any idea ?Hi ,
regarding this issue with port forwarding we need to do some packet capture,
On RV180 we have the option to capture the WAN and LAN interfaces.
When you have the issue, connect to the RV180 and run the Packet capture on LAN interface and try to access to the server connected to the local network of the router, and capture the WAN and LAN interface we can see the packet where is dropped.
Please you can also call the Cisco Technical Support and open a ticket regarding the issue, better when you have the issue they can investigate and made the capture traffic.
here is the small business contact : http://www.cisco.com/c/en/us/support/web/tsd-cisco-small-business-support-center-contacts.html
Thanks
Mehdi -
Laptop fan runs all the time, broker runtime cpu usage after Windows 10 final upgrade
ENVY 17t-J100 Leap Motion, 16 GB RAM, i7, SSD primary, HDD secondary drives. Avast antivirus free. Windows Firewall. The laptop had Windows 8.1 and everything was great. I did the Windows 10 Home free upgrade on Day 1. Everything seemed fine. Fingerprinter reader and everything works. Great. But then I noticed that the fan was always running and the left side of the metal casing gets hot. In task manager heat map sorted by CPU usage, Broker Runtime is at the top. Not much ram, about 10 MB. But the CPU usage is always 20% and higher. Doesn't seem like much. But it makes the fan run all the time and the laptop heats up with it running all the time. Anyone else seen this? General internet searching shows this has been an issue with Broker Runtime since Windows 8 and not unique to any brand of computer. But it wasn't like this when I was using WIndows 8.1 One forum said it was the P2P Windows update feature and my laptop was sharing updates. So I disabled that and rebooted. No change. Now I see some people saying it is the Live Tiles features in the Start Menu. But I had live tiles with the WIndows 8 menu and no issues. The only way to disable Live Tiles globally is to edit the registry, and I shouldn't have to do that for this. And I like Live Tiles. So not sure that really is the issue either.
hockeycanuckjc wrote:
Have all Windows Updates on Windows 10 been applied since installing it? I know there are people weary to update Windows 10 since there have been a few news reports with some people having the infinite reboot loop after installing a particular update For me, yes. All updates applied and automatic updates enabled. This Runtime Broker issue has been there since the upgrade and all updates to this point. -
Macbook Pro Randomly Crashing all the time
Hi Guys
My Macbook pro is crashing ALL the time I think its been sincing upgrading to Maverick
Below is the crash report
Process: revisiond [647]
Path: /System/Library/PrivateFrameworks/GenerationalStorage.framework/Versions/A/Supp ort/revisiond
Identifier: revisiond
Version: 160.3
Code Type: X86-64 (Native)
Parent Process: launchd [1]
Responsible: revisiond [647]
User ID: 0
Date/Time: 2014-06-25 16:30:34.433 +0100
OS Version: Mac OS X 10.9.3 (13D65)
Report Version: 11
Anonymous UUID: 1E29002B-F79F-12D2-4033-49CB6544AE2E
Crashed Thread: 7 Dispatch queue: com.apple.root.background-priority
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: EXC_I386_GPFLT
Thread 0:
0 libsystem_kernel.dylib 0x00007fff8dfd2a52 __semwait_signal_nocancel + 10
1 libsystem_c.dylib 0x00007fff906c099c nanosleep$NOCANCEL + 189
2 libsystem_c.dylib 0x00007fff906e8992 sleep$NOCANCEL + 42
3 libdispatch.dylib 0x00007fff8ca25765 _dispatch_queue_cleanup2 + 86
4 libsystem_pthread.dylib 0x00007fff90a1a5af _pthread_tsd_cleanup + 182
5 libsystem_pthread.dylib 0x00007fff90a17479 _pthread_exit + 111
6 libsystem_pthread.dylib 0x00007fff90a173e9 pthread_exit + 30
7 libdispatch.dylib 0x00007fff8ca2570f dispatch_main + 43
8 revisiond 0x000000010e00bb1c 0x10dff7000 + 84764
9 libdyld.dylib 0x00007fff868325fd start + 1
Thread 1:: Dispatch queue: com.apple.libdispatch-manager
0 libsystem_kernel.dylib 0x00007fff8dfd3662 kevent64 + 10
1 libdispatch.dylib 0x00007fff8ca1d421 _dispatch_mgr_invoke + 239
2 libdispatch.dylib 0x00007fff8ca1d136 _dispatch_mgr_thread + 52
Thread 2:
0 libsystem_kernel.dylib 0x00007fff8dfd2e6a __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x00007fff90a17f08 _pthread_wqthread + 330
2 libsystem_pthread.dylib 0x00007fff90a1afb9 start_wqthread + 13
Thread 3:
0 libsystem_kernel.dylib 0x00007fff8dfd2e6a __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x00007fff90a17f08 _pthread_wqthread + 330
2 libsystem_pthread.dylib 0x00007fff90a1afb9 start_wqthread + 13
Thread 4:: Dispatch queue: com.apple.root.default-overcommit-priority
0 libsystem_kernel.dylib 0x00007fff8dfd2caa __sigsuspend_nocancel + 10
1 libdispatch.dylib 0x00007fff8ca257da _dispatch_sigsuspend + 21
2 libdispatch.dylib 0x00007fff8ca257c5 _dispatch_sig_thread + 45
Thread 5:
0 libsystem_kernel.dylib 0x00007fff8dfd39f2 read + 10
1 com.apple.AppleFSCompression 0x00007fff8fb8c68c type5_handler_function + 156
2 libsystem_pthread.dylib 0x00007fff90a16899 _pthread_body + 138
3 libsystem_pthread.dylib 0x00007fff90a1672a _pthread_start + 137
4 libsystem_pthread.dylib 0x00007fff90a1afc9 thread_start + 13
Thread 6:
0 libsystem_kernel.dylib 0x00007fff8dfd32ea fsctl + 10
1 revisiond 0x000000010e00a9b9 0x10dff7000 + 80313
2 libsystem_pthread.dylib 0x00007fff90a16899 _pthread_body + 138
3 libsystem_pthread.dylib 0x00007fff90a1672a _pthread_start + 137
4 libsystem_pthread.dylib 0x00007fff90a1afc9 thread_start + 13
Thread 7 Crashed:: Dispatch queue: com.apple.root.background-priority
0 revisiond 0x000000010e028000 0x10dff7000 + 200704
1 libdispatch.dylib 0x00007fff8ca1b526 _dispatch_Block_copy + 43
2 libdispatch.dylib 0x00007fff8ca22419 dispatch_group_async + 21
3 revisiond 0x000000010e023fe0 0x10dff7000 + 184288
4 revisiond 0x000000010e02b809 0x10dff7000 + 215049
5 revisiond 0x000000010e02ba5c 0x10dff7000 + 215644
6 revisiond 0x000000010e02bebe 0x10dff7000 + 216766
7 libdispatch.dylib 0x00007fff8ca1e1bb _dispatch_call_block_and_release + 12
8 libdispatch.dylib 0x00007fff8ca1b28d _dispatch_client_callout + 8
9 libdispatch.dylib 0x00007fff8ca1d082 _dispatch_root_queue_drain + 326
10 libdispatch.dylib 0x00007fff8ca1e177 _dispatch_worker_thread2 + 40
11 libsystem_pthread.dylib 0x00007fff90a17ef8 _pthread_wqthread + 314
12 libsystem_pthread.dylib 0x00007fff90a1afb9 start_wqthread + 13
Thread 8:
0 libsystem_kernel.dylib 0x00007fff8dfd2e6a __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x00007fff90a17f08 _pthread_wqthread + 330
2 libsystem_pthread.dylib 0x00007fff90a1afb9 start_wqthread + 13
Thread 7 crashed with X86 Thread State (64-bit):
rax: 0x000000010e04f900 rbx: 0x00007fb870c0c1d0 rcx: 0x00007fb870f01850 rdx: 0x0000000000000000
rdi: 0x00007fb870c0c1d0 rsi: 0x000000010f409518 rbp: 0x000000010f4094c0 rsp: 0x000000010f409488
r8: 0x0000000000000002 r9: 0x00007fb870c00000 r10: 0x0000000000000012 r11: 0x00007fb761802cb8
r12: 0x000000010f409518 r13: 0x000000010f4095d0 r14: 0x0000000000000000 r15: 0x000000010e04f900
rip: 0x000000010e028000 rfl: 0x0000000000010246 cr2: 0x000000010e028000
Logical CPU: 6
Error Code: 0x00000000
Trap Number: 13
Binary Images:
0x10dff7000 - 0x10e049ff7 revisiond (160.3) <D47873DF-3407-3625-982D-4E80B7D4B8DC> /System/Library/PrivateFrameworks/GenerationalStorage.framework/Versions/A/Supp ort/revisiond
0x7fff68704000 - 0x7fff68737817 dyld (239.4) <042C4CED-6FB2-3B1C-948B-CAF2EE3B9F7A> /usr/lib/dyld
0x7fff857ad000 - 0x7fff857b1fff libpam.2.dylib (20) <B93CE8F5-DAA8-30A1-B1F6-F890509513CB> /usr/lib/libpam.2.dylib
0x7fff85a0c000 - 0x7fff85d0afff com.apple.Foundation (6.9 - 1056.13) <2EE9AB07-3EA0-37D3-B407-4A520F2CB497> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
0x7fff85eaa000 - 0x7fff8608ffff com.apple.CoreFoundation (6.9 - 855.16) <A63E680E-E4B2-368B-8564-9DBE0D8DDB91> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
0x7fff86401000 - 0x7fff86412ff7 libz.1.dylib (53) <42E0C8C6-CA38-3CA4-8619-D24ED5DD492E> /usr/lib/libz.1.dylib
0x7fff867f6000 - 0x7fff867fbfff libmacho.dylib (845) <1D2910DF-C036-3A82-A3FD-44FF73B5FF9B> /usr/lib/system/libmacho.dylib
0x7fff867fc000 - 0x7fff86804fff libMatch.1.dylib (19) <021293AB-407D-309A-87F5-8E782F46753E> /usr/lib/libMatch.1.dylib
0x7fff86805000 - 0x7fff8682efff com.apple.DictionaryServices (1.2 - 208) <A539A058-BA57-35EE-AA08-D0B0E835127D> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Diction aryServices.framework/Versions/A/DictionaryServices
0x7fff8682f000 - 0x7fff86832ff7 libdyld.dylib (239.4) <7C9EC3B7-DDE3-33FF-953F-4067C743951D> /usr/lib/system/libdyld.dylib
0x7fff8728f000 - 0x7fff872fcfff com.apple.SearchKit (1.4.0 - 1.4.0) <B9B8D510-A27E-36B0-93E9-17146D9E9045> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SearchK it.framework/Versions/A/SearchKit
0x7fff8730a000 - 0x7fff8732fff7 com.apple.ChunkingLibrary (2.0 - 155.1) <B845DC7A-D1EA-31E2-967C-D1FE0C628036> /System/Library/PrivateFrameworks/ChunkingLibrary.framework/Versions/A/Chunking Library
0x7fff87330000 - 0x7fff87334ff7 libcache.dylib (62) <BDC1E65B-72A1-3DA3-A57C-B23159CAAD0B> /usr/lib/system/libcache.dylib
0x7fff88161000 - 0x7fff882fcff8 com.apple.CFNetwork (673.3 - 673.3) <4375B7CB-34B6-3A26-99AC-2D2404AD9C9B> /System/Library/Frameworks/CFNetwork.framework/Versions/A/CFNetwork
0x7fff88369000 - 0x7fff88376ff0 libbz2.1.0.dylib (29) <0B98AC35-B138-349C-8063-2B987A75D24C> /usr/lib/libbz2.1.0.dylib
0x7fff88381000 - 0x7fff88382fff libunc.dylib (28) <62682455-1862-36FE-8A04-7A6B91256438> /usr/lib/system/libunc.dylib
0x7fff8890e000 - 0x7fff889f5ff7 libxml2.2.dylib (26) <A1DADD11-89E5-3DE4-8802-07186225967F> /usr/lib/libxml2.2.dylib
0x7fff88c95000 - 0x7fff88c9afff com.apple.DiskArbitration (2.6 - 2.6) <A4165553-770E-3D27-B217-01FC1F852B87> /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration
0x7fff88ccd000 - 0x7fff88cf4ff7 libsystem_network.dylib (241.3) <8B1E1F1D-A5CC-3BAE-8B1E-ABC84337A364> /usr/lib/system/libsystem_network.dylib
0x7fff88cf5000 - 0x7fff88d05fff libbsm.0.dylib (33) <2CAC00A2-1352-302A-88FA-C567D4D69179> /usr/lib/libbsm.0.dylib
0x7fff88dc5000 - 0x7fff88defff7 libsandbox.1.dylib (278.11) <BD3D8652-8871-36DB-A27D-3BE4F18428B4> /usr/lib/libsandbox.1.dylib
0x7fff88eda000 - 0x7fff89092ffb libicucore.A.dylib (511.32) <A7CE7DAD-D3AD-36A2-BE4F-25C5F21FADBB> /usr/lib/libicucore.A.dylib
0x7fff8a23f000 - 0x7fff8a246fff com.apple.NetFS (6.0 - 4.0) <8E26C099-CE9D-3819-91A2-64EA929C6137> /System/Library/Frameworks/NetFS.framework/Versions/A/NetFS
0x7fff8a34b000 - 0x7fff8a355fff libcommonCrypto.dylib (60049) <8C4F0CA0-389C-3EDC-B155-E62DD2187E1D> /usr/lib/system/libcommonCrypto.dylib
0x7fff8a51b000 - 0x7fff8a51cfff liblangid.dylib (117) <9546E641-F730-3AB0-B3CD-E0E2FDD173D9> /usr/lib/liblangid.dylib
0x7fff8a5e0000 - 0x7fff8a78df27 libobjc.A.dylib (551.1) <AD7FD984-271E-30F4-A361-6B20319EC73B> /usr/lib/libobjc.A.dylib
0x7fff8b37c000 - 0x7fff8b380ff7 libsystem_stats.dylib (93.90.3) <4E51D5B0-92A0-3D0D-B90E-495A1ED3E391> /usr/lib/system/libsystem_stats.dylib
0x7fff8b5fc000 - 0x7fff8b603ff3 libcopyfile.dylib (103) <5A881779-D0D6-3029-B371-E3021C2DDA5E> /usr/lib/system/libcopyfile.dylib
0x7fff8ba8e000 - 0x7fff8baa9ff7 libCRFSuite.dylib (34) <FFAE75FA-C54E-398B-AA97-18164CD9789D> /usr/lib/libCRFSuite.dylib
0x7fff8c418000 - 0x7fff8c4a8ff7 com.apple.Metadata (10.7.0 - 800.28) <E85AEB1B-CB17-38BC-B5C6-AAB50B47AF05> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadat a.framework/Versions/A/Metadata
0x7fff8ca1a000 - 0x7fff8ca34fff libdispatch.dylib (339.92.1) <C4E4A18D-3C3B-3C9C-8709-A4270D998DE7> /usr/lib/system/libdispatch.dylib
0x7fff8caba000 - 0x7fff8cda4fff com.apple.CoreServices.CarbonCore (1077.17 - 1077.17) <3A2E92FD-DEE2-3D45-9619-11500801A61C> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonC ore.framework/Versions/A/CarbonCore
0x7fff8cda5000 - 0x7fff8cdb0ff7 com.apple.NetAuth (5.0 - 5.0) <C811E662-9EC3-3B74-808A-A75D624F326B> /System/Library/PrivateFrameworks/NetAuth.framework/Versions/A/NetAuth
0x7fff8ce57000 - 0x7fff8ce5efff libcompiler_rt.dylib (35) <4CD916B2-1B17-362A-B403-EF24A1DAC141> /usr/lib/system/libcompiler_rt.dylib
0x7fff8ce5f000 - 0x7fff8ce64ff7 libunwind.dylib (35.3) <78DCC358-2FC1-302E-B395-0155B47CB547> /usr/lib/system/libunwind.dylib
0x7fff8ce65000 - 0x7fff8ce65ffd libOpenScriptingUtil.dylib (157) <19F0E769-0989-3062-9AFB-8976E90E9759> /usr/lib/libOpenScriptingUtil.dylib
0x7fff8d22e000 - 0x7fff8d29afff com.apple.framework.IOKit (2.0.1 - 907.100.13) <057FDBA3-56D6-3903-8C0B-849214BF1985> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
0x7fff8d2a7000 - 0x7fff8d501ffd com.apple.security (7.0 - 55471.14.4) <1D5DA20E-DB48-3E1D-9BF5-BAA694192B25> /System/Library/Frameworks/Security.framework/Versions/A/Security
0x7fff8d59d000 - 0x7fff8d59effb libremovefile.dylib (33) <3543F917-928E-3DB2-A2F4-7AB73B4970EF> /usr/lib/system/libremovefile.dylib
0x7fff8d65f000 - 0x7fff8d662fff com.apple.TCC (1.0 - 1) <32A075D9-47FD-3E71-95BC-BFB0D583F41C> /System/Library/PrivateFrameworks/TCC.framework/Versions/A/TCC
0x7fff8deee000 - 0x7fff8df3cfff libcorecrypto.dylib (161.1) <F3973C28-14B6-3006-BB2B-00DD7F09ABC7> /usr/lib/system/libcorecrypto.dylib
0x7fff8dfbc000 - 0x7fff8dfbcfff com.apple.CoreServices (59 - 59) <7A697B5E-F179-30DF-93F2-8B503CEEEFD5> /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices
0x7fff8dfbd000 - 0x7fff8dfd9ff7 libsystem_kernel.dylib (2422.100.13) <498AEBD7-4194-3CF2-AA16-D5D03FFBD8C0> /usr/lib/system/libsystem_kernel.dylib
0x7fff8dfda000 - 0x7fff8e002ffb libxslt.1.dylib (13) <C9794936-633C-3F0C-9E71-30190B9B41C1> /usr/lib/libxslt.1.dylib
0x7fff8e2ed000 - 0x7fff8e2efff7 libquarantine.dylib (71) <7A1A2BCB-C03D-3A25-BFA4-3E569B2D2C38> /usr/lib/system/libquarantine.dylib
0x7fff8e2f0000 - 0x7fff8e314fff libxpc.dylib (300.90.2) <AB40CD57-F454-3FD4-B415-63B3C0D5C624> /usr/lib/system/libxpc.dylib
0x7fff8e58f000 - 0x7fff8e597fff libsystem_dnssd.dylib (522.90.2) <A0B7CF19-D9F2-33D4-8107-A62184C9066E> /usr/lib/system/libsystem_dnssd.dylib
0x7fff8f591000 - 0x7fff8f67bfff libsqlite3.dylib (158) <00269BF9-43BE-39E0-9C85-24585B9923C8> /usr/lib/libsqlite3.dylib
0x7fff8f67c000 - 0x7fff8f685ff3 libsystem_notify.dylib (121) <52571EC3-6894-37E4-946E-064B021ED44E> /usr/lib/system/libsystem_notify.dylib
0x7fff8f686000 - 0x7fff8f693ff7 libxar.1.dylib (202) <5572AA71-E98D-3FE1-9402-BB4A84E0E71E> /usr/lib/libxar.1.dylib
0x7fff8fb83000 - 0x7fff8fb8fff3 com.apple.AppleFSCompression (56 - 1.0) <5652B0D0-EB08-381F-B23A-6DCF96991FB5> /System/Library/PrivateFrameworks/AppleFSCompression.framework/Versions/A/Apple FSCompression
0x7fff8fcf9000 - 0x7fff8fdc2fff com.apple.LaunchServices (572.26 - 572.26) <EF8A4A15-0861-35C5-9744-5E1BC5C26DD9> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchS ervices.framework/Versions/A/LaunchServices
0x7fff90220000 - 0x7fff9027bffb com.apple.AE (665.5 - 665.5) <BBA230F9-144C-3CAB-A77A-0621719244CD> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/AE.fram ework/Versions/A/AE
0x7fff90577000 - 0x7fff9057dff7 libsystem_platform.dylib (24.90.1) <3C3D3DA8-32B9-3243-98EC-D89B9A1670B3> /usr/lib/system/libsystem_platform.dylib
0x7fff9057e000 - 0x7fff90589fff libkxld.dylib (2422.100.13) <67D079F8-6C48-3F42-9FBE-26F1ADA03DC4> /usr/lib/system/libkxld.dylib
0x7fff906ba000 - 0x7fff90743ff7 libsystem_c.dylib (997.90.3) <6FD3A400-4BB2-3B95-B90C-BE6E9D0D78FA> /usr/lib/system/libsystem_c.dylib
0x7fff90744000 - 0x7fff9075bff7 com.apple.CFOpenDirectory (10.9 - 173.90.1) <EBC0A1F2-9054-3D39-99AE-A3F655E55D6A> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/Frameworks/CFOpen Directory.framework/Versions/A/CFOpenDirectory
0x7fff909e5000 - 0x7fff90a14fd2 libsystem_m.dylib (3047.16) <B7F0E2E4-2777-33FC-A787-D6430B630D54> /usr/lib/system/libsystem_m.dylib
0x7fff90a15000 - 0x7fff90a1cff7 libsystem_pthread.dylib (53.1.4) <AB498556-B555-310E-9041-F67EC9E00E2C> /usr/lib/system/libsystem_pthread.dylib
0x7fff917ee000 - 0x7fff917f0ff3 libsystem_configuration.dylib (596.15) <4998CB6A-9D54-390A-9F57-5D1AC53C135C> /usr/lib/system/libsystem_configuration.dylib
0x7fff9184d000 - 0x7fff91874ffb libsystem_info.dylib (449.1.3) <7D41A156-D285-3849-A2C3-C04ADE797D98> /usr/lib/system/libsystem_info.dylib
0x7fff919a7000 - 0x7fff919a8ff7 libSystem.B.dylib (1197.1.1) <E303F2F8-A8CF-3DF3-84B3-F2D0EE41CCF6> /usr/lib/libSystem.B.dylib
0x7fff919a9000 - 0x7fff919c4ff7 libsystem_malloc.dylib (23.10.1) <A695B4E4-38E9-332E-A772-29D31E3F1385> /usr/lib/system/libsystem_malloc.dylib
0x7fff919c5000 - 0x7fff91a07ff7 libauto.dylib (185.5) <F45C36E8-B606-3886-B5B1-B6745E757CA8> /usr/lib/libauto.dylib
0x7fff91a0a000 - 0x7fff91a0bff7 libsystem_sandbox.dylib (278.11) <B46E4040-A8C6-3EBC-91F8-F1CB01106614> /usr/lib/system/libsystem_sandbox.dylib
0x7fff91a64000 - 0x7fff91a64ff7 libkeymgr.dylib (28) <3AA8D85D-CF00-3BD3-A5A0-E28E1A32A6D8> /usr/lib/system/libkeymgr.dylib
0x7fff91a84000 - 0x7fff91ae7ffb com.apple.SystemConfiguration (1.13.1 - 1.13.1) <2C8E1A73-5AD6-3A7D-8ED8-D6755555A993> /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfi guration
0x7fff91ae8000 - 0x7fff91af9ff7 libsystem_asl.dylib (217.1.4) <655FB343-52CF-3E2F-B14D-BEBF5AAEF94D> /usr/lib/system/libsystem_asl.dylib
0x7fff91ed6000 - 0x7fff91f4dfff com.apple.CoreServices.OSServices (600.4 - 600.4) <C63562F5-6DF5-3EE9-8897-FF61A44C8251> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServi ces.framework/Versions/A/OSServices
0x7fff91f7f000 - 0x7fff91fe3fff com.apple.datadetectorscore (5.0 - 354.4) <37093186-6019-3071-8D67-F3EF429F8F08> /System/Library/PrivateFrameworks/DataDetectorsCore.framework/Versions/A/DataDe tectorsCore
0x7fff925a1000 - 0x7fff925f3fff libc++.1.dylib (120) <4F68DFC5-2077-39A8-A449-CAC5FDEE7BDE> /usr/lib/libc++.1.dylib
0x7fff92fc7000 - 0x7fff92fc8ff7 libsystem_blocks.dylib (63) <FB856CD1-2AEA-3907-8E9B-1E54B6827F82> /usr/lib/system/libsystem_blocks.dylib
0x7fff93293000 - 0x7fff9329aff8 liblaunch.dylib (842.90.1) <38D1AB2C-A476-385F-8EA8-7AB604CA1F89> /usr/lib/system/liblaunch.dylib
0x7fff933f5000 - 0x7fff933ffff7 com.apple.bsd.ServiceManagement (2.0 - 2.0) <2D27B498-BB9C-3D88-B05A-76908A8A26F3> /System/Library/Frameworks/ServiceManagement.framework/Versions/A/ServiceManage ment
0x7fff93427000 - 0x7fff93428ff7 libDiagnosticMessagesClient.dylib (100) <4CDB0F7B-C0AF-3424-BC39-495696F0DB1E> /usr/lib/libDiagnosticMessagesClient.dylib
0x7fff93459000 - 0x7fff93482ff7 libc++abi.dylib (49.1) <21A807D3-6732-3455-B77F-743E9F916DF0> /usr/lib/libc++abi.dylib
External Modification Summary:
Calls made by other processes targeting this process:
task_for_pid: 0
thread_create: 0
thread_set_state: 0
Calls made by this process:
task_for_pid: 0
thread_create: 0
thread_set_state: 0
Calls made by all processes on this machine:
task_for_pid: 35874
thread_create: 0
thread_set_state: 0
VM Region Summary:
ReadOnly portion of Libraries: Total=92.0M resident=45.1M(49%) swapped_out_or_unallocated=46.9M(51%)
Writable regions: Total=84.3M written=860K(1%) resident=1036K(1%) swapped_out=0K(0%) unallocated=83.3M(99%)
REGION TYPE VIRTUAL
=========== =======
Dispatch continuations 16.0M
Kernel Alloc Once 4K
MALLOC 56.2M
MALLOC (admin) 16K
SQLite page cache 256K
STACK GUARD 56.0M
Stack 11.6M
VM_ALLOCATE 12K
VM_ALLOCATE (reserved) 12K reserved VM address space (unallocated)
__DATA 3160K
__LINKEDIT 66.1M
__TEXT 25.9M
__UNICODE 544K
shared memory 4K
=========== =======
TOTAL 235.7M
TOTAL, minus reserved VM space 235.7MIf you want help with your problem, you're going to have to try harder than that. You're also going to have to be more polite.
"Crashing" means different things to different people. Is there an error message? Do you have to restart?
Maybe you are looking for
-
No "Submit to SAP" button, the submit button offered doesn't work
Hello everyone, I am working with the interactive forms and I have tried going through the PDF about how to use an RFC with the interactive forms. During the tutorial, they say to add a button called "Submit to SAP", but I don't have one. I have gr
-
How to connect oracle8.0.3
how to connect the oracle database by using oracle thin driver
-
Jdbc connectivity with mysql database
I created a database in mysql, but I have problems communicating with the DB in java here is the error java.sql.SQLException: No suitable driver found for jdbc:mysql://localhost:3306/books at java.sql.DriverManager.getConnection(DriverManager.java:6
-
hi i'm using a jtree in my gui but im facing a problem jTree1.addTreeSelectionListener(new TreeSelectionListener() { public void valueChanged(TreeSelectionEvent e) jTree1_valueChange(e); as you can see that whenever
-
Invalid input syntax for type boolean???? ahhhhhh
Hey all, Has anyone come accross the 'invalid input syntax for type boolean' error - its driving me crazy trying to figure out what is wrong with my function/java code!!! The postgres (using 8.1) function is: CREATE OR REPLACE FUNCTION selectstaffrol