Debugger creates 0 byte files

[vidrep]

When saving debug report, often times a 0 byte file is created which cannot be opened .

[vidrep]

Filetype is not recognised by the system, but appears normal when attachment opened in browser.

[anevilyak]

Sounds like you're simply trying to open them too quickly ; it can take some time to retrieve the information that gets written into the report, depending on the size/complexity of the team being reported on, and the speed of your system, so it's entirely possible for the file to be 0 bytes for a few seconds after creation. While it's 0 bytes, there's no data there for the system to recognize its type by, hence the error message you're seeing. This goes hand in hand with the fact that the files you've attached to this ticket are in fact not 0 bytes, and look like normal/complete reports.

[vidrep]

I have been seeing this for awhile now. Either the debug report appears as a StyledEdit file on the desktop or as one not recognized by the system. Sometimes they are 0 byte, although the examples I attached this time are not. When I get one of those I'll attach it.

[vidrep]

I unzipped hrev46656 and installed to a fresh initialized hard drive partition. After opening "about system" the debugger activates. Saved the debug report and waited several minutes before trying to open ( as per suggestion). System does not recognise this file type (same as before). See attached.

[vidrep]

Attached 0 byte debug report generated from hrev46900_x86_64.

[umccullough]

Replying to vidrep:

Tried to attach 0 byte debug report generated from hrev46900_x86_64, but trac does not accept 0 byte files for upload. See screenshot instead.

Yeah, I can't see how a 0 byte file would help anyone determine what's going on anyway - I think we can just take your word for it that it did what you say it did in that case :)

[vidrep]

Is there any other way of capturing data that might be useful in determining why this is happening? If you have some suggestions, let me know and I'll give them a try.

[anevilyak]

Realistically the best thing would be a reliable set of steps that causes this to happen so one of us can do so on our systems and analyze it. Do you only see the 0 byte behavior on x86-64 or on all architectures?

[vidrep]

Currently Webpositive is not working on 64 bit, so generating a debug report is easy. Keep trying to open Webpositive, and eventually you should get a 0 byte report from the debugger. I don't recall this happening on 32 bit, but that could be because it doesn't crash as much. If it happens on 32 bit, I'll definitely take note and update this ticket.

[anevilyak]

Is this still reproducible with the latest revisions? Report writing has been reworked in the meantime due to another issue that was found.

[vidrep]

I haven't seen this issue for a while now. I assume it has been fixed. However, I will reopen the ticket if it occurs again.

[anevilyak]

Thanks for the update!