Page 1 of 1
| Freezing 15/12/2014 at 23:32 #66714 | |
Muzer
718 posts |
So, this could just be a wine thing (albeit not one I've encountered before). But twice now, I've had Wimbledon freeze on me. I've posted it here because I have only been playing Wimbledon recently, so it could equally likely be just Wimbledon or a loader thing. The first time the freeze was literally immediately after I saved the game (I had a funny feeling something weird was going to happen which is what caused me to save in the first place, but unless I was subconsciously noticing something unusual I haven't consciously noticed yet, I expect this is a coincidence - I highly doubt I have any form of psychic bond with SimSig :p). The second time, it was right after unpausing just after having pressed the lower button on Malden level crossing (quite far from the last save  - I still want an option to autosave more frequently than once every ten minutes!). I don't have any other clues, there haven't been any other errors, and I'm running the latest loader (4.3). When this happened last time it was in the first version of Wimbledon; I upgraded to 1.1 before the second freeze happened.The freeze is a total freeze, with no CPU usage (so not an infinite loop, presumably), and not even screen redraws occurring (ie if you switch to another window and back, you no longer see any of the sim or menus). I've tried randomly mashing keys on the keyboard and it doesn't appear to help. (I've left it running in case there's some coredump technique I can perform that would be useful - I'm not particularly knowledgeable about Windows debugging) As I said, I've never encountered this before until recently, when I've encountered it twice. I don't recall having changed anything on my system recently that might affect this. It COULD be a wine thing but I find it odd that it's not something I've encountered before, given how much I've played SimSig Last edited: 15/12/2014 at 23:33 by Muzer Log in to reply |
| Freezing 15/12/2014 at 23:48 #66715 | |
|
peterb
452 posts |
Yep happened to me many times on many sims http://www.SimSig.co.uk/index.php?option=com_kunena&view=topic&catid=14&id=38595&Itemid=0 Log in to reply |
| Freezing 15/12/2014 at 23:55 #66716 | |
|
Muzer
718 posts |
Hmm, I remember seeing that thread. My memory is clearly failing 
Log in to reply |
| Freezing 21/12/2014 at 00:53 #66883 | |
|
Muzer
718 posts |
The freezing IS happening in other sims, it's not too irregular, and it tends to be something to do with pausing and scrolling, which makes me think it's more likely to be a wine issue. I'll try updating wine to the latest revision, that's always a good thing to try...
Log in to reply |
| Freezing 21/12/2014 at 01:31 #66884 | |
|
Muzer
718 posts |
Managed to get a backtrace out of it (I've not updated wine yet, so that might still fix it yet) - sorry, I don't have debug symbols installed, so I'm not sure how useful this will be to you. You do get one address actually from your binary, though! This particular crash happened while scrolling and trying to answer a telephone call by hitting "a", nothing to do with pausing this time. Wine-dbg>btAttached is a core dump file generated from gdb, again not sure how useful this is for you. EDIT: I think the board rejected the attachment, so the core file uploaded http://tim32.org/~muzer/core.7317.bz2 Last edited: 21/12/2014 at 01:33 by Muzer Log in to reply |
| Freezing 21/12/2014 at 05:11 #66888 | |
|
Muzer
718 posts |
Either updating wine has fixed it, or I've been particularly lucky in not being able to trigger the bug. It's strange, since I don't remember updating wine between the bug never happening and the bug routinely happening.
Log in to reply |
| Freezing 24/12/2014 at 16:14 #66984 | |
|
Southernrover
46 posts |
Hi all, I am having a problem with Wimbledon that I downloaded yesterday. I played it okay for a number of hours off and on during the evening but when openeing it today i'm finding it freezes straight after openeing. I get the attached screenshot which when cancelled goes to the milky white state you see in the second screenshot. Both Loader and Sim are uptodate as are all my drivers and Im running Vista. No problems with any other sim. The only thing I havent tried yet is starting the game again, which I was a bit loath to do if a solution exists. Anyone have any ideas?? Merry Xmas, Rick  
Post has attachments. Log in to view them. Log in to reply |
| Freezing 24/12/2014 at 20:27 #66988 | |
GeoffM
6377 posts |
" said:Managed to get a backtrace out of it (I've not updated wine yet, so that might still fix it yet) - sorry, I don't have debug symbols installed, so I'm not sure how useful this will be to you. You do get one address actually from your binary, though!Strange but SimSig doesn't even get a mention until line 50. That crash is happening deep within the O/S or Delphi libraries. I'm not saying SimSig doesn't provoke it but it's hard to look at a cause when it only happens on a few machines, presumably Windows as well as Linux. SimSig Boss Last edited: 24/12/2014 at 20:27 by GeoffM Log in to reply |
| Freezing 24/12/2014 at 22:03 #66989 | |
|
Danny252
1461 posts |
The call to __kernel_vsyscall+0x10 seems to be a function to pass a call to the Linux Kernel, implying the actual problem occurs even further down! It also seems to be a very common place for WINE call traces to show the crash occurring, so it doesn't seem terribly helpful. Even less helpfully, 0x0055aa00 (the previous instruction before 0x0055aa05) in Simsig is located almost at the end of the binary, and is is a call to Vcl.Forms.TApplication.Run(), for a form with the title "Simsig Loader". Going by the Delphi documentation, Run() starts when your application does and only returns when the application ends - that suggests that the call is a bit of a red herring to me, and doesn't really show what Simsig was up to at the time! Last edited: 24/12/2014 at 22:28 by Danny252 Log in to reply |
| Freezing 24/12/2014 at 22:14 #66990 | |
|
Airvan00
129 posts |
" said:Hi all,Not a solution but a workaround. You will notice that the error message mentions trains 2H10 and 2J10. Make both trains Non ARS. Then continue. After a few minutes you can return them to an ARS state. It works for me, let us know how you got on. My theory is that one of the trains has previously been taken off it's planned route and the ARS gets knotted. Merry Xmas Evan Log in to reply |
| Freezing 27/12/2014 at 17:24 #67115 | |
|
clive
2789 posts |
" said:The first problem is a known one in the core code. I can't explain the freeze. Log in to reply The following user said thank you: Southernrover |
| Freezing 27/12/2014 at 17:35 #67117 | |
|
clive
2789 posts |
" said:The call to __kernel_vsyscall+0x10 seems to be a function to pass a call to the Linux Kernel, implying the actual problem occurs even further down! It also seems to be a very common place for WINE call traces to show the crash occurring, so it doesn't seem terribly helpful.It looks to me that the loader is dispatching a Windows message to Windows (see line 48) and so this isn't a core code problem at all. I'm particularly interested in line 1, which is within the "select" system call. That's a standard part of Unix: select waits until either a message arrives from any of a range of sources (devices, pipes, or network links) or there's an interrupt. The whole thing feels like a Wine problem. Log in to reply |
| Freezing 27/12/2014 at 17:53 #67120 | |
|
Finger
220 posts |
" said:Managed to get a backtrace out of it (I've not updated wine yet, so that might still fix it yet) - sorry, I don't have debug symbols installed, so I'm not sure how useful this will be to you. You do get one address actually from your binary, though!The backtrace you provided is not relevant to any crashes you might have experienced - basically the crash shows Wine calling the kernel to pause for a while (which, most likely didn't crash). The crash itself must have happened in another thread and at another place. Core files are not terribly useful without the binaries that were loaded at the time - best with debugging symbols at least showing where functions start. Log in to reply |
| Freezing 27/12/2014 at 18:24 #67125 | |
|
Southernrover
46 posts |
" said:Hi all,Have now restarted the game which is now running okay so I suspect a corrupted gamesave. Rick Log in to reply |
| Freezing 27/12/2014 at 23:26 #67134 | |
|
Muzer
718 posts |
Indeed, as I mentioned previously in this thread, contrary to my earlier expectations, updating wine did indeed fix it, so I suspect it was a wine regression that I happened to unhappily stumble across. Still odd since I don't remember having updated wine recently. Maybe it's a sign that I haven't been playing SimSig enough. @Finger: It was a freeze, not a crash. Last edited: 27/12/2014 at 23:27 by Muzer Log in to reply |
| Freezing 28/12/2014 at 00:30 #67137 | |
BarryM
2158 posts |
" said:It is not a "freeze", it is "Not Responding". Too hot for a "freeze" especially in Aus. lol! Barry Barry, Sydney, New South Wales, Australia Log in to reply |