I am working vb project in which I am using a media player which is showing videos in a loop. Everything is working fine but after maybe 10 to 12 hours (time is not specific) showing me this dialog box saying close the program or Debug the program (below is the screenshot) but my app is still running.
I created a crash dump file and when I tried to figure out the reason then I found that below is the reason for this error. I used WinDbg to debug the crash dump file.
By seeing this I found that maybe this is a memory leak issue but I am not able to figure out from the code that where is the actually exception is occurring. As my app is not throwing any error during the running app but it throws after 10 or 12 hours.
I am new in VB I would appreciate any help.
Thanks.
According to this post a possible reason could be a memory leak in your code.
Related
I am working on a web based dynamic vb form which is of around 20,000 lines suddenly my system got shutdown due to power loss, When I reopened the system then I found my .vb file is only left with Hexadecimal-Binary kind of text as in the screen shot.
When I am running the code in Visual Studio it is running fine and show the form in web browser but I need to edit it as I am in development phase.
On opening the file in notepad it is showing blank page with lots of blank lines.
I have tried to recover using 'restoring previous versions' but I found 'There are no previous versions available'.
I also have tried to recover using 'Open system restore' in which I found a list of restore point but even after successful completion issue is remain same.
Error screen shot
I didn't any solution for this problem.
I have some my code in distributed manner so I merge those pieces of code and wrote rest of the code.
If any body knows better solution than this, please share it.
I'm new to NSZombie but I have a problem with my app crashing with EXC_BAD_ACCESS. I'm having real trouble finding the object that is causing the problem. Looking online I followed instructions to enable zombie objects.
The problem I'm having has been reported by another person on that page. Enabling zombie objects stops the bad access error but gives me no information. Nothing is printed by NSLog. Is there somewhere else I should look, or am I doing something wrong? I don't really know my way round XCode or a Mac very well as I'm mainly a C# programmer.
Any help would be most welcome.
1) Run your app on Intruments.
2) In instruments, select Object allocations tool(automatically selected if you select leaks tool).
3)Click on the little "i" on top left, within the Allocations tool.
4) Select "Enable NSZombie detection".
5) Press the record button and let your app run.
6) Go through the execution of the app untill it crashes. As soon as there is a crash, you'd see a pop up saying that there was a EXC_BAD_ACCESS. Click on the little -> on the pop up to see the object that has turned into a zombie and the line of code responsible.
Sorry I am unable to upload a screenshot, as am at work.
Expand your project Executable and right click on it. and click on GetInfo->Argument tag aat end of the window you see plus and minus sign button click on + sighn button and write
Name Value
NSZombieEnabled YES
then after execute your project and whenever crash your application click on run munu-> console you see there why your application crash. please try this may be this will help you.
My iphone app is crashing with this in the debug window:
Program ended with exit code: 87
Does anyone know what this exit code refers too. Google isn't helping much.
UPDATE: I have found that this was being caused when I was trying to call
[mutArray objectForIndex:indexpath.row]
and the index was outside the range of the array.
The stacktrace didn't include anything else besides the code 87 message. Also the console window didn't even slide up when the app crashed. Not very useful I guess. Anyone know how to make it more useful in these situations?
"Anyone know how to make it more useful in these situations?"
First, use CMD-SHIFT-R in XCode to show the console window. You should have seen an error message about accessing an array with an out of bounds index.
Also, use CMD-Y to build & debug (vice CMD-R to build & run) your app. If it crashes, you will be in the debugger (CMD-SHIFT-Y for debug window) with the exact line of code that crashes, as well as a stack trace, all your variables, etc.
I'm writing a simple Cocoa Application, no core data or multiple document support. Running on a Mac Pro, OS X 10.6.6, Xcode 3.2.3.
I have reduced my application to the following code in my AppDelegate class:
- (void)applicationDidFinishLaunching:(NSNotification *)aNotification
{
NSOpenPanel *openPanel = [NSOpenPanel openPanel];
[openPanel runModal];
return;
}
From within the debugger, I will run my application. As expected a somewhat not-to-useful OpenPanel will appear. I will click Cancel and it will disappear. All this is as expected. When I click [Command + Q] to Quit the application, the UI will go away but the debugger will indicate that the application is still running (as does the console output).
Based upon all the information I'm reading, I should not have to do anything else in order for this to run right. I've downloaded several examples on the Open Panel's usage but most use the deprecated methods of opening modal giving additional information as parameters. FWIW, I tried those methods and am still seeing the same result.
One last item, when the Open dialog appears, just for an instant I see a message box asking me something to the extent if I want my application to receive incoming connections. The dialog quickly disappears. I don't know if that is part of my problem or not. [Update - this deals with my Firewall being turned on.]
Yes, I'm fairly new at Objective C but not at programming in general. Any words of wisdom is greatly appreciated!
2011.02.07 - Update:
I have walked the debugger line by line without incident. There is no indication of any program failure in the console window.
I say that the debugger is still active after [Command + Q] because the Stop Process toolbar button is still enabled as is the Break button. Further the console indicates that after I tell the application to terminate (either via the menu or key command) that it is still running. The following is the Complete console output from start of run to after I Quit the application.
Program loaded.
run
[Switching to process 62370]
Running...
The Activity Monitor (system tool) will show my application terminating (no longer shows up as a process) but the Debugger will still not transition to "edit" mode - if I tell Xcode to run the debugger again, it will ask me if it's OK to Stop the current debugging session. If I was in Windows I would start looking for background threads keeping the process alive but as far as I know, NSOpenPanel should not be doing something like that.
I have further simplified the program to nothing more than creating a brand new Cocoa application and inserting the code snippet above - no other additions to the template project or updates in any way.
And lastly, when the application is run under the Leaks Performance Tool, everything runs fine when the panel is created but never used. When created and actually used though, at the end of the run I will get the following message in the tool "insufficient task_for_pid privileges (leakagent64)". Googling this hurts. If I read it right, the debugger does not have sufficient permissions to fully kill the target process ??? Now that sounds stupid but ... It does not make sense!
Another update - I just downloaded and ran FunHouse, one of the SDK sample applications that also uses NSOpenPanel. Well don't I feel special. It exhibits the same exact behavior. So from this I conclude either Apple has a bug in their code, my machine is special and messed up, and finally, it is Not my code that is at fault. That being the best part. Tomorrow, I will use a friends Mac and see if the same behavior is exhibited on his box.
This is just too weird.
I rebooted my box, took it to work and found it worked like a charm! I will assume this is fixed and has nothing to do with any other connected devices at home as compared to at work.
If it re-exhibits at home, then it is a network/device issue. Thanks all for your inputs and suggestions! Very much appreciated.
What, specifically, does the debugger say? It's possible that your program crashed, so the debugger is showing you information about the crash.
What if you omit any attempt to run an Open panel?
I have noticed that AVAudioRecorder (iOS) hangs when I pause and resume 8 or more times during the recording. On the simulator it hangs indefinitely, and on the device I get this errors:
AudioQueueStop posting message to kill mediaserverd
Does anyone know how to prevent this, or is there a workaround? My problem is that I try to load the file into AVAudioPlayer afterward and the resulting loaded file has no duration (and doesn't play). The strange thing is that I am able to save the file and later play it just fine. I'm not certain yet at what point the file is playable, but was hoping if there is a solution to the issue with the recorder, I won't need a workaround.
I've got the same same problem and I thought i had found a workaround, it seems to work for small recordings, but it still freezes for longer ones:
[NSThread detachNewThreadSelector:#selector(stop) toTarget:myrecorder withObject:nil]
maybe it can work for you if you're lucky, have you filed a bug report? i'll file one now