Reminder: Internet Explorer 6 or below are NOT supported.
Recent Comments
Random Image
Login Main Menu
Forum Chat-
Join the Freelancer Community Discord Server by Clicking Here!
Who's Online DonationsMonthly costs: -30€
Income (ads): +5€
Donations (last month): +5€
Income (ads): +5€
Donations (last month): +5€
Current balance: -60€
(last updated 10/2020)
Please make a donation if you want to help keeping The-Starport online:
Links
|
Advertisement|
There are currently 33 users playing Freelancer on
42 servers. | January. 28, 2021 |
The Starport Forum Index
>
The Shipyard
>
Speciality Modding
>
FLHook Development
>
Common.dll 0x0635C376 crash
Browsing this Thread:
1 Anonymous Users
Common.dll 0x0635C376 crash |
||||
|---|---|---|---|---|
|
Starport Admin
 
Joined:
2009/2/21 21:42 Group:
Webmasters Registered Users
Posts:
3520
 |
So this is a new one, I'm getting a seemingly random crash at 0x0635C376 in Common.dll. I have no information about when or why it'd happen and it's rare enough to be hard to track down. I'm also getting memory leaks (to the extent of having the server get killed by DSPM for high memory usage), so perhaps the two are related.
Has anyone run in that particular crash? I couldn't find anything about it with a cursory search.
Posted on: 2016/6/16 18:58
|
|||
|
"Cynicism is not realistic and tough. It's unrealistic and kind of cowardly because it means you don't have to try." -Peggy Noonan |
||||
|
||||
Re: Common.dll 0x0635C376 crash |
||||
|---|---|---|---|---|
|
Home away from home
 
Joined:
2009/8/16 2:58 From Qld, Aus.
Group:
Registered Users FLServer Admins Trusted Speciality Developers Senior Members
Posts:
1959
|
As you've probably noticed, that code is a copy loop
p[i] = p[i+1] and it's p[i+1] that is failing (or maybe just p). The data points to three signed ints (used as multipliers) and two table offsets (into powers of two), used at 635D360, eventually traced back to PhySys::FindRayCollisions. Don't know if that's any help, though.
Posted on: 2016/6/18 3:03
|
|||
|
||||
Re: Common.dll 0x0635C376 crash |
||||
|---|---|---|---|---|
|
Starport Admin
Joined:
2009/2/21 21:42 Group:
Webmasters Registered Users
Posts:
3520
|
It's the stack trace I couldn't manage to get properly. I'll have to think about what could cause ray collision errors...
Posted on: 2016/6/18 3:48
|
|||
|
"Cynicism is not realistic and tough. It's unrealistic and kind of cowardly because it means you don't have to try." -Peggy Noonan |
||||
|
||||
Re: Common.dll 0x0635C376 crash |
||||
|---|---|---|---|---|
|
Home away from home
Joined:
2009/8/16 2:58 From Qld, Aus.
Group:
Registered Users FLServer Admins Trusted Speciality Developers Senior Members
Posts:
1959
|
Actually, that might be misleading, as that's where the data itself is used, not where the crash is happening. Reloading a system (
s . using Console in SP) traced that eventually back to PhySys::UnMakePhysicalR from CObject::unmake_physical (and a couple more), and then to PhySys::PhyCollisionStateManager::enable_collisions, which is just PhySys::SetCollisionState. Well, maybe it is something to do with collisions, then.
Posted on: 2016/6/18 4:13
|
|||
|
||||
Re: Common.dll 0x0635C376 crash |
||||
|---|---|---|---|---|
|
Starport Admin
Joined:
2009/2/21 21:42 Group:
Webmasters Registered Users
Posts:
3520
|
The thing that surprises me is that this is a server crash, but I can't think off the top of my head what collisions the server has to deal with. NPCs ignore all collisions so that shouldn't be it. Players send their own collision events to the server. It'd have to be missiles or beams somehow using the collision infrastructure, I guess?
Posted on: 2016/6/18 14:20
|
|||
|
"Cynicism is not realistic and tough. It's unrealistic and kind of cowardly because it means you don't have to try." -Peggy Noonan |
||||
|
||||
Re: Common.dll 0x0635C376 crash |
||||
|---|---|---|---|---|
|
Home away from home
Joined:
2009/8/16 2:58 From Qld, Aus.
Group:
Registered Users FLServer Admins Trusted Speciality Developers Senior Members
Posts:
1959
|
The server calls
PhySys::Update, which eventually calls the function in question. Prior to the update, there's calls to CBeam::move; I also traced a usage of the pointer (at edx+0x1C) back to PhySys::BeamR, coming across an excessive amount of children warning and there's also Unknown anim_technique in PhySys::_BeamR_Children(). Still don't know if it helps.
Posted on: 2016/6/20 3:21
|
|||
|
||||
Re: Common.dll 0x0635C376 crash |
||||
|---|---|---|---|---|
|
Starport Admin
Joined:
2009/2/21 21:42 Group:
Webmasters Registered Users
Posts:
3520
|
Sounds like it'd be related to beams somehow then. I'll keep that in mind, thanks a lot man.
Posted on: 2016/6/20 4:08
|
|||
|
"Cynicism is not realistic and tough. It's unrealistic and kind of cowardly because it means you don't have to try." -Peggy Noonan |
||||
|
||||