No, I don't think it's worth blocking the feature. I do think long-term we
want to be touching all untrusted data in separate processes though --
talking to the cachingreaders via FIFO, etc. It's a big hassle but it would
eliminate a category of crashes we see.
On Mon, Oct 20, 2014 at 9:05 AM, Owen Williams <owilli...@mixxx.org> wrote:
> On Mon, 2014-10-20 at 09:01 +0300, Tuukka Pasanen wrote:
>> Hello,
>> Can't tell why no parsing in separate process but sound bit harsh to
>> me and doesn't really fix the problem of crashing..
>
>
> That's my point, RJ's contention is that if we don't have a separate
> process, we will get crashes. So I am saying, is it so crashy that we
> have to delay this feature until we can isolate the process, or can we
> consider the rare crash due to bad files an acceptable risk.
>
>
>
------------------------------------------------------------------------------
> Comprehensive Server Monitoring with Site24x7.
> Monitor 10 servers for $9/Month.
> Get alerted through email, SMS, voice calls or mobile push notifications.
> Take corrective actions from your mobile device.
> http://p.sf.net/sfu/Zoho
> _______________________________________________
> Get Mixxx, the #1 Free MP3 DJ Mixing software Today
> http://mixxx.org
>
>
> Mixxx-devel mailing list
> Mixxx-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/mixxx-devel
------------------------------------------------------------------------------
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push notifications.
Take corrective actions from your mobile device.
http://p.sf.net/sfu/Zoho
_______________________________________________
Get Mixxx, the #1 Free MP3 DJ Mixing software Today
http://mixxx.org
Mixxx-devel mailing list
Mixxx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mixxx-devel
