I have a big issue. I use an obfuscation solution to protect my solution.
When I try to build the solution in "Debug" mode, it finishes in less than 2 minutes.
When I try to build the solution in "Release" mode, if freezes at 'Compilation of [number] methods.
There is more than 100 thousands.
What should I do to overcome this issue?
Can someone have a solution to this issue?
Image screenshoot on where it freezes
Related
An MFC app crashes on startup at the same place about 30% of the time. I have seen the debug version crash a couple times, but not nearly as often as the release version.
It appears to be internal to MFC LoadState() processing. If you delete the workspace before each start then it never crashes.
I've created a sample project to reproduce the problem. It's located at the following link: LoadStateBug Example
I'm using VS2017. Extract the zip, load the project, use x64 / release build. To make it crash, I press F5, click the X to close the window and repeat over and over, within 10 times you should see the crash (sometimes it takes a few more).
Is there something in the sample causing it or is it MFC? If MFC, is there a fix or workaround.
Thanks.
I have developed several (experimental and prototype) iOS apps using Xamarin and the new Visual Studio for Mac OS and the build-times intermittently take about 5-10 minutes on average. When starting a new project, build-times are fine. After a few changes in the source code while working on my apps (no specific changes). For no reason, build times start increasing to 5-10 minutes. I've tried all possible build-options (linking, no linking, SDK versions, new consigning certificate, etc..).
Upon investigation with the Activities-app (Mac OS, Sierra) i find that the "codesign" process is taking up 110% CPU and runs for as long as the build takes to complete.
Does anyone have any experience with this problem?
I have the same issue
First Try close Visual Studio then delete bin , obj from your project , finally start visual Build and Run
Second Try make sure you build in real device sometimes emulator cause trouble , how you make sure , if build success but deploy stuck many times
In my case, after wiping my PC and completely re-installing Windows 10, my build speeds increased by 2x.
Clean builds that used to take 2:20 minutes now only take 1:20 minutes, and incremental builds that used to take 40 seconds now only take 17 seconds.
Doing an incremental build + deploying to device used to take around 4 minutes. Now it takes only 55 seconds!
I'm not sure what was leading to this awful experience, but I'm glad it's not so terrible anymore (still slow though).
Go to your *.Android project => "Properties" => "Android Options" and set the following options:
Dex compiler: dx
Linking: None
This gives me a fast build speed
I'm experienced a weird issue with Instruments. When I try to Profile the application, it gets stuck on an interface and becomes unresponsive. The same application is running perfectly on both Simulator and Device -- when not run with Instruments.
Is anyone else experiencing this issue? What's the workaround?
Additional Information:
1). This situation is occurring with both Allocations and Energy Diagnostics templates.
2). I'm profiling using "Debug" Build Configuration.
3). This issue is reproducing for more than one application.
Turns out, there were some NSLog statements in the code, and Instruments immediately freezes when NSLog statement is called. Pretty annoying and inconvenient (if you ask me).
Removing ALL NSLog statements from the code fixed the problem.
I'm currently learning OpenGL and I've noticed a rarely occuring performance problem:
My program is rather small so it's not a performance problem with the code itself, but when I'm running the code via Visual Studio I sometimes only get 1-2 FPS instead of the usual 60.
Once this happens I can restart the program as often as I want to (in debug and release mode alike) and it won't go away.
However, when I close my Firefox (or manually shut down the plugin-container.exe though task manager) and restart my program everything is fine again. After that I can start Firefox again (with the same tabs open) and the bug does not reappear.
I use the newest version of Firefox, and I've had this bug with several programs already - both made by me and others and using different versions of OpenGL. However I don't think I've had this problem when starting a compiled exe directly, but only by using the Run feature of Visual Studio.
I've searched the web but I only found a link about the generally bad performance of this plugin-container.
Does anyone else have this problem? Do you know any walkarounds or fixes?
PS: Regarding isti_spl's answer:
The CPU utilisation of the plugin-container.exe jumps to the 50% limit when the problem happens.
I'm working with Visual Studio, but the problem only occurs when I also have Firefox running (it most certainly is because of this plugin-container, so it probably won't happen with other browsers).
It's hard to isolate the problem because I can't replicate it. It might happen 1 out of 50 times.
I'll see if closing flash-related tabs (youtube, blip.tv etc) fixes the problem next time it happens.
Can you isolate the problem?
You first mentioned running visual studio then firefox. Please try to run separately.
Under FF. is it caused by WebGL or flash plugin? Is it caused by visiting specific sites?
Is it FF specific or happens under other browsers too?
Does CPU utilisation jump high? Please verify that too and which process consumes most CPU.
Not sure, but likely gpu driver + flash problems.
If so, the problem is not in your code, other GL program should be affected too.
I'm on windows 7 x64. Using C++ in Visual Studio 2008 and 2010.
When I run any own application with VS after, aprox, 15 seconds the application is forced to exit. No messages, no Exceptions, no nothing. It doesn't matter how simple it is the application.
After a couple of weeks reviewing and commenting my code, I tried by reinstalling my S.O. and programs, thinking in some driver update or something similar. Whatever it was should solve my problem. That didn't solve the problem either.
You can see an example in
https://twitter.com/#!/nachovall/status/176996407780188160/photo/1/large
Note that it hasn't empty the buffer!! Just crazy.
I'm thinking in some whatchdog problem. I mean some, windows 7 issue which causes a given application to exit after some seconds.
The worst thing is that I have no idea about how to search this in Google. 'Silent crash'? It's not crashing, just exiting.
Well, if anyone knows what the problem is... you know.
By the way, I did a whole hardware analysis looking for some CPU or Memory problem. Nothing found.
Even more. I run the debug. I set a breakpoint in the first line of code. The application is doing nothing. Just waiting me to step over in the debugger. After 15 seconds, the application ends. Cool ha?
Ok, all night awake but finally found.
It was the antivirus program. Avast version 7.0.1407. When I disable it, everything get sense again.
It's been 2 weeks. 2 large and exhausting weeks. Anyone who's using this antivirus, please be aware.