I've come across this annoying problem that I haven't found anywhere else. I've being using Julia in Atom for at least a few months, but suddenly today the console becomes unresponsive when I try to edit a file. Switching focus to a new file seems to cause some code to run in the background, which prevents me from executing any other code in the console.
Eventually an 'Internal Error' window pops up saying that there is a stack overflow error, which tells me that something hidden is endlessly running in the background.
Any ideas on what it could be?
The error output from ctrl-alt-I is:
Uncaught (in promise) cancelled by julia
misc.coffee:10
Julia Boot: 717.02s
internal/process/next_tick.js:103 Uncaught (in promise) cancelled by julia
internal/process/next_tick.js:103 Uncaught (in promise) cancelled by julia_tickCallback # internal/process/next_tick.js:103
Related
Since my last computer update, when I am running scripts in Rstudio, errors do not cause interruption in the execution (for example : if a stopifnotcondition in a function call is not met, the execution is not interrupted !), but instead raise warnings (with a warning message Warning: Error [...]. I find this behaviour very dangerous, and would like to restore the previous behaviour, but I did not find how to do it.
Does anyone know what happens and how I could force errors to interrupt the function/script ?
Thanks in advance
As you can see there is no debugger written here or any breakpoints given still it just haults execution here whenever Angular project get logged out due to timeout
that was a silly one. I just unchecked the box of 'Break when this exception type is thrown'. From the next executions it's not getting haulted.
As it turned out, this problem appears only when there is an error in the code.
A code without errors runs smooth, but as soon as there is even an 'undefined index' error, the whole server hangs, seems falling into sort of an endless loop.
The environment is Windows, Apache 2.4 from ApacheFriends, PHP 5.6, Symfony 2.3
It turned out to be a consequence of several issues:
Somewhere in the code someone put ini_set('max_execution_time', -1);
I am working with Doctrine.
I happen to process considerable amount of data
Twig, when trying to render an error page, attempts to var_dump() a backtrace.
And when using Doctrine, you know, it's better not to try `var_dump() a query result (or a back trace which is effectively the same).
After hardcoding values for memory_limit and max_execution_time using php_admin_value I was able to get the long sought error messages in the error log:
[13-Jul-2016 17:28:32] PHP Fatal error: Allowed memory size of 1280000000 bytes exhausted (tried to allocate 1245970432 bytes) in \vendor\twig\twig\lib\Twig\Extension\Debug.php on line 66
[13-Jul-2016 17:28:32] PHP Fatal error: Maximum execution time of 60 seconds exceeded in \vendor\symfony\symfony\src\Symfony\Component\Debug\ErrorHandler.php on line 136
Looks like Twig was choked by the back trace and then Symfony error handler for some reason hanged.
So I just commented out var_dump() in a Twig error handler and thus was able to make my system work.
Would like to see a better solution though.
When I run meteor, sometimes I get an error and it hangs on
=> Your application has errors. Waiting for file change.
I think I've let it sit before and it eventually got past that message, but it always takes a long time. What file change is it waiting for? Is it npm or meteor? And is it slow for others, or is it my Koding box being finicky? Can I just stop the process or should I wait?
I don't need help resolving the error that caused this message in this specific instance, just wondering how to handle meteor errors in general when it hangs on this message and curious as to what it means.
I've updated HereMaps JavaScript from 2.2.4 to 2.5.3 and the map has stopped working on Chrome (version 31.0.1650.57 m). Firefox and IE work as before.
On the console I see the message many times
Coroutine 'nokia.maps.map.render.p2d.Engine#_renderCo' aborted abnormally with exception base.js:158
TypeError: Cannot read property 'body' of undefined
Does anyone have a hint of what might be wrong?
Thanks.
It is very difficult to answer your specific problem without seeing your code, but I am able to produce a similar error which may help you track down your issue.
If you are getting multiple error messages, then it is likely that the JavaScript library itself is calling something periodically. From the text of the error it likely that the library is running a Coroutine, which is usually used for threading within the application.
The error I can produce is in a callback - if I add an overlay to the map, and deliberately try to access a non-existent property within my code I can get:
Coroutine 'nokia.maps.map.render.p2d.Engine#_renderCo' aborted abnormally with exception base.js:158
TypeError: Cannot read property 'bar' of undefined
This was because I added a typo as follows:
I changed the reference from foo.something.bar in the callback to foo.does_not_exist.bar. So I guess somewhere in your callbacks you are referencing foo.something.body in your callback - it could be in a listener for example.
Another possibility, is that you are switching directly to Display.SATELLITE when you are creating the map - this is no longer allowed:
Taken from the News feed on developer.here.com:
Breaking changes with 2.5.3
The new rendering engine requires the map to be initialized
asynchronously. If you want to change the center, zoom level or the
base map type the API now requires the application to wait for the
"displayready" event to be fired. This event is only fired once.
Please refer to the developer's guide (section "Beyond the Basic Map Application
") for details.