RE: xcode 2.2 beachball of death
RE: xcode 2.2 beachball of death
- Subject: RE: xcode 2.2 beachball of death
- From: Gregory Olds <email@hidden>
- Date: Tue, 29 Nov 2005 20:54:28 -0500
I have a similar problem that is reproducible. The following code
causes XCode to hang. 100% of the time on my machine. I get the
spinning beachball, high usage of my processors (Dual 2.5 G5) and
all I can do is terminate XCode.
Any ideas?
-Greg
The following is unfinished code I'm writing for a project I have
to turn in for class:
#include <iostream>
using namespace std;
void chain_code(char img[][]);
int main () {
string image_file, output_image;
int r, c;
double min, max;
ifstream iFile;
ofstream oFile;
char origional_img[25][30];
cout << "Enter the name of the image" << endl;
cin >> image_file;
//Reading in the origional image
iFile.open(image_file.c_str());
if(!iFile)
{
cout << "could not open file";
return 0;
}
for (int i = 0; i < 25; i++)
{
for(int j = 0; j < 30; j++)
{
origional_img[i][j] = iFile.get();
}
}
iFile.close();
}
void chain_code(char img[][])
{
//find where the image object starts
int x =0; int y = 0;
for (x; x< 25
I get to this point and XCode hangs. I restart XCode (the file is
saved) and it hangs.
On Nov 17, 2005, at 7:39 PM, Rick Ballard wrote:
On Nov 17, 2005, at 3:56 AM, Robert Dell wrote:
mine too was cured by reboot.
Jerry wrote:
On 17 Nov 2005, at 00:41, Alan Nilsson wrote:
I have 3 machines that I recently upgraded to xcode 2.2.
One works as expected. (1.6 G5 / 10.4.2)
The other two, upon launching xcode, xcode immediately gives a
beach ball and becomes non responsive. Top shows xcode chewing
up 100% of the processor. I let this go on for 30 minutes on
both machines with no change before I killed them and down
graded back to 2.1 (which runs correctly).
Configs of machines not working:
Dual 2.5 G5 / 10.4.1 & 1.5 G4 PB / 10.4.3
Anyone else seen similar behavior?
I had this, or something similar, happen on my Powerbook, but it
was cured by a restart. My iMac G5 and dual G5 were fine.
Jerry
The problem in Alan's case turned out to be a script in his
Scripts folder (/Library/Application Support/Apple/Developer
Tools/Scripts or ~/Library/Application Support/Apple/Developer
Tools/Scripts) which was causing the hang.
- Rick
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40comcast.net
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden