Page 1 of 1

Crashing on startup

Posted: Thu Feb 16, 2017 6:20 am
by alex4478
Hello,

I'm using version 4.6 on my iMac (macos Sierra) but every time I start the application it crashes.

Has anyone else found this issue? If so, was it resolved and how?

Thanks for any replies.

Re: Crashing on startup

Posted: Thu Feb 16, 2017 7:18 am
by Alt
Please contact our techsupport with this problem, they'll help you to solve it.

Re: Crashing on startup

Posted: Mon Aug 14, 2017 3:40 pm
by werdman
Alt wrote:Please contact our techsupport with this problem, they'll help you to solve it.
Would it be possible to push that kind of information to the forum? I am also experiencing the same issue and would benefit greatly by being able to reference the answer instead of contacting support :-)

Re: Crashing on startup

Posted: Tue Aug 15, 2017 6:45 am
by Alt
Do you use the latest version?
You see, our techsupport requests a crash report for the developers to fix the program in this case. I don't think you want your crash report be published on the forum.

Re: Crashing on startup

Posted: Tue Aug 15, 2017 7:39 am
by werdman
Alt wrote:Do you use the latest version?
You see, our techsupport requests a crash report for the developers to fix the program in this case. I don't think you want your crash report be published on the forum.
Yes, I have the latest version.

No, I would not want personal information posted.

That being said, while I do not know if our issues are the same, the result is the same. Given that there is more than one person having the issue, it would be nice that a forum ( in its true meaning ) be used to share possible things to look at. Ive went over every piece of documentation that is available through this site and am yet to come across something that even talks about anything remotely close to resolving application startup issues. Either your software is so amazing that it has never had a startup issue, your devs are so amazing that they have considered every and all possible conflicts with other software and system settings that it is not possible for the issue to exist, there has simply not been a need prior to now, or its a hush hush thing. If its the last one, it kind of defeats the point of a forum or public exchange of information.

A common practice, mostly to reduce the overhead for support needs, is to have things like the crash report submitted outside of the discussion, but to have the discussion still be available so that others may follow along if necessary.

Re: Crashing on startup

Posted: Tue Aug 15, 2017 8:35 am
by Alt
Well, the standard solution for a crash problem is to send a crash report, wait for the developers to solve the problem, download the new version.
Each particular case for the crash is quite a unique combination of the hardware, OS, and software which affects R-Studio. Common problems are usually eliminated during in-site and alpha testing.

Re: Crashing on startup

Posted: Fri Aug 18, 2017 1:11 pm
by werdman
As I have been in the process of working with some very large pieces of data, I have only been able to do limited testing but I have found the source of the issue in my case.

For me the issue was the presence of the JMS561U USB to Dual SATA Gen3 Ports Bridge
IOUSB:/USB3.0 Hub@00500000/USB to SATA bridge@00510000
**Attached image contains the details pertaining to the device from the registry**

This was found in the Thermaltake BlacX Duet HDD Docking Station, commonly found at Best Buy. I did not have the issue if the device was powered down. I did not have the issue if no drives were present in the device. The drives that were in the device were identified properly when using other means to attach them to the system. I do not know if the issue is related to your software specifically, or if there was something I could adjust in the OS or one of its related kext.

I apologize for not being more thorough than I was as I had already lost a week trying to work with other software which was not yielding very good results and was relieved to have it up and running.

I suspected that one of my Apricorn USB3 to SATA cables was at fault due to the fact that it does not transfer a product name from the guest device on it. I did not test this fully as it is an older model of which the new modes ( they look identical minus one extra hole used in the manufacturing of the device).

I also suspected one of my 3.5" external SATA drive bays made by Insignia to cause the issue but I did not test this fully.

I am pretty sure that both of the last two that I did not test all the way caused an issue, but I cannot remember for sure. When I get a moment ill hook them up alone and test to be sure.

Re: Crashing on startup

Posted: Sun Aug 20, 2017 8:16 pm
by Data-Medics
In my experience (years of it) with using R-Studio, the most common causes of crashes is related either to attempting to use software when the issue is actually a hardware problem (such as a failing hdd) or not having enough RAM.

You need a lot of RAM to run this software, and all data recovery software will give you issues if you've got hardware problems. Even just scanning the connected hardware, which R-Studio does on startup, will often crash out if any connected media is failing.

Re: Crashing on startup

Posted: Mon Aug 21, 2017 9:22 am
by Alt
werdman wrote:As I have been in the process of working with some very large pieces of data, I have only been able to do limited testing but I have found the source of the issue in my case.

For me the issue was the presence of the JMS561U USB to Dual SATA Gen3 Ports Bridge
IOUSB:/USB3.0 Hub@00500000/USB to SATA bridge@00510000
**Attached image contains the details pertaining to the device from the registry**

I am pretty sure that both of the last two that I did not test all the way caused an issue, but I cannot remember for sure. When I get a moment ill hook them up alone and test to be sure.
I've sent the link to our developers, but still, they'll ask you to send them a proper crash report.

Re: Crashing on startup

Posted: Mon Aug 21, 2017 12:05 pm
by Alt
Alt wrote:
I've sent the link to our developers, but still, they'll ask you to send them a proper crash report.
As I predicted, they asked for the crash report. Better, send it to my mail raptorbck (at) gmail (d0t) com