I am developing an Electron app for Windows and within the past couple weeks the app has begun to crash intermittently without any apparent cause. I downloaded the windows debugging tools to examine the crash dumps and found the error Unable to find system thread 1C10. What does this error mean? How can I proceed?
Related
I am trying to develop an application on windows 10 in Flutter 2.x.x. I am implementing bluetooth functionality with the app. The problem is that application is mostly crashing on startup. It is working only once I tried several times after it crashes.
The error message is just Lost connection to device.
Could you help me on it?
I am trying to use the debugger in Xcode, but since I installed version 11.2, it keeps crashing with this message: Message from debugger: The LLDB RPC server has crashed. The crash log is located in ~/Library/Logs/DiagnosticReports and has a prefix 'lldb-rpc-server'. Please file a bug and attach the most recent crash log.
The crash log is here: https://drive.google.com/file/d/1HB0mAWHiBgZRtyuDWRvpdZKPeQlMRnKR/view?usp=sharing
Is there any solution/workaround for this?
I had developed an app and uploaded it on app store. The app got rejected due to crash. But my problem is that I cannot detect this crash while running app on device for testing. App is working properly on the device.
The app is been created in unity and then I had exported it to xCode.
So I want to ask that how can I get to know about where it is getting crashed. Also how can I traverse the crash log.
Any help will be appreciated
Thanks in advance
Did they tell you about:
– Where crash happened? (At launch, On logging in, or in specific screen)
– Did they send you any images?
– Which devices and iOS they were testing
– They will surely send you crash log, please post it.
You said you cannot replicated the crash, but did you tried with simulator or real devices?
Since you are missing many information, I cannot give you a certain answer. My advice for you is to
1) Updating your question
2) Read my post about how to do when your app got rejected, or my post about how to symbolicate crash log
3) You can also follow the topics in stackoverflow: Iphone App was Rejected Due to We found your app crashed on launch so we were unable to review it and App rejected due to crash. They are very helpful
Actually, app was getting crashed on devices with 64 bit architecture. as older version of unity don't support 64 bit architecture. Unity 4.6.2 onwards support 64 bit architecture. Thus rebuild the ios app and it worked fine.
I have problem with Delphi Mac OS X development. I get debug assertion failure error when I try to debug program. My application is just simple form where is few TLabel and TEdit component. Also there is two TImage components where is two images included. And there is also one TProgressBar component on my form. Connection between mac and my pc works ok. It tries to start application when I run it but it disappiers and Windows 7 and Delphi shows error debug assertion failure.
At first there was problem with deployment and my project file was corrupted so I created new project and then I added my old form to new project. After that compiling application works ok but now I get error message debug assertion failure.
I have Delphi XE5 and Windows 7 64-bit.
Mac computer is macbook pro.
PAServer on OSX is a bit buggy and it sometimes crashes with these assertion failures. It's not your application that raises the assertion failure.
If PAServer crashes with an Assertion when trying to start your application, then I'd suggest the following:
1. Close Delphi and PAServer
2. Wait until both have completely shut down
3. Start Delphi and PAserver again
Sometimes this already solves the problem.
If this does not help, try starting your application from OSX from the Terminal and see what happens. Chances are you see an access violation or similar printed to the terminal window. If that is the case you might have a bug in the initialization part of a unit. PAServer likes to crash with an assertion failure if that happens. You'll have to debug the start-up process of your application using F7 and F8. You might be able to speed this up by setting breakpoints in the initialization of some units.
Agree with Sebastian. PAServer is not stable at this stage. There are MANY reports about this:
PAServer can't load dyld: Library
Delphi XE5 PAServer Unauthorized user
How can i debug my DLL project with Delphi's PAServer
Delphi XE4 iOS can't connect to PAServer
https://stackoverflow.com/questions/28115855/paserver-crashes-on-win64
Delphi Mac OS X
Solution: wait until they release something stable. (You will have to pay again, of course)
This question involves Unity3d, but it's not specifically about it.
I'm building a Unity project for OSX; as a result, I get complete .app that I can run — without xcode project in between, as on iOS. Everything goes OK, but my app hangs up from time to time, forcing me to kill it.
What OS X tools can I use to help with debugging such a situation? May be there's something in xcode instruments that can help me?
You'll want to get the crashlogs, which will give you the callstack, and therefore the location in the code of the crash.
Here's some info on how to find the crash logs:
http://serato.com/scratchlive/support/6600/how-to-get-a-crash-log-in-mac-osx
And here's some info about what to do with them once you have them:
How to symbolicate Mac OSX crash reports issued by Apple?