Opened 7 years ago

Closed 7 years ago

#8870 closed bug (fixed)

Exiting Quake3 causes "read fault" KDL every time.

Reported by: jstressman Owned by: anevilyak
Priority: critical Milestone: R1/alpha4
Component: Network & Internet/IPv6 Version: R1/Development
Keywords: Cc:
Blocked By: Blocking:
Has a Patch: no Platform: All

Description

gcc2h hrev44507 in virtualbox.

I was finishing up updating the ioquake3 bep/patch and testing the build and am getting a KDL on exit each time.

I tested this on a slightly older revision (hrev44483 I believe) on bare metal and got no such KDLs on exit.

This is a basically clean install from today. Fresh Haiku install, installed ports, installed SDL 1.2.15 from ports, then installed my ioquake3 port and tested it.

I'm attaching 2 images of the KDLs I got.

Attachments (2)

q3exitkdl1.png (32.0 KB) - added by jstressman 7 years ago.
q3exitkdl2.png (31.9 KB) - added by jstressman 7 years ago.

Download all attachments as: .zip

Change History (10)

Changed 7 years ago by jstressman

Attachment: q3exitkdl1.png added

Changed 7 years ago by jstressman

Attachment: q3exitkdl2.png added

comment:1 Changed 7 years ago by anevilyak

Priority: normalhigh

Is the ioquake3 port available somewhere at this point?

comment:2 Changed 7 years ago by jstressman

bep and patch here: http://ports.haiku-files.org/ticket/378

They're not in the official Ports repo yet... but you can download the bep and patch, put them in the right place, and install just fine that way.

Screenshots and more info: http://haikudou.blogspot.com/2012/08/ioquake3-update-for-haiku.html

comment:3 Changed 7 years ago by anevilyak

I'm unable to duplicate this crash here ; does it only happen for you in vbox, or does the latest on bare metal also panic? There aren't any revisions in the range you listed that should theoretically have any bearing on team exit cleanup.

comment:4 Changed 7 years ago by jstressman

I just tested in both virtualbox and on bare metal with hrev44524 gcc2h and duplicated the crash on both.

It only crashes if I actually start playing the game (actually start a single player game and load a level) and then exit.

I can otherwise start the game, switch resolutions, and exit the game without crashing. But if I actually start playing the game and then exit it crashes to KDL every time.

comment:5 Changed 7 years ago by axeld

Milestone: R1R1/alpha4
Priority: highcritical

comment:6 in reply to:  4 Changed 7 years ago by anevilyak

Replying to jstressman:

It only crashes if I actually start playing the game (actually start a single player game and load a level) and then exit.

That explains it, I only started it and then exited again from the main menu. Will try to look into it some more in the next few days if no one beats me to it.

comment:7 Changed 7 years ago by anevilyak

Component: System/KernelNetwork & Internet/IPv6
Owner: changed from axeld to anevilyak
Status: newin-progress

The culprit is the IPv6 network add-on, that explains why it only shows up after starting the game, since that's what causes a listening socket + connection to be set up. Digging further...

comment:8 Changed 7 years ago by anevilyak

Resolution: fixed
Status: in-progressclosed

Fixed in hrev44558.

Note: See TracTickets for help on using tickets.