Xojo shutdown does not log feedback case

After using the new Xojo 2015 r3 for a while (the performance improvements are fantastic on Windows!!), there have been a couple of times where I have received an error while working that shows a Xojo Window that says something like “Xojo has encountered a fatal error and must shutdown”. The Feedback application opens but there is no feedback window that appears for me to enter what I was doing when the error occurred and the Feedback program does not log the problem in the ‘My Cases’ section in Feedback.

If Xojo engineers don’t know about the problem, then it can’t be fixed. Is there a manual Feedback log file that is saved with each failure in the background on my computer with all the details of the error? If so then I can manually upload the file and create a feedback case. The most recent Xojo shutdown was when I was using Javascript.

Although my Feedback account looks great with lots of closed, fixed, reviewed, and verified cases, the recent errors are not appearing.

These errors are happening on Windows 10.

This is just a friendly notice to let the staff know about this issue.

If it has been logged at all it should be in AppData > Roaming > Xojo > Feedback > Reports
Simply starting Feedback directly should have it locate them and ask if you want to submit them

Now its possible that whatever error has been encountered has put the IDE in a state where it cannot successfully create a file and write to it

You can submit a report without a stack trace etc (although having one is usually better)
Just provide steps if you can

The good news is that there is no information in the \AppData\Roaming\Xojo\Feedback\Reports\ folder, meaning Feedback was likely working properly.

After restarting the Feedback program there were no additional entries added.

Yes, that makes sense. If there wasn’t an error file created then there is nothing for Feedback to submit.

[quote=223910:@Norman Palardy]You can submit a report without a stack trace etc (although having one is usually better)
Just provide steps if you can[/quote]

After Xojo forced a shutdown, I went back and tried to create the error again and wasn’t able to reproduce it when loading the same xojo_project_file. Without an error logfile then this makes it almost impossible for the Xojo Engineers to track down the issue. I’ll search for available software that might help when logging these issues to give you a helping hand in making Xojo better.

Thanks :slight_smile:

Since its not a hard crash even having mini dumps enabled won’t help :frowning:
bummer

i’ve had the exact same thing once.

An iOs project has been screwed up. Gone from xojo_binary_project to xojo_project (different folder saved with File->Save As).
Opened xojo_project all iOS views where screwed up. Lock icons where visible but the controls not.
Basicly on all views they seemed blank but had controls, which i can’t select (even using the right mouse menu).

After selecting one of the controls on any view there, it crashed.

Somehow it crashed and the logs are not there, feedback didn’t show a case.

We need to be kind of pedantic about what a “crash” is
If its a hard crash feedback wont have any chance - basically the app has run out of memory etc and you get a crash log (mini dump or OS X crash log)
There is unlikely to be ANY opportunity for the IDE to log anything under these circumstances

IF its an unhandled exception or other assertion from our Xojo code then there might be one

I have the same problem. Window 7 pro 10 GB Ram Phenom II 1055T with SSD and Xojo 2015R3 pro license.

Project: my cash program
32 Bit ok
64 Bit “Xojo has encountered a fatal error and must shutdown”. The Feedback application opens but there is no feedback window that appears for me to enter what I was doing when the error occurred and the Feedback program does not log the problem in the ‘My Cases’ section in Feedback.

Hello,

Xojo just stopped working and the feedback message box appeared asking me to submit or ignore. Pressing submit multiple times did not cause a case to be logged. Before the program was non-responsive, I was able to Ctrl-Alt-Del and right-mouse click on Xojo to create a dump file (Xojo.DMP is 666,351 KB), and Feedback was also not responsive and was able to create a dump file for feedback at the same time (Feedback.DMP 1,147,763 KB). These files are huge.

I am attempting to upload XojoDMP but am not sure they will be accepted in a new feedback case due to their large size.

I’ll give it a try. The dmp files are saved on my computer at: C:\Users\\AppData\Local\Temp

<https://xojo.com/issue/41537>

The Xojo.DMP file upload times out because of the large file size.