FROM : Becky Willrich
DATE : Mon Apr 25 19:34:27 2005
> I think it never returns. The app still runs (windows move, a
> Progress Indicator keeps spinning, etc) but it never returns from
> the requestWithURL call.
I don't think that call can possibly be responsible for the hang; it
does nothing but allocate a chunk of memory and write some values in
to it. It doesn't touch the network or anything. Try running your
application, letting it hang, and sampling it while it's hanging
("sample <process name> 3" in Terminal); that will give you a better
picture of where the code is stuck.
REW
DATE : Mon Apr 25 19:34:27 2005
> I think it never returns. The app still runs (windows move, a
> Progress Indicator keeps spinning, etc) but it never returns from
> the requestWithURL call.
I don't think that call can possibly be responsible for the hang; it
does nothing but allocate a chunk of memory and write some values in
to it. It doesn't touch the network or anything. Try running your
application, letting it hang, and sampling it while it's hanging
("sample <process name> 3" in Terminal); that will give you a better
picture of where the code is stuck.
REW
| Related mails | Author | Date |
|---|---|---|
| Miguel Arroz | Apr 24, 21:06 | |
| Marc Respass | Apr 25, 17:04 | |
| Miguel Arroz | Apr 25, 19:24 | |
| Becky Willrich | Apr 25, 19:34 | |
| Markus Hitter | Apr 25, 20:32 | |
| Miguel Arroz | Apr 25, 23:54 |






Cocoa mail archive

