Crash in Scarab when a large number of connections are active
Reported by David Cox | January 23rd, 2009 @ 09:17 AM | in 0.4.4
Manifests in the Client when there are many servers connected. No obvious pattern to when it happens – seems to occur randomly.
Crash looks like this:
Thread 32 Crashed: 0 edu.mit.MonkeyWorksCore 0x00b822eb scarab_session_geterr + 9 1 edu.mit.MonkeyWorksCore 0x0092b00b getScarabError(__ScarabSession*) + 17 2 edu.mit.MonkeyWorksCore 0x00916043 mScarabWriteConnection::service() + 159 3 edu.mit.MonkeyWorksCore 0x00915cd1 write(void*) + 31 4 ....LowPrioritySchedulerPlugin 0x001ebef2 low_priority_scheduler::zenScheduledExecutionThread(void*) + 586 5 libSystem.B.dylib 0x902576f5 _pthread_start + 321 6 libSystem.B.dylib 0x902575b2 thread_start + 34
Comments and changes to this ticket
-
David Cox February 4th, 2010 @ 02:20 PM
- State changed from “new” to “open”
Some changes on the path to 10.6 (removal of garbage collection) may have already resolved this issue. I'm going to leave it active, however, until we have a recent release candidate deployed in a "production" environment for a while.
-
David Cox May 3rd, 2010 @ 03:31 PM
- State changed from “open” to “resolved”
We haven't seen this intermittent crash in many moons, so I am going to close it for now, assuming the above described fixes have removed the problem. We can reopen/refile if it resurfaces.
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
The core framework and supporting libraries for the MWorks Suite
David Cox