Context
I was just updating mastercomfig from the github repo yesterday, so I tried to load up TF2 to test it out. However when I got to the main menu, every time I tried to load up a map/server TF2 would crash, and every row in the player column was always "1⁄1" in the server browser. I haven't fully tried hardcore searching it up, but this is not a typical error I have heard of/seen before. I posted this issue in the mastercomfig thread initially because I thought this was an issue with mastercomfig, but stock TF2 still crashed even when I cleaned it up, so that ruled out mastercomfig, thus is why I made this thread to solve this issue in a more relevant forum. Today I come back after exams and now TF2 can't even get to the main menu.
Debugging
I logged TF2 both through -condebug -dev and the GDB debugger. Looking through the logs, I noticed this strange error that shows just before I run into the segmentation fault error (shown by GDB) that's crashing the game:
Unknown command ""
or with the unicode converted to C-style escapes:
Unknown command "\xEF"
That unicode character converts to an 'ï' character. I have never used this character in any of my script (or CFG) files and while I do use this character in my captions, that has never caused any particular issue before.
Regular console log
The GDB log
It's important to note that this crash occurs when running the game through hl2.exe itself (meaning the crash occurs regardless if I launch TF2 through steam or Playnite). However the crash occurs during launch when using Playnite, while Steam manages to get to the main menu, but TF2 still crashes when entering a server/map.
Hypothesis
I have a feeling there's some sort of internal corruption going on that I'm not seeing. I checked the stock VPKs TF2 comes with and none of them are corrupted (confirmed by open files through GCFScape and they are intact). I am also running stock TF2, so this might be an issue with the game itself.
I haven't checked the video config yet, but that might give me clues.
Why are you posting this here?
So that future players who have this issue can get this issue solved much faster, without going through this painful process.
EDIT: TF2 running in -insecure mode means nothing in this situation, so I removed unneccessary information relating to it.
[b][h]Context[/h][/b]
I was just updating mastercomfig from the github repo yesterday, so I tried to load up TF2 to test it out. However when I got to the main menu, every time I tried to load up a map/server TF2 would crash, and every row in the player column was always "1⁄1" in the server browser. I haven't fully tried hardcore searching it up, but this is [i]not[/i] a typical error I have heard of/seen before. I posted this issue in the mastercomfig thread initially because I thought this was an issue with mastercomfig, but stock TF2 still crashed even when I [url=https://docs.mastercomfig.com/en/latest/setup/clean_up/]cleaned it up[/url], so that ruled out mastercomfig, thus is why I made this thread to solve this issue in a more relevant forum. Today I come back after exams and now TF2 can't even get to the main menu.
[b][h]Debugging[/h][/b]
I logged TF2 both through -condebug -dev and the [url=https://www.gnu.org/software/gdb/]GDB[/url] debugger. Looking through the logs, I noticed this strange error that shows just before I run into the segmentation fault error (shown by GDB) that's crashing the game:
[code]Unknown command ""[/code]
or with the unicode converted to C-style escapes:
[code]Unknown command "\xEF"[/code]
That unicode character converts to an 'ï' character. I have [i]never[/i] used this character in any of my script (or CFG) files and while I do use this character in my captions, that has never caused any particular issue before.
[url=https://pastebin.com/4mtftdyn]Regular console log[/url]
[url=https://pastebin.com/DSnaBH3U]The GDB log[/url]
It's important to note that this crash occurs when running the game through hl2.exe itself (meaning the crash occurs regardless if I launch TF2 through steam or [url=https://playnite.link/]Playnite[/url]). However the crash occurs during launch when using Playnite, while Steam manages to get to the main menu, but TF2 still crashes when entering a server/map.
[b][h]Hypothesis[/h][/b]
I have a feeling there's some sort of internal corruption going on that I'm not seeing. I checked the stock VPKs TF2 comes with and none of them are corrupted (confirmed by open files through [url=https://developer.valvesoftware.com/wiki/GCFScape]GCFScape[/url] and they are intact). I am also running stock TF2, so this might be an issue with the game itself.
I haven't checked the video config yet, but that might give me clues.
[b][h]Why are you posting this here?[/h][/b]
So that future players who have this issue can get this issue solved much faster, without going through this painful process.
EDIT: TF2 running in -insecure mode means nothing in this situation, so I removed unneccessary information relating to it.
vaniwhat
TL;DR Everytime I load up a server the game crashes, and the player column in the server browser only shows 1⁄1, which is not normal behavior.
[quote=vani]what[/quote]
TL;DR Everytime I load up a server the game crashes, and the player column in the server browser only shows 1⁄1, which is not normal behavior.
mastercoms been reeeeal quiet since new AimIsADick post dropped
mastercoms been reeeeal quiet since new AimIsADick post dropped
mans typed a hypothesis and everything
mans typed a hypothesis and everything
https://www.teamfortress.tv/59525/cant-join-any-servers-max-players-1
That thread has like 1/3 of the words and the solution.
Ariehttps://www.teamfortress.tv/59525/cant-join-any-servers-max-players-1
That thread has like 1/3 of the words and the solution.
Well hey it's not easy to search up the solution. Sometimes it's obscured in very specific permutations of letters out of thousands of possibilities, and I either give a detailed explanation, or a shitty boomer one. Anyway I forgot about Steam Betas and opted out. Now I don't get this issue.
Likewise I think there's some corruption glitch in the beta steam client.
[quote=Arie]https://www.teamfortress.tv/59525/cant-join-any-servers-max-players-1
That thread has like 1/3 of the words and the solution.[/quote]
Well hey it's not easy to search up the solution. Sometimes it's obscured in very specific permutations of letters out of thousands of possibilities, and I either give a detailed explanation, or a shitty boomer one. Anyway I forgot about Steam Betas and opted out. Now I don't get this issue.
Likewise I think there's some corruption glitch in the beta steam client.
i think more people will probably find it by googling max players 1 than googling "bug that aimisadick hasnt seen/heard before"
i think more people will probably find it by googling max players 1 than googling "bug that aimisadick hasnt seen/heard before"
BumFreezei think more people will probably find it by googling max players 1 than googling "bug that aimisadick hasnt seen/heard before"
Well hey I was panicking and couldn't think that well, and my wisdown level is pretty low (relative of course; there's no reliable way to measure intelligence or wisdom).
[quote=BumFreeze]i think more people will probably find it by googling max players 1 than googling "bug that aimisadick hasnt seen/heard before"[/quote]
Well hey I was panicking and couldn't think that well, and my wisdown level is pretty low (relative of course; there's no reliable way to measure intelligence or wisdom).
[img]https://i.imgur.com/ewPZkLy.jpeg[/img]
this guy is the best tftv shitposter currently active and nobody else even comes close
this guy is the best tftv shitposter currently active and nobody else even comes close
i cant believe i fell for the troll for so long this is insane keep it up dog +1 from me
i cant believe i fell for the troll for so long this is insane keep it up dog +1 from me
hpqoeui cant believe i fell for the troll for so long this is insane keep it up dog +1 from me
This isn't a TROLL!
[quote=hpqoeu]i cant believe i fell for the troll for so long this is insane keep it up dog +1 from me[/quote]
This [b]isn't[/b] a TROLL!
This reads like the end of an English essay in high school, when you’ve realised you haven’t hit the word count.
This reads like the end of an English essay in high school, when you’ve realised you haven’t hit the word count.
grade A trolling, love to see it. keep it up aim welcome to tftv
grade A trolling, love to see it. keep it up aim welcome to tftv
Hi aim is a dick. I looked at your 'GDB log' and feel the need to let you know that that is not debugger output from GDB at all. Only the [New Thread xxxx.xxxxx] is coming from GDB. TF2 outputs the rest of that stuff to stdout regardless, try running it without GDB and you will see much the same output.
Hi aim is a dick. I looked at your 'GDB log' and feel the need to let you know that that is not debugger output from GDB at all. Only the [New Thread xxxx.xxxxx] is coming from GDB. TF2 outputs the rest of that stuff to stdout regardless, try running it without GDB and you will see much the same output.
BumFreezeaimisadick hasnt seen/heard
god i wish
[quote=BumFreeze]aimisadick hasnt seen/heard[/quote]
god i wish
I'm not trolling.
turbochad69Hi aim is a dick. I looked at your 'GDB log' and feel the need to let you know that that is not debugger output from GDB at all. Only the [New Thread xxxx.xxxxx] is coming from GDB. TF2 outputs the rest of that stuff to stdout regardless, try running it without GDB and you will see much the same output.
Right and how do you exactly get the output from stdout without a debugger? I tried launching TF2 from the regular command line and I got nothing. How exactly do you think I got the segmentation fault error? They doesn't show up at all in source console logs; only debuggers can show those fatal errors.
I'm not trolling.
[quote=turbochad69]Hi aim is a dick. I looked at your 'GDB log' and feel the need to let you know that that is not debugger output from GDB at all. Only the [New Thread xxxx.xxxxx] is coming from GDB. TF2 outputs the rest of that stuff to stdout regardless, try running it without GDB and you will see much the same output.[/quote]
Right and how do you exactly get the output from stdout without a debugger? I tried launching TF2 from the regular command line and I got nothing. How exactly do you think I got the segmentation fault error? They doesn't show up at all in source console logs; only debuggers can show those fatal errors.
That it segfaulted is pretty useless information, it technically narrows it down a bit, but you might as well anyway be saying it crashed. Seeing stdout is not what a debugger is used for. You can do that in other ways.
What a debugger is actually used for is breaking into the code, viewing variables and the stack, and in some cases, rewind in the case of time travel debugging with something like rr or WinDbg. However, as was said before to you, since you do not have debug information, it will be very hard to debug the program without very good experience with programming and especially assembly.
Also, I think in these cases, you will find Valgrind more helpful than simply using gdb.
That it segfaulted is pretty useless information, it technically narrows it down a bit, but you might as well anyway be saying it crashed. Seeing stdout is not what a debugger is used for. You can do that in other ways.
What a debugger is actually used for is breaking into the code, viewing variables and the stack, and in some cases, rewind in the case of time travel debugging with something like rr or WinDbg. However, as was said before to you, since you do not have debug information, it will be very hard to debug the program without very good experience with programming and especially assembly.
Also, I think in these cases, you will find Valgrind more helpful than simply using gdb.
Sry late reply.
mastercomsThat it segfaulted is pretty useless information, it technically narrows it down a bit, but you might as well anyway be saying it crashed.
Yeah you're right I eventually realized that sometime before you said so, since the segfault error appeared so commonly.
mastercomsSeeing stdout is not what a debugger is used for. You can do that in other ways.
I realize that now. I just thought that GDB was the only way to get stdout, since stdout wouldn't show on the (Windows) command line when I ran TF2 without start.
mastercomsWhat a debugger is actually used for is breaking into the code, viewing variables and the stack, and in some cases, rewind in the case of time travel debugging with something like rr or WinDbg. However, as was said before to you, since you do not have debug information, it will be very hard to debug the program without very good experience with programming and especially assembly.
I realize that already.
mastercomsAlso, I think in these cases, you will find Valgrind more helpful than simply using gdb.
How so? I just picked up valgrind and it feels confusing, but I'm sure I'll get the hang of it eventually.
Sry late reply.
[quote=mastercoms]That it segfaulted is pretty useless information, it technically narrows it down a bit, but you might as well anyway be saying it crashed.[/quote]
Yeah you're right I eventually realized that sometime before you said so, since the segfault error appeared so commonly.
[quote=mastercoms]Seeing stdout is not what a debugger is used for. You can do that in other ways.[/quote]
I realize that now. I just thought that GDB was the only way to get stdout, since stdout wouldn't show on the (Windows) command line when I ran TF2 without start.
[quote=mastercoms]What a debugger is actually used for is breaking into the code, viewing variables and the stack, and in some cases, rewind in the case of time travel debugging with something like rr or WinDbg. However, as was said before to you, since you do not have debug information, it will be very hard to debug the program without very good experience with programming and especially assembly.[/quote]
I realize that already.
[quote=mastercoms]Also, I think in these cases, you will find Valgrind more helpful than simply using gdb.[/quote]
How so? I just picked up valgrind and it feels confusing, but I'm sure I'll get the hang of it eventually.