
| Key: |
SVC-53
|
| Type: |
Bug
|
| Status: |
Resolved
|
| Resolution: |
Misfiled
|
| Priority: |
Showstopper
|
| Assignee: |
Unassigned
|
| Reporter: |
Olivia Yering
|
| Votes: |
9
|
| Watchers: |
0
|
|
If you were logged in you would be able to see more operations.
|
|
|
|
Issue Links:
|
Duplicate
|
|
|
|
This issue is original of duplicate:
|
|
VWR-134
Linux FL viewer locks up on start w/nVidia MCP51
|
|
|
|
|
Relates
|
|
This issue Relates to:
|
|
|
VWR-3568 Meta-Issue: Crashes and bugs on startup / login
|
|
|
|
|
|
This issue is related to by:
|
|
SVC-437
Login fails because system is logging you out
|
|
|
|
 |
VWR-1911
hanging at connecting to region unless the -noquicktime commandline option is used
|
|
|
|
|
SVC-162
"Double teleport screen" bug freezes your avatar and requires viewer restart
|
|
|
|
|
|
|
Login freeze on LLCircuit::addCircuitData
About halfway through the connection process (blue progress bar at ~50%, message "Connecting to Region"), the client completely stops responding, the progress bar stops throbbing, CPU Usage drops to 0, and forceful killing is required to terminate the client. The console window usually displays the output "LLCircuit::addCircuitData" as the last message before this freeze occurs.
This happens regardless of time of day, previous connection/disconnection status, region, use of router, NAT, etc. This happens very often, but not 100% of the time.
This does not appear to effect the Windows client.
|
|
Description
|
Login freeze on LLCircuit::addCircuitData
About halfway through the connection process (blue progress bar at ~50%, message "Connecting to Region"), the client completely stops responding, the progress bar stops throbbing, CPU Usage drops to 0, and forceful killing is required to terminate the client. The console window usually displays the output "LLCircuit::addCircuitData" as the last message before this freeze occurs.
This happens regardless of time of day, previous connection/disconnection status, region, use of router, NAT, etc. This happens very often, but not 100% of the time.
This does not appear to effect the Windows client. |
Show » |
made changes - 14/Apr/07 07:28 AM
| Field |
Original Value |
New Value |
|
Component/s
|
|
Simulation
[ 10042
]
|
made changes - 26/Apr/07 11:02 PM
|
Resolution
|
|
Cannot Reproduce
[ 5
]
|
|
Status
|
Open
[ 1
]
|
Resolved
[ 5
]
|
made changes - 30/Apr/07 03:56 AM
|
Resolution
|
Cannot Reproduce
[ 5
]
|
|
|
Status
|
Resolved
[ 5
]
|
Reopened
[ 4
]
|
made changes - 30/Apr/07 07:09 AM
|
Description
|
|
Login freeze on LLCircuit::addCircuitData
|
|
Summary
|
Cannot log in-freezes at "Connecting to Region", relog message says "your service will be available in (5 minutes from the current time)"
|
Cannot log in-freezes at "Connecting to Region"
|
made changes - 01/May/07 07:44 AM
|
Priority
|
Major
[ 3
]
|
Blocker
[ 1
]
|
made changes - 02/May/07 12:07 PM
|
Link
|
|
This issue is related to by VWR-626
[ VWR-626
]
|
made changes - 02/May/07 12:19 PM
|
Link
|
|
This issue is duplicated by SVC-162
[ SVC-162
]
|
made changes - 02/May/07 12:20 PM
|
Link
|
This issue is duplicated by SVC-162
[ SVC-162
]
|
|
made changes - 02/May/07 12:22 PM
|
Link
|
|
This issue is related to by SVC-162
[ SVC-162
]
|
made changes - 11/May/07 10:26 AM
|
Summary
|
Cannot log in-freezes at "Connecting to Region"
|
Login -> Freeze -> LLCircuit::addCircuitData
|
made changes - 11/May/07 10:30 AM
|
Status
|
Reopened
[ 4
]
|
Resolved
[ 5
]
|
|
Resolution
|
|
Cannot Reproduce
[ 5
]
|
made changes - 15/May/07 07:19 AM
|
Description
|
Login freeze on LLCircuit::addCircuitData
|
Login freeze on LLCircuit::addCircuitData
About halfway through the connection process (blue progress bar at ~50%, message "Connecting to Region"), the client completely stops responding, the progress bar stops throbbing, CPU Usage drops to 0, and forceful killing is required to terminate the client. The console window usually displays the output "LLCircuit::addCircuitData" as the last message before this freeze occurs.
This happens regardless of time of day, previous connection/disconnection status, region, use of router, NAT, etc. This happens very often, but not 100% of the time.
This does not appear to effect the Windows client.
|
made changes - 21/May/07 06:19 AM
|
Link
|
|
This issue is duplicated by VWR-134
[ VWR-134
]
|
made changes - 24/May/07 04:22 AM
|
Status
|
Resolved
[ 5
]
|
Reopened
[ 4
]
|
|
Resolution
|
Cannot Reproduce
[ 5
]
|
|
made changes - 01/Jul/07 12:12 AM
|
Status
|
Reopened
[ 4
]
|
Resolved
[ 5
]
|
|
Resolution
|
|
Misfiled
[ 6
]
|
made changes - 28/Jul/07 08:59 AM
|
Link
|
|
This issue is related to by VWR-1911
[ VWR-1911
]
|
made changes - 01/Dec/07 05:19 AM
|
Link
|
|
This issue Relates to VWR-3568
[ VWR-3568
]
|
made changes - 22/Dec/07 01:23 AM
|
Workflow
|
jira
[ 10553
]
|
jira-2007-12-21
[ 21908
]
|
made changes - 23/Dec/07 12:24 AM
|
Workflow
|
jira-2007-12-21
[ 21908
]
|
jira-2007-12-22a
[ 48776
]
|
made changes - 13/Nov/08 12:07 PM
|
Workflow
|
jira-2007-12-22a
[ 48776
]
|
jira-2008-11-14
[ 81730
]
|
made changes - 13/Nov/08 04:36 PM
|
Workflow
|
jira-2008-11-14
[ 81730
]
|
jira-2008-11-14a
[ 88850
]
|
|