MantisBT - Zandronum |
| View Issue Details |
|
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0004198 | Zandronum | [All Projects] Bug | public | 2024-02-26 08:41 | 2024-03-01 14:37 |
|
| Reporter | Apollonius | |
| Assigned To | | |
| Priority | normal | Severity | crash | Reproducibility | always |
| Status | resolved | Resolution | fixed | |
| Platform | Linux | OS | Mint | OS Version | 21.3 |
| Product Version | 3.1 | |
| Target Version | | Fixed in Version | 3.2 | |
|
| Summary | 0004198: Address not mapped to object (signal 11) |
| Description | Whenever I try to access multiplayer servers, it will freeze, repeat "WARNING: Please wait a full 10 seconds before refreshing the server list", and then the debug console will produce the following error and the game will crash:
*** Fatal Error ***
Address not mapped to object (signal 11)
Address: 0xfffffffffffffff4
Generating [crash log] and killing process [pid], please wait... 30 ../sysdeps/unix/sysv/linux/wait4.c: No such file or directory.
warning: Memory read failed for corefile section, 4096 bytes at 0xffffffffff600000.
sh: 1: gxmessage: not found
Killed
One of the crash logs is attached for reference |
| Steps To Reproduce | 1. Open Zandronum (with freedm.wad IWAD, the only one I have in ~/.config/zandronum)
2. Go to Options
3. Go to Multiplayer Options
4. Go to Browse Servers
5. Get a crash |
| Additional Information | I'm using the freedm.wad IWAD from Freedoom |
| Tags | No tags attached. |
| Relationships | |
| Attached Files |  zandronum-crash-02_26_2024-00_14_37.58349.log (47,014) 2024-02-26 08:41
https://zandronum.com/tracker/file_download.php?file_id=2903&type=bug |
|
| Issue History |
| Date Modified | Username | Field | Change |
| 2024-02-26 08:41 | Apollonius | New Issue | |
| 2024-02-26 08:41 | Apollonius | File Added: zandronum-crash-02_26_2024-00_14_37.58349.log | |
| 2024-02-26 09:31 | Apollonius | Note Added: 0023090 | |
| 2024-02-26 15:04 | Kaminsky | Note Added: 0023091 | |
| 2024-02-26 15:04 | Kaminsky | Severity | minor => crash |
| 2024-02-26 15:04 | Kaminsky | Status | new => needs testing |
| 2024-02-27 06:22 | Apollonius | Note Added: 0023094 | |
| 2024-03-01 14:36 | Kaminsky | Note Added: 0023166 | |
| 2024-03-01 14:36 | Kaminsky | Status | needs testing => resolved |
| 2024-03-01 14:36 | Kaminsky | Fixed in Version | => 3.2 |
| 2024-03-01 14:36 | Kaminsky | Resolution | open => fixed |
| 2024-03-01 14:36 | Kaminsky | Assigned To | => Kaminsky |
| 2024-03-01 14:37 | Kaminsky | Assigned To | Kaminsky => |
|
Notes |
|
|
|
|
SEVERITY SHOULD BE *CRASH*, NOT *MINOR* |
|
|
|
|
|
This should've been fixed in 3.2 already. Can you please test with the latest beta (230709-1914) to confirm that? |
|
|
|
|
|
Updated to 3.2 flatpak and issue no longer applies |
|
|
|
|
|
Thanks for checking, I'll mark this as resolved then. |
|