I had this very annoying problem that while debugging, suddenly it started to show the disassembled code rather than the C++ code, via google I found several with the same problem, and a suggested weird solution here which I'm not sure how to interpret. I tried things similar to that post and found a solution:
Shut down and restart QT Creator
In left-hand tab "Projects", untick then re-tick "Shadow build"
Seems like voodoo right? But I noticed that step 1 clears all breakpoints, and step 2 temporarily changes some paths after which it says "evaluating" for a second in the lower right corner. So perhaps it's not as weird as it sounds, apparently a few things are cleared during this process.
I don't think I'm supposed to write answers to my own problems here but I thought it would be a waste not to post this solution to this very annoying problem that apparently more than I have encountered. The next guy hopefully finds my post.
I cant post links to others with similar problems since I need a higher reputation then.. :-/
It probably helps if you uncheck options to break debugging on Thread creation and Thread exit if you have these options checked for the Debugger. These options will certainly pop the disassembler view up when you start debugging even if you haven't set any Breakpoints in your code. You find these options in menu Tools/Debugger/CDB. If you want to break on C++ exceptions leave that option checked, otherwise uncheck that too.
Related
I'm writing a WP plugin that makes changes to tags and categories. After making my selections and submitting the form, the page reloads and executes wp_set_post_categories and/or wp_set_post_terms.
It works fine even in other Chromium based browsers, but when I try it in Chrome, it throws the following error:
Error code: RESULT_CODE_INVALID_CMDLINE_URL
There's a "Learn more" link, but nothing happens when I click it.
After refreshing the page, I can see that my script did what it was supposed to do, but I'd like to eliminate this error if possible.
I found this support page about the error code, and I turned on logging to see if that would give me any clues, but I don't really know what to look for.
Please let me know if there is any additional info I can add that might lead to an answer. Thanks!
I don't know what might have caused your problem, but I know a problem that causes this error. So even if it is too late someone may benefit from it. I found your question when I was answering a related problem here. you can read it if you want, but in short this happens when an array of length infinity is created. (like a
stackoverflow
). If you want to regenerate such an issue you can use this js code below.
let arr = [];
let arrcounter = 13;
for (let x = 1; x <= arrcounter; x) {
arr.push(x);
}
This is an infinite loop that adds an element to an array.
This might not be your exact problem, but I hope this helps.
I was running into this problem too, and I found in the end that my web app was running out of memory. So #EHM is right - an infinite loop that keeps adding to an array will eventually run out of memory and cause this issue.
But in my case, it was running out of memory because the js heap was not getting cleared after each page refresh. For testing purposes, I was running a puppeteer script that refreshed the page many times, and after 40 or so refreshes it would crash with the RESULT_CODE_INVALID_CMDLINE_URL error.
I'm not sure why chrome was not clearing the heap between refreshes, but this type of issue has been reported before under certain conditions, see this issue: https://bugs.chromium.org/p/chromium/issues/detail?id=113983.
Without digging too much here into why it can happen, I will post here how to detect if your memory is getting out of control. You can use the chrome dev tools performance monitor, a built-in part of chrome dev tools:
The official docs on the performance monitor are here: https://developers.google.com/web/updates/2017/11/devtools-release-notes#perf-monitor
In case that link stops working, here are the basic steps:
Open chrome dev tools while on your web site with a memory issue
Press cmd-shift-P to open the command palette. Search for "Performance Monitor"
Once the perf monitor is open, watch the heap size in real time. While watching the heap size, reproduce the condition that causes the RESULT_CODE_INVALID_CMDLINE_URL. You should see the heap size gradually increase until the error occurs.
Now that you can see the memory leak happening, try to isolate what part of your code is causing a memory leak. Chrome dev tools has other tools to record heap usage and isolate which objects are being allocated. You may have an infinitely growing array, like #EHM mentioned, or a number of other issues. In my case, Chrome didn't seem to be releasing certain DOM nodes between refreshes. I was able to fix my script by navigating to a different domain between refreshes, which caused chrome to correctly release all the DOM nodes. To learn all about finding memory issues in chrome, read their article on the topic here: https://developers.google.com/web/tools/chrome-devtools/memory-problems
I have absolutely no idea why, but on 2 websites (2 websites that I professionnaly work on, and they havent been hacked or compromised), my Chrome console keeps clearing every 500ms.
Which is pretty annoying.
I desactivated all extensions. Tried private browsing. It's the same thing.
I uninstalled chrome as well as my extensions. Same.
When I try to reproduce it on someone else's computer, I cannot.
When I use another Chrome session the issue does not happen.
I have absolutely no idea how to get rid of this or what is the exact cause of the issue.
The code running is :
setInterval(function(){console.clear();console.info('Console was cleared by browser extension.');},500);
Since I unfortunately do not seem to find the reason, my only question will be : would there be a way to desactivate that code or postpone the setinveral to a bigger number?
Thanks !
In Chrome, on the developer tools, click on the settings icon, and tick the the "Preserve Log" option so the console is not cleared.
If your websites happen to be ecommerce (Magento specially) I'll advice you to check your code well for unknown js. This is one of the "symptoms" of the Magecart credit card skimmer. Preserve log option
When:
Live Preview is running
I'm writing CSS
& I hit Enter to use an auto-completion recommendation
Then:
The auto-completion occurs
The cursor skips down a line & indents
I usually work around this annoying cursor movement by closing Live Preview, but I'd really rather not. Is this a bug or am I missing something? How can I fix it to where it just simply fills in the auto-completion recommendation?
Thanks!
Brackets 0.41
Windows 7
Brackets doesn't normally behave this way - you may have an extension installed that's causing trouble. Try using Debug > Reload Without Extensions and see if the problem still happens. If that fixes it, you can systematically disable individual extensions until you find which one was causing the problem. I believe the "Emmet" extension has caused some similar issues in the past, so that might be a good one to check first.
Once you know which extension causes the problem, I can walk you though filing a bug with the extension's author so it can be fixed.
If you're seeing the issue even after Debug > Reload Without Extensions, then it would be good to get more specific with the steps that trigger the problem. For example:
Open the default "Getting Started" project and open its main.css file
Start Live Preview
Add a new line to the end of the body rule
Type font-w and press Enter
type b and press Enter
When I do these steps, no extra newline is inserted. What steps should I use instead to see the problem?
I found this as I was experiencing the exact same issue. Try disabling any scripts called in your html one by one to see if it goes away. My issue was a script I was loading from a Wu
I was having this issue for several days. I finally figured out a fix for ASP.NET programmers, and I figured I would share.
Problem
After setting a breakpoint, and then debugging my breakpoint would turn yellow with an exclamation point. When hovering over the breakpoint it would say "The breakpoint will not currently be hit. No symbols have been loaded for this document.”. I tried cleaning, rebuilding, changing various settings through my project and visual studio. Nothing worked.
Solution
I was digging around in the Solution settings. I noticed that under "Web" tab my Start Action setting was set to something other than "Current Page". After setting it back to current page everything worked out.
I hope this solves the issue for other's like me that were exhausted after trying every other suggestion/answer they could find on the internet.
The issue only happens to me on ASP.Net Projects
Right Click the Web Project
Select Property Pages
Start Options
Make sure Use current page is selected (as shown below)
This happens because your project still has errors, so run the last correct version.
Correct your mistakes, surely it is the error "CodeBehind" change it to "CodeFile" and surely the errors disappear, you can return project run without errors.
I want to preface this question by admitting that I'm still very much a novice, to Xcode 4 and to development in general. But I find I learn the most when I've made mistakes and been able to discover ways to correct my errors.
So I was mucking about in Xcode, following an example in the book I've been studying, in this case trying to determine why the keyboard wouldn't hide when I touched outside a text field. In the process of experimentation, I tried adding an Outlet to the top level View of a View Controller, dragging into the Header file to automagically create it. I knew almost at once this wasn't what I wanted, and I deleted the reference in Interface Builder, and the code it had added to the other files.
And when I did run the program, it threw an exception. Being new to this, I didn't think to check the log files, and when I couldn't work out what the error was, I restored an earlier version of the project from Time Machine, and tried again -- same result. I restored an even earlier version and tried again -- and got the same error!
When I finally did have the good sense to look at the log file, I noticed the reference to the name of the Outlet I had added, but removed! But these were older versions of the code, before I'd even made that change.
I made a thorough search of the code, and my NIB file, looking for any reference to the deleted Outlet. I couldn't find anything.
I eventually replaced the NIB file with a version from the tutorial from the book I was following (it was identical, and easier than rebuilding it from the bottom up), and all was well, everything ran just fine. But now I'm left wondering -- what could I have done to make this error so persistent, across different versions of the file? I'm already kinda uncertain about the way Xcode 4 will automagically add code under certain circumstances (that's probably more dangerous than useful for the novice), and I wonder if this is a bug in Xcode 4, or if I inadvertently tripped over a useful feature.
Xcode loves to play tricks on you. I've several times gotten an XIB mysteriously hosed up to the point where I had to delete it and start over. No matter what I'd do to the XIB some elements wouldn't display correctly (or at all).
In a recent case I had an XIB with a label with the text "Start date:". I changed that label text to "Treatment date:", but it still kept coming out "Start date:". I opened the XIB as text and scanned for "Start date:" and it wasn't there. So I tried dragging the label off to one side. Then it displayed the correct words. Dragged the label back to the correct place -- back to "Start date:". I finally deleted the label and recreated it and then the text came out correctly.