ZeroBrane studio crashes when using win7 x64 #164
Comments
ghost
assigned 
|
@thebothead, sorry to hear this is happening and thank you for reporting. I don't have access to win7 64bit machine and unfortunately can't do the analysis on a 32bit machine (I found some instructions here). Maybe we can try to solve the issue in a different way. First of all, what version of ZBS are you running? What are you trying to do when the app crashes? Some of the earlier versions could crash when auto-complete suggestions were generated or when the IDE was closed while the debugging was still in progress. Both of those issues have been fixed and I haven't seen (or got any reports) about crashes with v0.37 or the current master branch. It may also help if you could generate the stack trace I can read based on the dump file. I'm working on getting access to a win7 64bit machine, but it may take few days. Thanks. |
|
@pkulchenko I am running ZeroBrane Studio (0.37; MobDebug 0.526). The app has been crashing intermittently when I've been typing in the editor (I think it might have actually been an auto-complete or intelli-sense scenario in some of the cases, but I can't remember exactly:/), I will take better note of the repro steps if it happens again, I was hoping the dump file would have been enough information. I am not sure how else I can generate the stack trace for an application that has crashed other than creating a dump file for the process that has encountered a fatal error such as this. I think so long as you have the matching sources, PDB's, and binaries you should be able to step right into the source at that line of code that encountered the error (giving you the stack trace) right? You could probably even pull open the dump file in WinDBG to get the exception information. If it happens again I'll let you know if I have more information. If there is any logging or any other data that the app generates itself that you would like me to share let me know and I will. |
|
Accidently closed it, re-opened it. |
|
Thank you for the details; I was thinking maybe you can generate the stack trace based on the dump file using WinDBG (as I need to have 64bit WinDBG and can't run it on 32bit system I have), but even that may not be possible as the executable is compiled using mingw, which doesn't generate PDB file WinDBG can use. I guess I'll probably need to try to reproduce it myself when I get access to 64 bit win7 instance. Do you have anything in user.lua that changes default configuration? Another option would be to try to reproduce the same issue and use run-time debugger like DrMingw. You may not get a complete list of symbols (as I do have debug information stripped from the executable/dlls), but if we can't identify the issue using the debugger and I can't reproduce it, I can prepare a version with debug information to see what may be going on. There is some interesting information in this SO question, but using DrMingw may be the easiest option. I'll also try to extend the code to do its own crash analysis, but this may take even longer... Thanks for all your help. |
|
Ok, thanks! I have to step away from my dev station for the day but will try some of the things you mentioned as well as try and see if I can pull anything useful out of the dump file. Will keep you posted. |
|
Sounds good; this will be very helpful. |
|
So I loaded up the crash dump in WinDBG and ran the exception analysis command and here's what I got so far... Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64 Loading Dump File [...\zbstudio.DMP] Symbol search path is: SRV_C:\sym_http://msdl.microsoft.com/download/symbols
*** ERROR: Module load completed but symbols could not be loaded for zbstudio.exe FAULTING_IP: EXCEPTION_RECORD: ffffffffffffffff -- (.exr 0xffffffffffffffff) FAULTING_THREAD: 0000000000001d1c DEFAULT_BUCKET_ID: STATUS_BREAKPOINT PROCESS_NAME: zbstudio.exe OVERLAPPED_MODULE: Address regions for 'propsys' and 'swi_ifslsp' overlap ERROR_CODE: (NTSTATUS) 0x80000003 - {EXCEPTION} Breakpoint A breakpoint has been reached. EXCEPTION_CODE: (HRESULT) 0x80000003 (2147483651) - One or more arguments are invalid MOD_LIST: NTGLOBALFLAG: 0 APPLICATION_VERIFIER_FLAGS: 0 PRIMARY_PROBLEM_CLASS: STATUS_BREAKPOINT BUGCHECK_STR: APPLICATION_FAULT_STATUS_BREAKPOINT LAST_CONTROL_TRANSFER: from 00000000745c283e to 00000000745c2e09 STACK_TEXT: STACK_COMMAND: ~0s; .ecxr ; kb FOLLOWUP_IP: SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: wow64cpu!CpupSyscallStub+9 FOLLOWUP_NAME: MachineOwner MODULE_NAME: wow64cpu IMAGE_NAME: wow64cpu.dll DEBUG_FLR_IMAGE_TIMESTAMP: 50b8488e FAILURE_BUCKET_ID: STATUS_BREAKPOINT_80000003_wow64cpu.dll!CpupSyscallStub BUCKET_ID: X64_APPLICATION_FAULT_STATUS_BREAKPOINT_wow64cpu!CpupSyscallStub+9 WATSON_STAGEONE_URL: http://watson.microsoft.com/StageOne/zbstudio_exe/0_0_0_0/513f5afd/unknown/0_0_0_0/bbbbbbb4/80000003/00000000.htm?Retriage=1 Followup: MachineOwner |
|
@thebothead, thank you for the crash report. It looks a bit strange as it appears that the fault is in wow64cpu module/dll and the error code (0x80000003) indicates that "a hard coded breakpoint or assertion was hit, but this system was booted /NODEBUG." I found several (possibly relevant) references for this error; one of them (back from 2008) suggested running the app with a different set of credentials (unfortunately, there is no information on why exactly this would help). Could you try running ZBS with admin or non-admin credentials? |
|
That's very interesting, nice find! I will make sure to capture a new dump file using ProcDump the next time it happens and post the new dump file. I am currently running the app as an administrator (I set a short-cut to always do that) and installed to the "C:\Program Files (x86)\ZeroBraneStudio". Later tonight when I have a chance to do some work that involves zbstudio I'll keep an eye out for this and be ready to re-capture the dump if I hit the crash again, sorry I didn't get that right the first time:( |
|
@thebothead, please do. I checked with other users who are also running win7/64bit and so far nobody has reported anything similar. Is there something unique to your setup? For example, do you have any settings in cfg/user.lua? I'm trying to gather as much information as possible to reproduce the issue. Thank you. |
|
I have not changed anything myself in those files. I should have mentioned that I am using Marmalade 6.2 with Quick, if that helps at all. |
|
It does help; just to confirm, the crash happens when you edit something or when you debug your Quick application (or start debugging)? |
|
The crash only occurred when I was writing code in the editor, never in a debug session, and I am pretty sure that the crash was when auto-complete/intellisense would kick in (I.e. after typing a semi-colon on the director object). |
|
@thebothead, one last question: ZBS doesn't crash right away, it appears to be "busy" for a second or two and crashes or you need to "kill" it? There was an issue in auto-complete logic that was weeks about 3 weeks ago (#153), but it was after 0.37 was released. You may want to get the most recent version from the master branch and try it to see if it resolves the issue. |
|
Busy for a second or two and them crashes, haven't had to kill it. That issue 153 looks like it is probably the same thing that is going on here. I will grab the latest and use that. I'll re-open this issue if it doesn't resolve the issue, at which point will have an x32 dump to look at too. Thanks for all your help! |
|
Sounds good; closing for now, but please let me know if the issue is (not) resolved in the current master. Thank you! |
|
@pkulchenko I happened to hit this again (note that I haven't pulled the latest verison yet, still the version I mentioned above). This time I used procdump to grab a 32-bit dump file, and ran analyze exception again and got some better looking information (shown below). I also shared the new dump file here (https://docs.google.com/file/d/0B7KLcn-Vx-2VWW16aTBMMlZieG8/edit?usp=sharing) for you, and I think that even without symbols/sources attached you can probably dig deeper into the exception address shown here to get some more information out of it. This time when the crash occurred I was typing in a text file (.txt extension) in ZeroBrane, not even a lua source file. Let me know if there is anything else I can provide here. *** procdump.exe -ma 12488
*** ERROR: Module load completed but symbols could not be loaded for zbstudio.exe FAULTING_IP: EXCEPTION_RECORD: 0028e668 -- (.exr 0x28e668) FAULTING_THREAD: 00002680 DEFAULT_BUCKET_ID: STATUS_BREAKPOINT PROCESS_NAME: zbstudio.exe ERROR_CODE: (NTSTATUS) 0x80000003 - {EXCEPTION} Breakpoint A breakpoint has been reached. EXCEPTION_CODE: (HRESULT) 0x80000003 (2147483651) - One or more arguments are invalid MOD_LIST: NTGLOBALFLAG: 0 APPLICATION_VERIFIER_FLAGS: 0 CONTEXT: 0028e6b8 -- (.cxr 0x28e6b8) READ_ADDRESS: 0c7c0233 FOLLOWUP_IP: FAILED_INSTRUCTION_ADDRESS: ADDITIONAL_DEBUG_TEXT: Followup set based on attribute [Is_ChosenCrashFollowupThread] from Frame:[0] on thread:[PSEUDO_THREAD] LAST_CONTROL_TRANSFER: from 02330b3f to 0c7c0233 PRIMARY_PROBLEM_CLASS: STATUS_BREAKPOINT BUGCHECK_STR: APPLICATION_FAULT_STATUS_BREAKPOINT IP_ON_HEAP: 0c7c0233 IP_IN_FREE_BLOCK: c7c0233 STACK_TEXT: SYMBOL_NAME: wx!ZN12wxEvtHandler15AddPendingEventERK7wxEvent+0 FOLLOWUP_NAME: MachineOwner MODULE_NAME: wx IMAGE_NAME: wx.dll DEBUG_FLR_IMAGE_TIMESTAMP: 5130fe8c STACK_COMMAND: .cxr 000000000028E6B8 ; kb ; dds 28eb1c ; kb FAILURE_BUCKET_ID: STATUS_BREAKPOINT_80000003_wx.dll!ZN12wxEvtHandler15AddPendingEventERK7wxEvent BUCKET_ID: APPLICATION_FAULT_STATUS_BREAKPOINT_BAD_IP_wx!ZN12wxEvtHandler15AddPendingEventERK7wxEvent+0 WATSON_STAGEONE_URL: http://watson.microsoft.com/StageOne/zbstudio_exe/0_0_0_0/513f5afd/unknown/0_0_0_0/bbbbbbb4/80000003/00000000.htm?Retriage=1 Followup: MachineOwner |
|
@thebothead, thank you for the update; this looks very useful! I'm puzzled a bit by the crash report though as it shows calls that I wouldn't expect to see there. For example, it references I'd love for you to use the latest version (just to make sure that it's not the same issue as the one that was fixed already); although auto-complete should not be in effect for |
|
@pkulchenko, that's definitely weird, especially since its a UI component, it would be one thing if it was some utility component that had nothing to do with the UI that something you were using was making a call into:/ I'll grab the latest version and start using that. I noticed there is a zbstudio.exe file in the master branch, can I just grab that or do I need to pull all the sources and build them? |
|
Another way is to download the zip file (from the github project page); this is smaller than the clone (as it doesn't have any history), but doesn't allow you for getting updates easily. In both cases it will use the same .ini configuration, so all your project and window configuration should be preserved. |
|
@thebothead, have you had a chance to try with the most recent version? Still crashes? |
|
@pkulchecko, sorry I haven't tried the latest version yet because my
|
|
@thebothead, you don't need Marmalade license if you don't run/debug the project. It would be great if you could try with the current version typing the fragments that were crashing ZBS for you. Thank you! |
|
@pkulchenko, sure thing. Will try out the latest version later today and
|
|
@pkulchenko, been using the latest for a couple days now (been back on the LUA train) and just got a crash again today. I posted the 32-bit dump here (https://docs.google.com/file/d/0B7KLcn-Vx-2VUzBxOW9oM0xqUWc/edit?usp=sharing). Here is the exception details again. Let me know if you need anything else, or want me to use a special build with some more debug settings turned on. Can probably open this issue since its still happening, rather than working on it in a closed state:) Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64 Loading Dump File [...\zbstudio_130612_174352.dmp] Comment: '
*** ERROR: Module load completed but symbols could not be loaded for zbstudio.exe FAULTING_IP: EXCEPTION_RECORD: 0028e668 -- (.exr 0x28e668) FAULTING_THREAD: 000021ac DEFAULT_BUCKET_ID: STATUS_BREAKPOINT PROCESS_NAME: zbstudio.exe ERROR_CODE: (NTSTATUS) 0x80000003 - {EXCEPTION} Breakpoint A breakpoint has been reached. EXCEPTION_CODE: (HRESULT) 0x80000003 (2147483651) - One or more arguments are invalid MOD_LIST: NTGLOBALFLAG: 0 APPLICATION_VERIFIER_FLAGS: 0 CONTEXT: 0028e6b8 -- (.cxr 0x28e6b8) READ_ADDRESS: 5dac0207 FOLLOWUP_IP: FAILED_INSTRUCTION_ADDRESS: ADDITIONAL_DEBUG_TEXT: Followup set based on attribute [Is_ChosenCrashFollowupThread] from Frame:[0] on thread:[PSEUDO_THREAD] LAST_CONTROL_TRANSFER: from 02270b3f to 5dac0207 PRIMARY_PROBLEM_CLASS: STATUS_BREAKPOINT BUGCHECK_STR: APPLICATION_FAULT_STATUS_BREAKPOINT IP_ON_HEAP: 5dac0207 IP_IN_FREE_BLOCK: 5dac0207 STACK_TEXT: SYMBOL_NAME: wx!ZN12wxEvtHandler15AddPendingEventERK7wxEvent+0 FOLLOWUP_NAME: MachineOwner MODULE_NAME: wx IMAGE_NAME: wx.dll DEBUG_FLR_IMAGE_TIMESTAMP: 5130fe8c STACK_COMMAND: .cxr 000000000028E6B8 ; kb ; dds 28eb1c ; kb FAILURE_BUCKET_ID: STATUS_BREAKPOINT_80000003_wx.dll!ZN12wxEvtHandler15AddPendingEventERK7wxEvent BUCKET_ID: APPLICATION_FAULT_STATUS_BREAKPOINT_BAD_IP_wx!ZN12wxEvtHandler15AddPendingEventERK7wxEvent+0 WATSON_STAGEONE_URL: http://watson.microsoft.com/StageOne/zbstudio_exe/0_0_0_0/513f5afd/unknown/0_0_0_0/bbbbbbb4/80000003/00000000.htm?Retriage=1 Followup: MachineOwner |
|
Finally happened again... and once again when I was typing in a text file. This was the first time since I got the new build and added you debug DLL that I actually wrote in a ".txt" file, and sure enough it happened... I have been coding in the IDE non-stop for the past few weeks with new issues, and as soon as I started working in this text file it crashed. Grabbed a screen shot of the error message, which is practically useless it seems. Also here is the new dump file that I grabbed. Dump file: https://docs.google.com/file/d/0B7KLcn-Vx-2VM01ZTzkycUcxazQ/edit?usp=sharing |
|
@thebothead, thank you for the update! Can you run the exception analysis like you did before? BTW, I offered a bounty for this issue. |
|
@thebothead, I ran the analysis, but the stack trace looks strange; this is the top part: Is it the same thing you see? Thanks! |
|
@pkulchenko, here is the stack trace I get. The timing of the dump I took this time is different than the previous ones. This dump I took when the message box popped up in the screen shot I took, and the previous dumps were taken at the time when Windows pops up its "your app has died" popup where you can choose to debug or close it, which is when you typically want to take the dump. My head wasn't screwed on all the way last night and I forgot to capture the extra dump when windows jumps in and gives you the "your app has died" message... Sorry about that, I wanted to get both for comparison. I will see if I can repro this again and grab both, but hopefully the one I grabbed has some use. STACK_TEXT: |
|
will try to look into this as well, as I've been running into the same problem. @thebothead, do you have a "cfg/user.lua" file for custom settings? if yes That could improve the situation, at least that's what I suspect as it's autocomplete logic which is also active in txt files |
|
@CrazyButcher, I do not have that file at the moment. I will create that file and add that line tonight when I have time to do some LUA work. Can you explain to me what that line is? Thanks. |
|
It disables one part of the autocomplete logic that more or less allows suggestions within any file type, simply based on words already written in the file. Another option would be turning autocomplete off with "autocomplete = false" |
|
@bothead, @CrazyButcher suspected that some of the crashes could be related to handling of dynamic words when they should be turned off by default, but after further investigation it turned out that dynamic words are indeed turned of by default, so it's unlikely that the change will make a difference for you. @CrazyButcher, or do we still suspect that? It would be interesting though to see if setting |
|
I had a crash on my Win7-64 bit machine at work ... could this be the same problem - or a different one? (ZBSv0.38) |
|
@robzed, most likely. Did it happen when you were typing text (probably with auto-complete)? It does look like it's auto-complete related, but it doesn't happen on the same text and as the result is very difficult to reproduce. You probably noticed, but I even put a bounty on it as I haven't been able (so far) to come up with a fix for it. |
|
Yes, I was in the middle of typing a line. More info to follow. |
|
@pkulchenko @thebothead have you considered placing the bounty on Bountysource? That way, the developer is able to claim it seamlessly once the issue has been closed/addressed: https://www.bountysource.com/issues/869743-zerobrane-studio-crashes-when-using-win7-x64 |
|
@ccvergara, good point, although they want 10% on top of fees that paypal or Google Wallet may charge. Other options (like an Amazon giftcard) won't have any fees associated with them... |
|
@pkulchenko the 10% fee includes payment processing fees :) |
|
@thebothead, @bothead, @robzed, I wonder if with the recent move to LuaJIT made the situation with this crash worse, better, or if it stayed the same. Could you give it a try on win7 64bit when you get a chance to see if anything has changed? Thank you! |
|
One note. I've had no opportunity to work on W7-64 this week, but ZBS has been running in the background - without incident - since last week. |
|
@thebothead, @robzed, any new information about recent crashes on win7 64bit? Did the switch to LuaJIT make it better? Thanks! |
|
@pkulchenko, nothing new yet. Haven't done any development lately or |
|
Crashed yesterday (W7-64) when I was developing a relatively short text processing script. Again, it was when I was typing. It idles for days and days on end without problems. I've spent maybe 4 hours (or so) activity using it on Win7-64 this week, so not much. Difficult to say if it's worst or better. What's the best way of getting more information on what's causing this problem? I assume stack traces aren't doing it? |
|
@robzed, @thebothead, when you get a chance, please grab the latest master as I expect 762baba to fix the crash (if it's indeed related to auto-complete). I'd love to hear you are not able to reproduce it anymore ;). Thank you! |
|
@pkulchenko, doesn't look like the executable in master has been updated |
|
@thebothead, there were no (recent) changes to the executables. All the changes were in Lua files, so you don't need to recompile or update executables. Just clone the repo or use the latest zip. Thank you! |
|
@pkulchenko, ok thanks. I am moving to a new dev station with win8 x64 this
|
|
@thebothead, any new issues on win8 64bit? Any new reports during the last 4 days (if you installed the new version)? Thanks!
@robzed, unfortunately not. Some of them do point to handling of pending events ( |
|
@pkulchenko, nothing yet. I actually returned the surface pro I had due to
|
|
No crashes recently on Win7-64. I'd pretty much say it's better than before - had a few days coding on it at least. Will post more only if I get another crash. |
|
This is great! Rob, thank you for the update. |
In my win7 x64 laptop ZeroBrane intermittently crashes when I am working on LUA code in the IDE. I have captured a core dump file from the most recent crash and shared it here (https://docs.google.com/file/d/0B7KLcn-Vx-2VRmpUR2lOdlFFNnc/edit?usp=sharing). The crashes are occurring pretty frequently making it very difficult to make consistent progress when using the IDE...
The text was updated successfully, but these errors were encountered: