<html>
<head>
<base href="https://bugs.documentfoundation.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Disable Crash report in master builds"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=126488#c34">Comment # 34</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Disable Crash report in master builds"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=126488">bug 126488</a>
from <span class="vcard"><a class="email" href="mailto:telesto@surfxs.nl" title="Telesto <telesto@surfxs.nl>"> <span class="fn">Telesto</span></a>
</span></b>
<pre>(In reply to Xisco Faulí from <a href="show_bug.cgi?id=126488#c27">comment #27</a>)
<span class="quote">> (In reply to Timur from <a href="show_bug.cgi?id=126488#c26">comment #26</a>)
> > Same issue in <a class="bz_bug_link
bz_status_NEW "
title="NEW - LO no print or crash when printing graphic/image in Linux"
href="show_bug.cgi?id=126368">Bug 126368</a>, I got a crash with master, otherwise not easily
> > reproducible, that I cannot write.
> > Is there any reason why we wouldn't have links in Crash report for master?
>
> I've said it before, we don't upload master symbols to the crashreport
> instance. The final releases already use thousands of gbs for their symbols
> and we upload new ones every week.</span >
Crash report working for daily DEV builds is maybe not the best thing to do..
However, I would like a crash reporter edition for 'release' builds in
Alpha/Beta/RC area.
1. to check for symbolic issues.. before
2. BT of mine tend to have a different outcome</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>