search

jirentabu / crashrpt

Automatically exported from code.google.com/p/crashrpt
0 stars 0 forks source link

screenshot support at time of crash #8

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Add support for screenshots for each monitor (some systems have more than 1
monitor) that are included in the archive at the time of crash. bugtrap has
such support and I found it very useful.

Original issue reported on code.google.com by crcod...@gmail.com on 21 Nov 2009 at 5:10

GoogleCodeExporter commented 9 years ago 
I think this is a nice feature. Thanks for the info on bugtrap, I'll figure out 
what
it can do.

However, I think captured desktop image may contain some personal information 
of the
user, so we have to request additional user consent before sending such report. 
I do
not want some antivirus program detect CrashRpt as spyware.

Original comment by zexspect...@gmail.com on 22 Nov 2009 at 11:50

GoogleCodeExporter commented 9 years ago 
Understood about the personal information. For my projects there is no personal
information risk. These are workstations that process large volumes of data. Is 
a
simple crash dialog sufficient? I don't want to make my end-users to have to 
click
through numerous dialogs or repeatedly check radio buttons, etc. in order to 
include
the screenshot. My concern is that end-users won't send the crash report or stop
sending screenshots if the process is too cumbersome.

Original comment by crcod...@gmail.com on 23 Nov 2009 at 3:06

GoogleCodeExporter commented 9 years ago 
I think there won't be additional troubles for users, we should just let them 
know
that the report contains screenshots of the desktop.

I'm thinking about what image format to choose for screenshots (GIF or PNG). I
performed some tests and it seems that zipped GIF files provide better 
compression.
However GIF causes image quality loss (which is not critical factor). 

I think the report size should be as small as possible, that's why I would 
stick to
GIF format. Your ideas?

Original comment by zexspect...@gmail.com on 23 Nov 2009 at 4:14

GoogleCodeExporter commented 9 years ago 
GIF is fine. My workstations are usually dual screen running at very high 
resolution.
I am not so concerned about file size. There will be times where I will need to 
dump
the entire process space memory contents. Some of my crash dumps will be 
hundreds of
megs in size after compression. The difference between GIF and PNG is small when
compared to a dump file of the entire process space.

GIF or PNG is fine. Does not matter to me. GIF might be better for some users. 
PNG is
more widely accepted and more popular. Your choice.

I can say that bugtrap uses standard BMP which are huge. PNG or GIF would be an
improvement over BMP.

Original comment by crcod...@gmail.com on 23 Nov 2009 at 10:19

GoogleCodeExporter commented 9 years ago

Original comment by zexspect...@gmail.com on 23 Dec 2009 at 7:09

GoogleCodeExporter commented 9 years ago 
Issue 23 has been merged into this issue.

Original comment by zexspect...@gmail.com on 22 Mar 2010 at 3:30