Opened 9 years ago
Closed 9 years ago
#3493 closed defect (needsinfo)
[NEEDS INFO] Segfault when minimizing
| Reported by: | elexis | Owned by: | |
|---|---|---|---|
| Priority: | Must Have | Milestone: | |
| Component: | Core engine | Keywords: | |
| Cc: | Patch: |
Description
Today Arthur_D late-joined as a spectator (-> #3242) when playing a match in r17108. He was able to see turns 1723-3070 and then got a segfault.
Replaying the commands.txt of the host doesn't cause a segfault (on my linux system).
Probably not caused by the late-join feature as that only changed the boolean value isRejoining and cleaned the rejoin mechanism, see http://trac.wildfiregames.com/changeset/16945#file5.
Attachments (1)
Change History (5)
by , 9 years ago
comment:1 by , 9 years ago
Replaying the commands.txt doesn't crash (tested by Stan, Arthur and me).
Notice he said "I had another game running as well and I tried to minimize 0ad when it segfaulted". Since he uses linux, having multiple instances should not crash.
comment:2 by , 9 years ago
| Milestone: | Alpha 19 → Alpha 20 |
|---|---|
| Summary: | Segfault on rejoin → Segfault when minimizing |
comment:3 by , 9 years ago
Is it reproducible? If not, I wouldn't call it a release blocker. Ideally we would have a call stack from the crash and some steps to reproduce it.
comment:4 by , 9 years ago
| Milestone: | Alpha 20 |
|---|---|
| Priority: | Release Blocker → Must Have |
| Resolution: | → needsinfo |
| Status: | new → closed |
| Summary: | Segfault when minimizing → [NEEDS INFO] Segfault when minimizing |
No, can't reproduce for now. He tried to play around with having multiple instances of the game running and minimizing/maximizing quickly. Will reopen if we have more intel.
Logfiles including
commands.txtof rejoined and non-rejoined clients. No crash dumps.