Bugs in 4.2.0

[dionysian]

Carrying the phial, so I should have light... but in the town, I've got light 0 unless I'm standing adjacent to a shop entrance. This has happened before, but I'm not sure what causes it.

edit: This was happening during the day. I rested in town until the sun fell, and then the behavior went back to normal.

[Huqhox]

Originally Posted by dionysian

Carrying the phial, so I should have light... but in the town, I've got light 0 unless I'm standing adjacent to a shop entrance. This has happened before, but I'm not sure what causes it.

edit: This was happening during the day. I rested in town until the sun fell, and then the behavior went back to normal.

This was changed a little while ago (3.0.? or thereabouts) so that lights are effective unequipped during daylight in the town

This was done because otherwise when you appeared in the town you had to remember to unequip your torch or lantern to stop it wasting fuel, and then remember to equip it again when you entered the dungeon. It just helped to streamline things

It obviously extends to permanent light sources as well. But that seems reasonable?

[dionysian]

That makes sense, except for the inability to read scrolls or browse/cast spells in broad daylight.

[wobbly]

Quick question, is persistent levels on or off? The last person to hit this bug was playing with persistent levels on. Your light is off because its daylight but for some reason the town level hasn't illuminated properly.

[wobbly]

Yeah I can reproduce this pretty easily. At least with persistent levels on. Go to the general store buy a bunch of food rations. Go down the stairs & rest on the up stairs until its night. Go up stairs. The level is still lit even though its night. Alternatively if you repeat this, except you wait till night to go down the stairs then when you come back up its still dark, even though its day.

[wobbly]

lava still burns you on the turn you tele-level

[dionysian]

I posted about this in a separate thread, but didn't get any response. I'm considering it a bug because it gives the player nearly game breaking unearned information...

Using persistent levels, upon leaving a level, artifact knowledge (using the ~ screen) is updated with any artifacts that were generated. The player didn't have to explore any of the dungeon or get an item feeling for the level. You can literally enter a level, go right back up the stairs and check if there is any artifact to go back for. It's a bit scummy to act on that knowledge, but it seems like the kind of thing that should be hidden from the player anyway.

[Nick]

OK, bug filed for persistent levels issues, I'll try and fix them faster than they crop up...

[lonadar]

I don't know if this is the proper form for this specific type of post, but twice under 4.2 I've had my application just up and die. I didn't catch the crash report from the first one but I have for this, so here it is in all it's glory. If posts of this length belong elsewhere, I apologize:

Process: angband [23013]
Path: /Applications/Angband.app/Contents/MacOS/angband
Identifier: angband
Version: 4.2.0-dirty (???)
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: angband [23013]
User ID: 502

Date/Time: 2019-11-16 09:14:09.156 -0500
OS Version: Mac OS X 10.13.6 (17G9016)
Report Version: 12

Time Awake Since Boot: 1500000 seconds

System Integrity Protection: enabled

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000078
Exception Note: EXC_CORPSE_NOTIFY

Termination Signal: Segmentation fault: 11
Termination Reason: Namespace SIGNAL, Code 0xb
Terminating Process: exc handler [0]

VM Regions Near 0x78:
-->
__TEXT 0000000109eb3000-0000000109fb8000 [ 1044K] r-x/rwx SM=COW /Applications/Angband.app/Contents/MacOS/angband

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 org.rephial.angband 0x0000000109f510f7 hit_trap + 583
1 org.rephial.angband 0x0000000109f0768a monster_swap + 522
2 org.rephial.angband 0x0000000109ebeb7d move_player + 621
3 org.rephial.angband 0x0000000109ebeeae do_cmd_walk + 318
4 org.rephial.angband 0x0000000109ebff41 process_command + 369
5 org.rephial.angband 0x0000000109ec00ef cmdq_pop + 111
6 org.rephial.angband 0x0000000109ecfaf9 process_player + 377
7 org.rephial.angband 0x0000000109ecfe8e run_game_loop + 46
8 org.rephial.angband 0x0000000109f5be32 play_game + 258
9 org.rephial.angband 0x0000000109f8f988 +[AngbandContext beginGame] + 1560
10 org.rephial.angband 0x0000000109f92bf2 -[AngbandAppDelegate applicationDidFinishLaunching:] + 34
11 com.apple.CoreFoundation 0x00007fff36c2053c __CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERV ER__ + 12
12 com.apple.CoreFoundation 0x00007fff36c2040a _CFXRegistrationPost + 458
13 com.apple.CoreFoundation 0x00007fff36c20141 ___CFXNotificationPost_block_invoke + 225
14 com.apple.CoreFoundation 0x00007fff36bdecd2 -[_CFXNotificationRegistrar findbjectbserver:enumerator:] + 1826
15 com.apple.CoreFoundation 0x00007fff36bddd63 _CFXNotificationPost + 659
16 com.apple.Foundation 0x00007fff38d0c087 -[NSNotificationCenter postNotificationNamebject:userInfo:] + 66
17 com.apple.AppKit 0x00007fff342cc206 -[NSApplication _postDidFinishNotification] + 313
18 com.apple.AppKit 0x00007fff342cbe4f -[NSApplication _sendFinishLaunchingNotification] + 220
19 com.apple.AppKit 0x00007fff3419ea7b -[NSApplication(NSAppleEventHandling) _handleAEOpenEvent:] + 562
20 com.apple.AppKit 0x00007fff3419e6b1 -[NSApplication(NSAppleEventHandling) _handleCoreEvent:withReplyEvent:] + 690
21 com.apple.Foundation 0x00007fff38d4ef34 -[NSAppleEventManager dispatchRawAppleEvent:withRawReply:handlerRefCon:] + 287
22 com.apple.Foundation 0x00007fff38d4edb2 _NSAppleEventManagerGenericHandler + 102
23 com.apple.AE 0x00007fff37d26f08 aeDispatchAppleEvent(AEDesc const*, AEDesc*, unsigned int, unsigned char*) + 1788
24 com.apple.AE 0x00007fff37d267af dispatchEventAndSendReply(AEDesc const*, AEDesc*) + 41
25 com.apple.AE 0x00007fff37d2669d aeProcessAppleEvent + 383
26 com.apple.HIToolbox 0x00007fff35efa4a0 AEProcessAppleEvent + 55
27 com.apple.AppKit 0x00007fff34199cfa _DPSNextEvent + 2788
28 com.apple.AppKit 0x00007fff3492fe34 -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:deque ue:] + 3044
29 com.apple.AppKit 0x00007fff3418e84d -[NSApplication run] + 764
30 com.apple.AppKit 0x00007fff3415da3a NSApplicationMain + 804
31 org.rephial.angband 0x0000000109f92f99 main + 9
32 libdyld.dylib 0x00007fff5ec08015 start + 1

Thread 1:: com.apple.NSEventThread
0 libsystem_kernel.dylib 0x00007fff5ed4f20a mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff5ed4e724 mach_msg + 60
2 com.apple.CoreFoundation 0x00007fff36c0bf65 __CFRunLoopServiceMachPort + 341
3 com.apple.CoreFoundation 0x00007fff36c0b2b7 __CFRunLoopRun + 1783
4 com.apple.CoreFoundation 0x00007fff36c0a927 CFRunLoopRunSpecific + 487
5 com.apple.AppKit 0x00007fff342d6fc4 _NSEventThread + 184
6 libsystem_pthread.dylib 0x00007fff5ef20661 _pthread_body + 340
7 libsystem_pthread.dylib 0x00007fff5ef2050d _pthread_start + 377
8 libsystem_pthread.dylib 0x00007fff5ef1fbf9 thread_start + 13

Thread 2:
0 libsystem_kernel.dylib 0x00007fff5ed5928a __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x00007fff5ef20009 _pthread_wqthread + 1035
2 libsystem_pthread.dylib 0x00007fff5ef1fbe9 start_wqthread + 13

Thread 3:
0 libsystem_kernel.dylib 0x00007fff5ed5928a __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x00007fff5ef20009 _pthread_wqthread + 1035
2 libsystem_pthread.dylib 0x00007fff5ef1fbe9 start_wqthread + 13

Thread 4:
0 libsystem_kernel.dylib 0x00007fff5ed5928a __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x00007fff5ef2020e _pthread_wqthread + 1552
2 libsystem_pthread.dylib 0x00007fff5ef1fbe9 start_wqthread + 13

Thread 0 crashed with X86 Thread State (64-bit):
rax: 0x0000000000000000 rbx: 0x0000600000c4ef18 rcx: 0x00006000000af728 rdx: 0x00006000000af668
rdi: 0x00007fc167846808 rsi: 0x000000000000000d rbp: 0x00007ffee5d4b300 rsp: 0x00007ffee5d4b2a0
r8: 0x0000000000000023 r9: 0x0000000000000009 r10: 0x00006000001bc708 r11: 0x00007fc168b99688
r12: 0x0000000109fad828 r13: 0x0000000000000000 r14: 0x0000604000c64088 r15: 0x0000000109fcad58
rip: 0x0000000109f510f7 rfl: 0x0000000000010206 cr2: 0x0000000000000078

Logical CPU: 0
Error Code: 0x00000004
Trap Number: 14


Binary Images:
0x109eb3000 - 0x109fb7ff3 +org.rephial.angband (4.2.0-dirty - ???) <C20664F2-2839-3CA4-8885-8C50C3895837> /Applications/Angband.app/Contents/MacOS/angband

External Modification Summary:
Calls made by other processes targeting this process:
task_for_pid: 1657
thread_create: 0
thread_set_state: 0
Calls made by this process:
task_for_pid: 0
thread_create: 0
thread_set_state: 0
Calls made by all processes on this machine:
task_for_pid: 1582519
thread_create: 0
thread_set_state: 0

VM Region Summary:
ReadOnly portion of Libraries: Total=425.7M resident=0K(0%) swapped_out_or_unallocated=425.7M(100%)
Writable regions: Total=173.0M written=0K(0%) resident=0K(0%) swapped_out=0K(0%) unallocated=173.0M(100%)

VIRTUAL REGION
REGION TYPE SIZE COUNT (non-coalesced)
=========== ======= =======
Accelerate framework 128K 2
Activity Tracing 256K 2
CG backing stores 9388K 9
CG image 192K 23
CoreAnimation 140K 26
CoreGraphics 8K 2
CoreImage 212K 48
CoreUI image data 2392K 26
CoreUI image file 216K 6
Foundation 28K 3
Image IO 64K 2
Kernel Alloc Once 8K 2
MALLOC 150.2M 65
MALLOC guard page 48K 12
Memory Tag 242 12K 2
Memory Tag 251 80K 4
OpenCL 16K 3
STACK GUARD 56.0M 6
Stack 10.0M 8
VM_ALLOCATE 276K 26
__DATA 34.9M 330
__FONT_DATA 4K 2
__LINKEDIT 195.1M 14
__TEXT 230.6M 330
__UNICODE 560K 2
mapped file 49.7M 43
shared memory 656K 13
=========== ======= =======
TOTAL 740.9M 984

Model: iMac10,1, BootROM 215.0.0.0.0, 2 processors, Intel Core 2 Duo, 3.06 GHz, 12 GB, SMC 1.53f13
Graphics: ATI Radeon HD 4670, ATI Radeon HD 4670, PCIe
Memory Module: BANK 0/DIMM0, 4 GB, DDR3, 1067 MHz, 0x859B, 0x435434473353313036374D2E4D3136464B44
Memory Module: BANK 1/DIMM0, 4 GB, DDR3, 1067 MHz, 0x859B, 0x435434473353313036374D2E4D3136464D52
Memory Module: BANK 0/DIMM1, 2 GB, DDR3, 1067 MHz, 0x80CE, 0x4D34373142353637334548312D4346382020
Memory Module: BANK 1/DIMM1, 2 GB, DDR3, 1067 MHz, 0x80CE, 0x4D34373142353637334548312D4346382020
AirPort: spairport_wireless_card_type_airport_extreme (0x168C, 0x8F), Atheros 9280: 4.0.74.0-P2P
Bluetooth: Version 6.0.7f16, 3 services, 27 devices, 1 incoming serial ports
Network Service: AirPort, AirPort, en1
Serial ATA Device: Hitachi HDE721010SLA330, 1 TB
Serial ATA Device: PIONEER DVD-RW DVRTS09
USB Device: USB 2.0 Bus
USB Device: Built-in iSight
USB Device: USB 2.0 Bus
USB Device: Internal Memory Card Reader
USB Device: easystore 25FC
USB Device: USB Bus
USB Device: USB Trackball
USB Device: BRCM2046 Hub
USB Device: Bluetooth USB Host Controller
USB Device: USB Bus
USB Device: IR Receiver
Thunderbolt Bus:

[Nick]

Originally Posted by lonadar

I don't know if this is the proper form for this specific type of post, but twice under 4.2 I've had my application just up and die. I didn't catch the crash report from the first one but I have for this, so here it is in all it's glory. If posts of this length belong elsewhere, I apologize:

Reporting like this here is great.

I'm pretty sure this is the problem with the block fall trap, which basically always crashes the game when it is triggered. When you opened the game again, my guess is that there was a wall where you had just hit a trap.

The bug is fixed in development, but thanks for reporting it anyway.