I am seeing frequent crashes, while running a Java program, always immediately after compiling.
I have compile and run both on a hot key, which means I can initiate the run very quickly after compile, and it's *always* when I run a program hard on the heels of a compile. The tool completion beep will still be playing as I hit run.
I have had it happen for a variety of classes/programs.
I have not tried 1.4 for either running or compiling.
Output is being capture by both compile and run to the tool output window.
One final detail. I have run programs dozens, even hundreds of times in the particular instance of TextPad. The consistent factor seems to be trying to run hard on the heels of another tool (the compiler) finishing.
TextPad 7.0.4, 32 bit
Windows 7 Ultimate, 64 bit, Service Pack 1
Java Compile Version: 1.5.0_18
Java Runtime Version: Java 1.7.0_21
This is becoming incredibly annoying, as I often have dozens of files open from widely disparate directories and TextPad only save MRUs on exit (which doesn't happen when it crashes). It should save MRUs immediately when they are changed.
Crash when running Java program
Moderators: AmigoJack, bbadmin, helios, Bob Hansen, MudGuard
-
Kiwi6469
No, Not Running Tool - Closing Tool Window
Didn't get right exactly what I was doing to trip this crash - it's closing the tool window too soon after running a tool (in my case often the Java 5 compiler).
If I ALT-F + C to close the window too quickly TextPad crashes.
If I ALT-F + C to close the window too quickly TextPad crashes.
Please uprade to TextPad 7.0.7 and see if that helps. If the problem still occurs, send the diagnostic dump file to "support@textpad.com".
-
Kiwi6469
TextPad 7.0.8 Still Crashes
Upgraded to 7.0.8 as provided, but am still seeing two distinct crashes when running tools.
The first is a fault that causes textpad to create a crash dump. The second is a hard fault in the VC DLL which causes TextPad to fault and Windows kills it.
Both are frequent enough to be extremely agravating - I have seen about 10 today.
Details of both already emailed to support@textpad.com.
The first is a fault that causes textpad to create a crash dump. The second is a hard fault in the VC DLL which causes TextPad to fault and Windows kills it.
Both are frequent enough to be extremely agravating - I have seen about 10 today.
Details of both already emailed to support@textpad.com.