Opened 4 years ago
Last modified 17 months ago
#6147 assigned enhancement
Make bundle and manager/provider initialize in predictable order
Reported by: | Tom Goddard | Owned by: | Greg Couch |
---|---|---|---|
Priority: | high | Milestone: | |
Component: | Tool Shed | Version: | |
Keywords: | Cc: | pett, Tristan Croll | |
Blocked By: | Blocking: | ||
Notify when closed: | Platform: | all | |
Project: | ChimeraX |
Description (last modified by )
Tristan spent immense effort debugging a startup crash #6131 which was not reproducible due to random initialization order of manager/provider.
We have many other tickets of random startup errors and crashes that we have never been able to debug because they are not reproducible.
Initialization of bundles and manager/provider should use the same order at every startup so these problems can be debugged.
Change History (7)
comment:1 by , 4 years ago
follow-up: 2 comment:2 by , 4 years ago
Ok. Then read this ticket as "Make sure startup is in predictable order".
comment:3 by , 3 years ago
Milestone: | 1.4 → 1.5 |
---|
comment:4 by , 3 years ago
Milestone: | 1.5 → 1.6 |
---|
comment:5 by , 3 years ago
Milestone: | 1.6 → 1.7 |
---|
comment:6 by , 2 years ago
Description: | modified (diff) |
---|---|
Milestone: | 1.7 → 1.8 |
comment:7 by , 17 months ago
Milestone: | 1.8 |
---|
Note:
See TracTickets
for help on using tickets.
I don't know that it's not deterministic. That wasn't the problem in ticket #6131. The problem there was that there were multiple bundles claiming the .pdb prefix and the ZDOCK (viewdockx) bundle had not declared itself as not the default opener, so which opener got chosen depended on dictionary order. When I'm not on vacation I intend to have the code issue a warning when that situation occurs.