Enso Crashes over night

Bug #1249005 reported by mellamokb on 2013-11-07
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Enso Project
Undecided
Unassigned

Bug Description

I get the message "Enso can't go to this application right now" so often it has made the "go" command basically useless for me. It may or may not be related to locking computer overnight and keeping everything running for days on end? I typically have around 40-50 applications open at any one time and most of them stay open for days on end. If I restart Enso it will start working fine again, but will probably have problems again when I access my computer tomorrow morning.

Thanks!

mellamokb (kbachtold) wrote :

I am still having this issue. I just restarted my PC this morning, and a couple hours later, I wanted to switch to an app, and got "can't go to this application right now". If it happens every single time I want to use it, the tool basically becomes useless...

On an unrelated note, the "report bug" command isn't working properly. I can fill out the bug details, but then when I submit the bug, I get:

http://www.humanized.com/enso/bugreport
Not Found

The requested URL /enso/bugreport was not found on this server.

Apache/2.2.22 Server at www.humanized.com Port 80

mellamokb (kbachtold) wrote :
Download full text (33.5 KiB)

So since the bug report feature is not working, I imagine the System Information dump may be useful, so here it is reproduced in full after the most recent "crash":

I am still having this issue. I just restarted my PC this morning, and a couple hours later, I wanted to switch to an app, and got "can't go to this application right now". If it happens every single time I want to use it, the tool basically becomes useless...

On an unrelated note, the "report bug" command isn't working properly. I can fill out the bug details, but then when I submit the bug, I get:

http://www.humanized.com/enso/bugreport
Not Found

The requested URL /enso/bugreport was not found on this server.

Apache/2.2.22 Server at www.humanized.com Port 80

----

So since that isn't working, here is a System Information dump in case it is helpful:

<os> Windows NT v6.1 Service Pack 1, build 7601 (6,1,7601,3,1,0,134238720,0,6,Service Pack 1) </os>
<commandline> ['C:\\Users\\%username%\\AppData\\Local\\HumanizedEnso\\Enso.exe', '--disable-monologue-boxes'] </commandline>
<enso> Enso revision 3268 (pure, frozen) - Built by VM-TESTER-01 @ Mon Jan 14 14:41:22 2008 </enso>
<traceback> None </traceback>
<log> 05 10:12:28 2013 TaskBox\MessageWindow.cxx L76]: Created message window.
INFO [Thu Dec 05 10:12:28 2013 Utils\ComponentLoader.pyc L211]: Initializing component 'BetaProducts.EnsoBridge'...
INFO [Thu Dec 05 10:12:28 2013 EnsoApp.pyc L211]: Entering the main event loop.
INFO [Thu Dec 05 10:12:28 2013 Input\InputManager\InputManager.cxx L304]: Installed exit handler.
INFO [Thu Dec 05 10:12:28 2013 Input\InputManager\HookHandlers.c L169]: In _installKeyboardHook().
INFO [Thu Dec 05 10:12:28 2013 Input\InputManager\InputManager.cxx L313]: Installed keyboard/mouse hooks.
INFO [Thu Dec 05 10:12:28 2013 Input\InputManager\TrayIconManager.cxx L237]: Taskbar appears to exist.
INFO [Thu Dec 05 10:12:28 2013 Input\InputManager\TrayIconManager.cxx L266]: Shell_NotifyIcon() returned: 1
INFO [Thu Dec 05 10:12:28 2013 Input\InputManager\InputManager.cxx L321]: Initialized tray icon manager.
INFO [Thu Dec 05 10:12:28 2013 UserInterface\WebServer\Server.pyc L382]: Bound to port 7070.
INFO [Thu Dec 05 10:12:28 2013 UserInterface\Messages\PrimaryWindow.pyc L183]: newMessage: <p>Welcome to <command>Enso</command>!</p><caption>copyright 2006 by Humanized, Inc.</caption>
INFO [Thu Dec 05 10:12:28 2013 UserInterface\Messages\__init__.pyc L315]: Primary message dismissed.
INFO [Thu Dec 05 10:20:16 2013 EnsoApp.pyc L119]: MEMOIZE USAGE STATISTICS:

     Number of functions which used memoizing: 4
     Number of unique function values recorded: 48

INFO [Thu Dec 05 10:27:10 2013 EnsoAppLauncher.pyc L512]: Validating directories.
INFO [Thu Dec 05 10:27:10 2013 EnsoAppLauncher.pyc L526]: Setting process memory usage parameters.
INFO [Thu Dec 05 10:27:10 2013 EnsoAppLauncher.pyc L365]: Initial process working set size: (204800, 1413120)
INFO [Thu Dec 05 10:27:10 2013 EnsoAppLauncher.pyc L383]: Process working set size is now: (8388608, 16777216)
INFO [Thu Dec 05 10:27:10 2013 EnsoAppLauncher.pyc L457]: ImmDisableIME() called succ...

mellamokb (kbachtold) wrote :

I don't understand the output of the System Information dump, but I see messages like 'Access is denied.'. So if it helps, this is a Windows 7 , 64-bit installation, and I am Local Admin on the machine, with UAC prompt disabled. Also, this machine is joined to a Windows Domain.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers